Symptom
Before you develop an extension that should be re-used by several customers you should make yourself familiar with the different option to package and deliver such extensions.
How can you package your solution from your SAP S/4HANA Cloud Public Edition tenant?
Environment
SAP S/4HANA Cloud Public Edition
Resolution
[1] You can build a Extensibility Template.
- You must request the enablement of "Namespace and Template Development" according to this SAP Note 2787809 - ATO: Enable Extensibility Template Development in SAP S/4HANA Cloud, public edition - SAP for Me.
- After that the key users can develop extension items in a dedicated namespace. The users must assign themselves to that namespace via app Extensibility Settings
- Namespaces like '/XYZ/' cannot be used to develop Extensibility Templates. During enablement for Extensibility Templates SAP will create a unique namespace starting with 'YY'. Customer namespaces in the '/../' format cannot be used.
- The extension items in that namespace can then be collected into an Extensibility Template in the app Export Extensibility Template
- The Extensibility Template can then be downloaded from the system and be uploaded to other customer systems
- The upload is done in app Import Extensibility Template
- Provisioning Product: SAP S/4HANA Cloud / System Role: Partner Customizing
- Supported Extension Items:
App Name | Extensibilty Item |
Custom Business Objects | Custom Business Object
For details, see Creating Custom Business Objects. |
Custom Reusable Elements | Custom Code Lists
For details, see Creating Custom Code Lists. |
Custom Fields | Custom Fields
For details, see Creating Custom Fields. |
Custom Logic | Custom Logic
For details, see Creating Custom Logic. |
Custom Reuse Library | Custom Library
For details, see Creating Custom Libraries and Methods. |
Custom Analytical Queries | Custom Queries
For details, see How to Create Custom Queries |
Custom CDS Views | Custom CDS Views
For details, see Creating Custom CDS Views |
[2] abapGIT can be used to deliver Custom Fields.
- Creating Custom Fields for abapGit Integration | SAP Help Portal.
- Key User Extensibility and abapGit | SAP Help Portal
- How to transport SAP S/4HANA Key User Custom Fields using abapGit - SAP Community
- Provisioning Product: SAP S/4HANA Cloud / System Role: Partner Development
[3] Scalable Delivery can be used to deliver Custom Fields as part of a partner Addon.
- Developing an Extension Using Key User Extensibility | SAP Help Portal > Creating Custom Fields in a Partner Add-On.
- Scalable Delivery | SAP Help Portal
- Landscape Portal for SAP S/4HANA Cloud, ABAP environment | SAP Help Portal > Maintain Namespaces | SAP Help Portal
- Provisioning Product: SAP S/4HANA Cloud / System Role: Partner Add-On Development
[4] Multi-Off delivery via GIT-enabled CTS does not support Key User Extensibility.
- General Rules | SAP Help Portal.
- Multi-Off Delivery | SAP Help Portal
- 3334794 - Implementing and delivering Extensions in SAP S/4HANA Cloud, public edition using multi-off delivery - SAP for Me
- Provisioning Product: SAP S/4HANA Cloud / System Role: Partner Demo Development
See Also
Developing Extension Items for Extensibility Templates | SAP Help Portal
Preparing for Extensibility Template Development | SAP Help Portal
Keywords
Extensibility templates, extension items, extensibility, SAP Application Services, key user extensibility , KBA , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem