[DMC] Migration Cockpit File Load – Price Condition
In this post, the objective is to help you to understand data fields in standard template and successfully migrate object “Condition record for Pricing” by file load approach under ERP to S/4 HANA migration scenario in new version S/4 HANA 2020 OP. As described in many other posts about Migration Cockpit and the standard template delivered by SAP, I will show that it is not much difficult to populate correct field value in the template to meet migration cockpit program.
- Understand Foreground Work
- Understand Technical Table
- Hands On DMC Template
- Hands On Fiori Migration Cockpit
1. Understand Foreground Work
First, to start with foreground work, we need to know how to manually create price master data under Transaction Code VK11.
Understanding Data Field Maintenance Sequence and Relationship in Creation is helpful for following template value filling.
Therefore, we need to check which combination needs to migrate from legacy table.
2. Understand Technical Table
Let’s move to technical table – KONH (Conditions Header) and KNOP (Conditions Item).
In the foreground screen, there are different types of Key Combination. Here we run Transaction Code SE16N to check what value is recorded in legacy table.
In foreground work, combination is “Material with release status”, it needs two mandatory fields “sales organization/distribution channel” in the header.
3. Hands On DMC Template
|LIFNR||Supplier’s Account Number|
|PLTYP||Price List Type|
|WAERK||SD document currency|
|UKONM||Material pricing group of main item|
|UPMAT||Pricing reference material of main item|
|ESOKZ||Purchasing info record category|
|EVRTN||Purchasing Document Number|
|EVRTP||Item Number of Purchasing Document|
|INFNR||Number of purchasing info record|
|LLAND||Country of Destination|
|LIFRE||Different Invoicing Party|
4. Hands On Fiori Migration Cockpit
Now we have correct value in the template. The next step is to load template into Fiori migration cockpit.
- choose all 8 mapping tasks and click confirm.
- select mapping object one by one, go into details to change and confirm value.
- Download mapping template, upload mapping value through template.
Price Condition becomes an easy object to migrate after you understand the most difficult field “Field Name” in data migration cockpit standard template.
I hope this blog post makes you get the ways of how to migrate price condition data object from source ERP to S/4 HANA and will help you in data value populated by SAP delivered migration template to meet your business requirements.