Reply: 1

Auto translated

How to interface with customer duplicates from previous system

Hello All,

We are currently in the process of creating the technical and business concept for a customer's migration to S/4.

We currently have the following problem: Our customer has a previous system. This is a booking system where the customer can book without login. The data is transferred from this pre-system via an interface to R3, where the customers are then always created with a new customer number and thus with a new customer master record, which is logical, since there is no login and the booking system sees each customer, even if they recur, as a new customer and transfers it to SAP. As a result, we have a system that has numerous customer duplicates.

Now we were wondering if, as part of S/4HANA in the standard, there is a way to either:

1) Identify the customer duplicates and either merge the redundant data into one customer or purge the redundant ones.

2) Otherwise solve the above mentioned problem.

Thank you very much in advance.

Kind regards

You must be logged in to post a reply.

Login now

1 Answers

  • BETA
    ChatBot
    Automated answer
    This reply was automagically generated by our Espressi A.I. Think of it as a one-off attempt to instantly solve your problem. It will not respond to further replies.

    Hello, Regarding the customer duplicates in S/4HANA, there are several solutions that can be considered. 1) SAP S/4HANA provides native data cleansing tools that can identify and eliminate duplicates. Among others, there is the "SAP Master Data Governance" (SAP MDG) software that can help solve the data quality problem. It allows duplicates to be identified while records are being created and can help eliminate redundancies and increase data quality. 2) Within SAP S/4HANA, there is the Business Partner, which serves as the central customer and vendor master data store. Here, one could define rules in the business on how duplicates should be identified and what actions should be taken in response. 3) As part of an S/4HANA migration, a method of data cleansing can be performed in advance that also targets duplicate checks and merging of redundant information. This would happen prior to the migration to ensure that only clean data is transferred to the new SAP S/4HANA landscape. Please note that these approaches require careful planning and implementation to ensure that data cleansing is performed correctly and efficiently. Best regards!

    Need more help from our chatbot? Click here and visit our AI SAP Helper on the SAP learning platform et.training.1

    1. log in with your Espresso Tutorials account. Digital subscription or trial access required.