Because different Combinations need different data fields in the header. And here we need to understand those 3 Combinations in fields differences. In condition type PR00, there are 3 types of Key Combination. So here we will take an example of condition type as “PR00” which is frequently used in purchasing price condition. In business requirement, we need to acquire data value about what kinds of condition type from business users side need to be migrated. The first data field when we enter in screen is “Condition Type” in price condition.
Understanding Data Field Maintenance Sequence and Relationship in Creation is helpful for following template value filling.
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.įirst, to start with foreground work, we need to know how to manually create price master data under Transaction Code VK11. 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.
0 kommentar(er)
