Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 


This blog explains the different approach for the load of customers, suppliers (vendors), contact persons in S/4HANA, that makes the use of business partners for these objects mandatory and old transactions like XD01, XK01, ... have been deprecated and are no longer available. I will explain how the data migration cockpit can be used for customer load and what is the logic to fill the file template for customers with its different sheets (general data, sales view, finance view, contact persons,...).


How customers were loaded with ECC 6.0

With SAP ECC6.0 and previous versions it was common to create LSMW objects linked to different recordings created ad-hoc with transactions XD01 or VD01 or use program RFBIDEK0. File structure had to be defined within LSMW.



Why approach with ECC 6.0 is no longer possible. Business Partner concept.

S/4HANA requires the use of business partner, instead of using previous methods of creating separate objects for customers, suppliers and contacts. Transactions like XD01, VD01 are outdated and SAP will redirect to new transaction BP, which will be the single point of entry to mantain these objects.

With the business partner approach, one BP can be a customer, vendor (now supplier), contact person, payer, etc. all at once, so there is no need for separate master data objects. The business partner role will define the role they have in the company.

These roles can be defined in customizing.


With the new business partner concept, the tables starting with BUT* are the central repository for all BP created. Older tables like KNA1, KNVV, KNB1 are still filled in S/4HANA, but it is necessary to do the necessary customizing settings in Customer-Vendor-Integration (CVI). CVI is used to synchronize customer and vendor master data objects with SAP business partner objects within SAP. With CVI in place, all the customers and vendors are assigned a BP number.

Besides this, with S/4 HANA it is not recommended to use LSMW, as there is a new data migration tool called Data Migration Cockpit, which provides file templates that we will fill to perform the data migration.



Load customers with Data Migration Cockpit. Fill the file template

The Migration Cockpit (transaction LTMC) provides structured migration templates as it is the case for Customer Master and Customer Master Extension.


To get the file you can click the corresponding option in the migration object. This will download an xml file that can be edited in Excel.


The Customer Master template contains a number of sheets, each sheet has mandatory fields marked with (*) which must be filled.


The person responsible of loading customers needs to fill the load template. I start with the general data that covers name, account group, ….  Although it is possible to use internal numbering for customer creation, customer number is mandatory on the template as it serves as the unique identifier to link data in all sheets to the general data in the first sheet.

If for some customer accounts types you need to use external numbering, it is necessary to enter those in the sheet and use them in all sheets. In this example I use sequencial numbers.


Address data also available in this sheet.


With S/4HANA Business Partner concept it is necessary to specify the business partner role. In this case I have to choose FLCU01 for customers.


The sales views need to be specified in the sheet Sales Data.It is necessary to use the customer number key entered in General Data sheet to link this and other sheets, otherwise there will be an error in the import.


Company code view filled in sheet Company Data. Here is where I set the payment terms, reconciliation account, …


Contact person data: I assign the contact persons to each customers, using consecutive numbers as ID as numbering will be internal.


Sales partner: The customer numbers are repeated four times to assign each partner role to that customer.


There are other views that can be filled for sales texts, company texts, ... but not included in this exercise. It is necessary to link all possible entries in the file to to the customer numbers specified in the general data view.



Load customers with Data Migration Cockpit. Run LTMC

Inside of the migration object first it is necessary to upload the filled file.


Once uploaded, the file needs to be activated.


Now it is possible to start the transfer.


Next step is the data validation. Depending on the file size, this will take some time.


Once finished, the migration cockpit will show all file validation messages like wrong format, missing mandatory fields, ….


Next step is the conversion for the field values.


The template contains an external number for the customer; however, we need internal number assignment so the mapping is maintained as below;


Remember the number ranges have to be set up in customizing.


Click on save and the internal numbers will be generated in sequence.

For other fields I had to add the conversion values from the file to the S/4HANA instance.


Next step is to simulate the import in SAP, where different errors might appear.


Any errors will appear in the notification screen.


Once done, it is time to import the data in SAP. Executing the import loads the data in SAP.


data loaded appears in the log. If there are some errors, a Delta file would be created to be processed at a later stage.


Once loaded, I check in transaction BP that the customers are loaded. It is also possible to use transaction SE16N with tables BUT000 and KNA1, KNVV, …



As summary, a business partner can be a vendor, customer, contact person all at once and there is no need of separate objects. As this is the new approach in S/4HANA. this makes the use of LSMW not recommendable.

The data migration cockpit is then the best approach in a low complexity scenario, with data being migrated from a single legacy system to a new SAP S/4HANA environment with minimal data transformation requirements.
Labels in this area