Enterprise Resource Planning Blog Posts by SAP
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Introduction to the Parallel Line

SrividyaNR01
Advisor
Advisor
‎2025 Apr 03 11:10 AM
2,805

Introduction to the Parallel Line

In the current situation with SAP Central Business Configuration (CBC), extending a new country solution, business configuration (finetuning), and releasing it to the productive system is all possible with only one CBC workspace. What if there was an additional CBC workspace to add new countries/regions or extend the business configuration, test it and then transport it to the productive system, without disturbing the ongoing implementation project? You heard it right!! This is exactly what parallel line is meant for.

This blog post aims to provide an overview of the parallel line, its functionality and benefits.

The parallel line enhances the existing SAP S/4HANA Cloud Public Edition, 3-system landscape by including an additional CBC workspace with a parallel customizing tenant (D.120) and a parallel test tenant (T.120). The primary function of the parallel line is to separate the incremental configuration activities from the main line and use the parallel line to develop and test configuration enhancements, without impacting the main line.

Benefits of having a parallel line

  • Incremental implementation of countries/regions
  • Build additional master data
  • Extend new organization structure
  • Scope extension
  • Enhance and validate additional finetuning
  • Run sessions for trainings within the project teams
  • Replicate subsequent changes done in the main line to the parallel line via rebase
  • Replicate new country/scope extended in parallel line to main line via merge

Before we jump to further details of the parallel line, it is important to understand that we will have the below segregation of tenants:

Svidya_0-1743674225505.png

Branch:

Branch is the operation of creating a parallel line by copying the business configuration from the main line. With the parallel line, two additional SAP S/4HANA Cloud Public Edition tenants, a parallel customizing tenant (D.120) and a parallel test tenant (T.120), are provisioned and the business configurations are copied as follows:

  • The customizing tenant (D.100) is copied to the parallel customizing tenant (D.120)
  • The test tenant (T.100) is copied to the parallel test tenant (T.120)
  • The CBC main line workspace is replicated into the CBC parallel line workspace.

What gets copied during Branch:

  • Business Configurations – Scope/ Organization Structure/ Financial settings
  • Address Data of Configurations
  • Product-specific Configuration
  • Client-dependent configurations
  • Business roles and catalogs
  • Cross-client key-user extensibility*
  • Client-dependent key-user extensibility*

*There are a few configurations/extensibility objects which are currently not replicated to the parallel line during branch and need additional attention in the parallel line. SAP is looking at resolving these limitations in the upcoming releases. Please refer to 3542536 - Release Note for SAP S/4HANA Cloud Public Edition for more details.

SrividyaNR01_1-1743689206552.png

Fig 1 : Branch

Once SAP completes the branch procedures:   

  • A new workspace gets created in CBC, which starts with “Parallel Line of XXX“, where XXX is the name of your main line workspace. This project is a copy of the main line workspace.

Svidya_1-1743662941226.png

Fig 2 : CBC workspace for parallel line

  • The initial Administration user receives the handover email for the parallel customizing and the parallel test tenant. These two new tenants will also be connected to the existing non-production (test) SAP Cloud Identity Authentication Services(IAS) tenant and hence it works with single-sign on.

 

SrividyaNR01_0-1745311206034.png

SrividyaNR01_1-1745311260741.png

Fig 3 : Hand over e-mail of Parallel Customizing Tenant      

   

SrividyaNR01_2-1745311349520.png

SrividyaNR01_3-1745311382555.png

   Fig 4 : Hand over e-mail of Parallel Test Tenant

 

  • As per requirement, new business users need to be created, and the business roles need to be assigned to the business users accordingly. For more details on onboarding business users, please refer to Onboarding Business Users | SAP Help Portal

Master data creation is necessary in both the parallel customizing and the parallel test tenants. While master data itself is not copied into parallel line, for the SSCUI configurations dependent on master data, you can use a report from the application “Manage Check Runs for Business Configurations“ to determine which master data needs to be created to keep the main line and parallel line harmonized. To access this application, business catalogs SAP_CORE_BC_BCC_DSP_PC & SAP_CORE_BC_BCC_PC are required, which are available with the business role template “SAP_BR_BPC_EXPERT”. This application is available in both the parallel customizing and parallel test tenants. Refer to  “Migrate Your Data - Migration Cockpit | SAP Help Portal“ for mass master data creation via the Migration Cockpit. For more details, please refer to “Manage Check Runs for Business Configurations “.

With this, the parallel line is ready for consumption.

How to Request a Parallel Line

SAP for Me is the gateway for all system provisioning requests in SAP S/4HANA Cloud Public Edition and also for the parallel line. S-User Administrator can request the branch from the “Services and Support” dashboard. Before requesting the branch, the prerequisites for a branch should be verified. For more details on how to request a branch from SAP for Me, please refer to the blog post Parallel Line Branch via SAP for ME

Prerequisites for Branch

For a seamless and smooth branch process, the below prerequisites need to be taken care of before you can request a parallel line branch:

  • SAP Central Business Configuration is ready for branch:
    • In the main line workspace, all activities and milestones of the “Scope and Organizational Structure” phase are completed.
    • The main line workspace is in the “Product-Specific Configuration” phase.
    • The main line workspace is unlocked.

 

  • The SAP S/4HANA Cloud Public Edition Customizing tenant is ready for branch:
    • Release all CBC and BC transports in the customizing tenant.

 

  • The SAP S/4HANA Cloud Test tenant is ready for branch:
    • Import all transports in the import buffer of the test tenant.

Once the parallel line is ready for consumption and the existing implementation project is ongoing in the main line, there may be an extension of business configurations like scope items, an organization structure extension, or SSCUI configurations happening in both lines. To keep the parallel line and main line synchronized with data, there are two additional functionalities available for the parallel line.

Rebase:

Business configurations added to the main line after the branch can be synchronized to the parallel line with the rebase functionality in the parallel line workspace in CBC. For more details, please refer to blog :Rebase: Synchronize the Configurations of Your Main Line with Your Parallel Line

SrividyaNR01_0-1743689082461.png

Fig 4 : Rebase

Merge: Business configurations added to the parallel line after the branch can be synchronized to the main line with the merge functionality. Currently, merging is a manual process. For more details, please refer to SAP Note 3584765.

With this, the user will be able to efficiently use the parallel line for their additional business configurations and implementations.

Thank you for reading the blog post. You may also refer to   Parallel Line in SAP S/4HANA Cloud Public Edition | SAP Help Portal & Parallel Line in SAP Central Business Configuration for more details.