3433477 - Best practices for Key User Extensibility in Parallel Line - SAP S/4HANA Cloud, public edition

SAP offers a new feature called Parallel Line for selected early adopter customers of SAP S/4HANA Cloud, public edition.

This note provides best practices for the use of Key User Extensibility in that environment including restrictions.

This SAP Note is subject to change. Please check this note regularly for updates.

SAP S/4HANA Cloud, public edition

Supported Key User Extensibility.   

Due to their inherent characteristics, key user extensibility is divided into two types:

• Client-independent key user extensibility (such as Custom Fields) created in the main line are automatically available in the project line. Such key user extensibility can't be created in the Parallel Line.
• Client-dependent key user extensibility that supports your implementation project created in the main line are copied to the project line during the provisioning process.
  • Copied items can be changed in the Parallel Line independent of the mainline.
  • New client-dependent key user extensibility items can be created in the project line.
  • However there is some exceptions that don’t support the branch process, yet. For such items there is only the option to create them anew in the Parallel Line. A list of these items type can be found below.
    • Business User Group
    • Business Role Group
  • For key user extensibility, there is no option to merge or rebase until now. Manual double maintenance is needed in the respective apps.

View the supported item types in the Extensibility Settings app.

The type of Key User Extensibility objects that are client-dependent can be checked in the Extensibility Settings app. 

Transport from Development System to Test System.

The Export Software Collection app will show a single default software collection that can be used to transport all items that are created in the project line client of the development system.

The key user extensibility items can be added to this software collection only. This brings the following restrictions:

• There will be no option to create further software collections.
• The default software collection can't be deleted.
• It's not possible to move items to another software collection, or to merge software collections.
• It's not possible to do a hotfix export. You have the option to export changed and deleted items, or all items altogether.
• Only client-dependent items belonging to the same client will be visible and can be added to the software collection.

The Import Collection app will show the versions of that extensibility software collection that are transported to the same client in the test system. It can be used to import the software collections as usual.

Applications/business catalogs overview in the Parallel Line tenants:

Notes:

Client-independent key user extensibility items need to be transported using the client 100, and they will be automatically available in every test tenant client.

Business catalog SAP_CORE_BC_SL_IMP (Business Role template SAP_BR_ADMINISTRATOR) is required in project line test tenant(client 120) to use the Import Collections app.

Dependency Management

There is several types of dependencies that can appear between the customizing created in your implementation project and the key user extensibility:

• The customizing of your implementation project depends on client-dependent extensibility (such as Financial Substitution and Validation, for example). The extensibility item needs to be imported in the project line tenants of the test system before the customizing can be imported to the same tenant.      
• The customizing of your implementation project depends on client-independent key user extensibility (such as Custom Field, for example). The extensibility items needs to be imported in the main line tenant of the test system before the customizing can be imported in the project line tenant of the test system.
• Client-dependent key user extensibility (such as Financial Substitution and Validation, for example) in the project line tenant depends on client-independent key user extensibility (such as Custom Field, for example) in the main line tenant. The client-independent extensibility items needs to be imported in the main line tenant of the test system before the client-dependent extensibility item can be imported in the project line tenant of the test system.

Best Practices

• You might need to develop new client-independent key user extensibility items in the main line because they are needed for your implementation project in the Parallel Line. The key user extensibility items should be kept in a dedicated software collection in the Export Software Collection app of the main line tenant. This will allow to separate the development for the implementation project from development for the main line production system. Hence the collection can be exported and imported to the main line tenant of the test system without the need to forward it to the production system.
• After the implementation project is finished bring the client-dependent extensibility items to the main line and add them to the same software collection that already contains the client-independent development for the implementation project.

3399785 - Release Note for SAP S/4HANA Cloud, public edition, parallel project line with 2402 Release - SAP for Me

3483536 - Release Note for SAP S/4HANA Cloud, public edition, parallel project line with 2408 Release. - SAP for Me

3542536 - Release Note for SAP S/4HANA Cloud Public Edition, Parallel Line with 2502 Release - SAP for Me

Parallel Project Line, PPL, transport, export, import, software collection, Parallel Line , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , How To