Extensibility covers a broad spectrum of topics that allows customers to adopt standard business software to their business needs, such as UI/forms/report layout adoption, custom fields, custom business objects and logic, etc. Customer extensibility in SAP S/4HANA Cloud (and SAP Marketing Cloud) is done in a Q environment and transported to the P environment. However, partners and enterprise customers with many Q/P environments need a possibility to distribute extensibility content across multiple Q/P environments.
To address this gap, SAP provides a light-weight process for SAP S/4HANA Cloud called extensibility templates. With extensibility templates you can collect extensibility items (such as custom fields, business logic implementation, …), export their metadata in a file (“template”), and import this file into another SAP S/4HANA Cloud quality tenant.
As a template provider, you can:
- Create and change extensibility items in a dedicated namespace for all extensibility items enabled for foreign namespace development. Namespaces / prefixes are used to separate extensibility objects from the core objects and between different extending parties.
- Combine extensibility items to create a file and download the template file and present it to a template consumer.
- Download an installation file to enable the template consumer to import extensibility items developed in a dedicated namespace.
As a template consumer, you can:
- Register foreign namespaces from template provider with an installation file.
- Import extensibility templates from a template provider and publish them to your system.
- For transfer between Dev/Q environments, import into P environment is not possible.
- After the import, the consumer has the “ownership” of the objects. SAP is not involved in the relationship between provider and consumer (e.g. no protection of IP, there is no special support process for extensibility items that were imported via templates, …)
- Templates can be used in higher versions of SAP S/4HANA Cloud (version compatibility requirements defined by the export/import service)
- During activation in the Q environment, apps may be blocked
- Change and adapt the imported extensibility items to meet your requirements.
- After the import of the template, the imported objects can be adopted, patched, deleted, etc. in the consumer Q environment (using the key user tools)
- Objects imported once cannot be imported again
- Export imported extensibility items to the production system. Transport from Q to P is done with the existing Export/Import Software Collection apps (“ATO”). , see here the link to the documentation for SAP S/4HANA Cloud: )
New Fiori Apps
SAP provides three new Fiori apps to support template development and consumption.
- Extensibility Settings: In this app, you can prepare your system for template development, export and import; this means, for example, manage your namespace settings (in Business Catalog Extensibility Settings, SAP_CORE_BC_EXT_SET)
- Export Extensibility Template: In this app, you can collect extensibility items (such as custom fields, business logic implementation, …) into a template and export the template file. (In Business Catalog Extensibility Templates – Export, SAP_CORE_BC_EXT_EIT_EXP)
- Import Extensibility Template: In this app, you can import the template file and publish the extensibility items (in Business Catalog Extensibility Templates – Import, SAP_CORE_BC_EXT_EIT_IMP)
As of 1908 version, the following extensibility types are supported
- Custom fields
- Custom logic (BAdI implementations)
- Custom business objects
- Custom code lists and custom reuse libraries
Further extensibility types, for example Custom CDS views and Custom analytical queries shall follow in subsequent releases.