cancel
Showing results for 
Search instead for 
Did you mean: 

Vendor Master data migration using migration cockpit in 1909

Hi All,

I have requirement to load Vendors master data using migration cockpit through file staging process but if i look the available objects in Mig cockpit vendor migration supports only direct transfer and i can not use that due to source system,

Could you please assist me do i have to create custom object for that or should i use available migration objects

Accepted Solutions (0)

Answers (4)

Answers (4)

Elizaveta2
Advisor
Advisor

Hello,

You may choose the approach you would like to use:

In File/Staging tables there are Supplier, Customer MOs.

In Direct Transfer there are Vendor, Customer, Business partner MOs.

1) Regarding your question about Business Partner with Staging tables approach 1909 – in the Supplier MO Docu, you will find some info, for example:

Out of scope N.2 Supplier and customer are two separate business partners with, as a consequence, two different numbers. With the Supplier - extend existing record by new org levels data migration object, you're able to create a supplier with the same customer number. As a prerequisite, you have to create the customer first.

One of the Mapping instructions: If you need to create a business partner with both customer and supplier roles, you can enter this manually or extend an already migrated customer with the Supplier - extend existing record by new org levels migration object.

2) If you would like to use the Direct Transfer approach, you may refer to this Customer Vendor Integration PDF:

https://www.sap.com/documents/2020/10/1cc0e08c-b57d-0010-87a3-c30de2ffd8ff.html

3) Regarding the mandatory fields, you can influence that with the SAP S/4HANA migration object modeler (choose if the fields should be mandatory or not) – until it does not influence the API behavior – if the API needs these fields, you may receive an error in Simulation..and may need to try the dummy values.

You may want to check how to use the migration object modeler:

https://help.sap.com/viewer/ffaed9ee977247e689972af70212149e/SHIP/en-US/8bc93e781ddd463a9710bf5d505d...

4) In the Fiori, Migrate your data app, when you copy the migration objects to the project, you can check “Tables” info, there are technical names listed – see the picture. In the documentation this info is included in Supplier MO (section: “In scope”), but if you want to check the technical names, you can use Migrate your data app (migration cockpit).

Best regards,

Elizaveta

former_member132078
Active Participant

Hello Sreenivasulu,

Below is the object documentation for 'Supplier' migration object.

https://help.sap.com/viewer/d3a3eb7caa1842858bf0372e17ad3909/1909.000/en-US/16b8c81e2269493a8b8b44b3...

Post migration, you can validate the data using transaction BP. The underlying tables example LFA1... also gets updated when Supplier is created.

With BP Grouping field on the General Data sheet, you arrange the different number ranges (internal or external) and the vendor account group.

The above document link provides additional information.

Best Regards,

Shreyanka

Elizaveta2
Advisor
Advisor

Hello, this object is called "Supplier". In later releases, the name "Vendor" was replaced with "Supplier" in Direct Transfer approach as well.

Best regards,

Elizaveta

0 Kudos

Thanks Elizaveta for responding, So in the supplier object can i map template file with the vendor tables of LFA1,LFB1,LFBK ,LFM1 also in file i see there are mandatory fields of BP_ROLE and BP GROUP but my source does not have those information.

0 Kudos

Hi All,

I was bit confused need clarifications on the below, As per my understanding customer and vendor master data we cal Business Partner in S4HANA system,

In S4HANA cockpit we have migration objects like Business Partner, Customer, Vendor, Supplier and for example if i want to migrate LFA1,LFB1,LFBK ,LFM1 tables in cockpit is that Business partner, vendor and supplier objects are same or different ?

why many objects for customer and vendor migration and how we choose which one to use.

Regards,

Sreenivas.