This blog aims to provide information about the new feature that allows copying of Master Data related to Business Configuration in a Parallel Line from the Main Line. Thanks to Divyaprakash Singh & Nicola Pace for valuable inputs.
Prior to release 2602, the “Manage Check Runs for Business Configurations” app was used to run checks for Business Configurations, displaying the progress and status of the checks. Some configuration tables are designed so that individual fields can reference business master data. For example, when configuring a production plant, a Business Configuration Expert can assign a default supplier that is automatically used when the plant receives materials. This can create a mismatch — i.e., the value stored in the configuration table may reference master data that exists in the Main Line but not in the target tenant (Parallel Line) where the configuration is being deployed. Hence, there is a need to perform these checks to ensure that there is no mismatch between the data referenced in the Business Configuration and the data existing in the tenant.
At the end of the check run, the system issues either a successful or error status:
- Successful status means there is no missing master data — i.e., all defined references to master data in the scanned configuration tables exist in the current system where the check run was executed.
- Error status means that some references to master data in the scanned configuration tables do not exist in the current system. Resolution options include replacing the data with master data that exists in the system or manually creating the referenced data in the system.
The recommendation is to perform the checks after executing the Branch, Rebase or Merge process — i.e., when creating a Parallel Line from the Main Line, synchronising the data from Main Line to Parallel line or vice versa.
In addition to check runs, here also possible to perform a simulation of Cross-Client Validation to check configuration consistency using the “Manage Check Runs for Business Configurations” app. This check ensures that changes in configuration data in a tenant of the development system match the configuration used by business data present in target systems, such as test or production systems. The recommendation is to always run the check before you perform a merge operation.
For further details, please refer to the following SAP Help documentation:
As of release 2602, a new feature has been enabled that allows copying of certain Master Data from the Main Line (ML) to the Parallel Line (PL) via SAP for Me. This functionality helps maintain the consistency of Business Configurations by replacing the manual effort needed post branch. Prior to this release, customers had to manually maintain the configuration-referenced master data, the “Manage Check Runs for Business Configurations” app after the Branch process was needs to trigger and configured for the missing master data.
A flag is now available which, when enabled, allows the copy of the following Master Data objects:
- Address Number
- Bank Master Record
- Business Partner
- Cash Pool
- Contract Account Header (Partner Specific)
- Cost Centre
- Customer
- FIFM: Financing Code
- Hierarchy Directory
- House Bank Account IDs
- House Banks
- Job Code Tile (Worker)
- JVA Agreement
- JVA Master
- JVA Partner
- Material
- Profit Centre
- Vendor
Please note: Only during Branch process, the relevant Business Configuration master data is copied from D100 to D120 and from T100 to T120 once the flag is enabled.
It is also important to note that the feature also generates the business user in Parallel Line without any business roles assigned. There are also set of pre-requisites which needs to be met before requesting the copy of master data during branch. More information is available in the following link –
Thank you for reading this blog post.
Your insights and opinions are valuable, so please don't hesitate to contribute by commenting on this blog.
Follow us via @SAP and #S4HANA or follow @JaiSrinivasan .
