As a business process configuration expert, I have been using the parallel line offered with SAP S/4HANA Cloud Public Edition, 3-system landscape. I have performed several configurations in the main line, such as creating a new scope and organizational structure or extending business configurations for my ongoing implementation project. I wonder, how do I validate whether these additional configurations created in the main line work in the parallel line? Should I redo all these configurations in the parallel line again to test this? Ugh!! This seems like a lot of effort, but essential to ensure everything functions correctly.
Do you also have these questions about using the main line and parallel line simultaneously? If so, this blog post is just for you.
SAP offers a functionality called Rebase, which helps transfer the delta business configurations from the main line to the parallel line after branching. For more details on branch and parallel line, refer to my earlier blog Introduction to Parallel Line.
Rebase - Overview
After creating the parallel line, you can use it to create and validate additional business configurations. Meanwhile, continue using the main line to perform business configurations and run business processes in the ongoing implementation project. Use the rebase functionality to transfer these delta configurations to the parallel line.
Prerequisites for Rebase
Please ensure you address the following prerequisites before initiating the rebase from SAP Central Business Configuration (CBC).
- You are currently in your parallel line workspace.
- The main line workspace is in the “Product-Specific Configuration” phase.
- The parallel line workspace is in the “Product-Specific Configuration” phase.
Rebase - Process
To initiate a rebase, go to the “Settings” tab of the parallel line workspace in CBC and choose “Rebase”.
Rebase can be initiated from the parallel line workspace by a user who has either the “SAP_CBC_CONSUMPTION_PROGRAM_LEAD” user group or the “SAP_CBC_CONSUMPTION_PROJECT_LEAD” user group assigned.
Fig : Initiating a rebase in SAP Central Business Configuration
Staging Activation During Rebase:
After you’ve initiated a rebase, the parallel line workspace is locked. The status can be checked in the “Deployment Target” app.
Fig : Parallel line workspace locked during rebase
Fig: Navigation in the "Deployment Target” app
In the “Deployment Target” app, two staging IDs with the description “BC Rebase” are displayed:
- “SAP Central Business Configuration” – With this staging type, the delta of the SAP Best Practices reference content configured in the main line is transferred to the parallel line.
- “Customer” – With this staging type, the delta of the customer adaptations configured in main line is transferred to the parallel line.
Both staging types are sequentially transferred, starting with the “ SAP Central Business Configuration” staging followed by the “Customer” staging.
Fig: Rebase – activation of SAP Central Business Configuration
Once the “ SAP Central Business Configuration” staging type is in status “Staging Completed”, the “Customer” staging type is automatically created and stays in status “Transfer Completed”.
While the “ SAP Central Business Configuration” staging type does not require any action from the user, the “Customer” staging type requires some action to complete the transfer to the parallel line.
Fig: Rebase – Customer staging
Note : During the Rebase staging activation, the main line workspace is not locked and can be used for ongoing project activities.
Activation of the “Customer” Staging Type
Customer staging records all the customer adaptations through configuration activities performed in the main line, which are required to be rebased to the parallel line performing the following steps:
- In the SAP Central Business Configuration workspace for the parallel line, go to the “Deployment Target” tab, and choose “Go to Deployment Target” to access the “Display Business Configuration Stagings” app in parallel customizing tenant(D.120).
- In the “Display Business Configuration Stagings” app, select the “Customer” staging type with the description “BC Rebase”.
- Go to the “Activities” tab. The IMG activities that are part of the rebase are visible and in status “Not processed”.
- Choose “Display<->Change”. The “Activate” button gets enabled.
- Select all IMG activities and choose “Activate”.
Note: A strict sequential activation process is followed here. If one activation fails, the subsequent activations does not proceed. You'll need to resolve the failed activity before moving forward.
Some business configuration data is excluded during rebase and shows status “Processing Failed” during the activation. This requires double maintenance, meaning these configurations are required to be manually configured in the parallel line. For a list of excluded configuration activities, please refer to Excluded Configuration Activities During Rebase and Merge | SAP Help Portal
- Once all the configuration activities are activated successfully, they will be in status “Processing Completed”.
- Choose “Display<->Change” and set the staging to completed.
- Once the staging is completed, the “Customer” staging type is set to “Staging Completed”.
With this, the rebase process is complete, and both your main and parallel lines get synchronized. The parallel line workspace also unlocks, and the "Rebase" button is greyed out if there are no further configurations to rebase.
Note: If there are any erroneous activities during the activation of the “SAP Central Business Configuration” staging type, the “Customer” staging type will not be created. Please create a support case under component CBC-BCL-PL.
Conflicts During Rebase:
When rebase is initiated, a background check for conflicts is run in CBC based on the configuration done in both the main line and the parallel line. When conflicting configurations exist for the same configuration table, they're reported in the "Conflicts" tab. This allows users to review and adjust the configurations between the two lines.
While background jobs for conflicts run, the parallel line workspace is locked. If conflicts are detected, the workspace is unlocked with a notification message for conflict resolution.
Fig: Conflict notification
Access the “Conflict” tab in the parallel line workspace to view the details of the conflicts. By clicking on the details, you’re forwarded to the details of the conflicts between the main line and the parallel line.
Fig: Conflicts tab
Fig: Conflict details
Clicking the "Compare" button initiates a comparison between the customizing tenant (D.100) and the parallel customizing tenant (D.120). This process focuses on configurations that have conflicts.
Fig: Conflict comparison
Fig: Comparison results
Based on the decision about which configuration entries to retain, adjust the other line to resolve the conflict.
After resolving conflicts by adjusting the configuration entries, CBC typically takes about 10-15 minutes to receive and process the backsync from SAP S/4HANA Cloud Public Edition. Therefore, no conflicts should be visible in the "Conflicts" tab 15-20 minutes after resolving them.
After resolving conflicts, initiate the rebase again. This allows the rebase process to proceed. Y ou can check the rebase progress in the “Deployment Target” tab of the parallel line workspace.
In case, there are erroneous scenarios during rebase or if you have other issues during conflict resolution, create a support case for component CBC-BCL-PL.
Rebase Content in Parallel Test Tenant (T.120)
After completing the rebase, you'll find two transports labelled "BC-Rebase" in the "Export Customizing Transports" app in the D.120 tenant. These transports are created for both the "SAP Central Business Configuration" and the "Customer" staging type. You need to move these transports to T.120 to make the rebased content available there.
Thank you for reading this blog post. You may also refer to Rebase and Merge | SAP Help Portal and Rebase - Overview | SAP Help Portal for more details on rebase.
| User | Count |
|---|---|
| 17 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
