As the data model in ABAP is cross-client, data model enhancements in a multitenancy environment are tricky. However, SAP has implemented a framework where the data model enhancements are predefined and part of the application. Customers can then easily specify its label, tooltip, semantic type etc. in a tenant-specific way.
In this blog, you will get:
By the end, you’ll be equipped with the knowledge to integrate predefined custom fields seamlessly into your application.
Predefined custom fields are defined and created within the development process. This means that the number of fields per type is fixed (e.g. five character fields, three decimal fields etc.). So custom fields are immediately available to the customer without long generation times.
The customer can configure these predefined custom fields to meet their business requirements using the Configure Predefined Custom Fields SAP Fiori app. The configuration includes setting a label, a tooltip, and a semantic type (for example: email address or code list). Other "Custom Fields"-like features, such as translations and code values, are also available. Once the specification is done in the SAP Fiori app, the OData metadata is adjusted to reflect the user’s configuration. The customer can now handle the fields in a similar manner as "Custom Fields" in the SAP S/4HANA Public Cloud Edition. You can find more information in the SAP Help Portal.
Screenshort of "Configure Predefined Custom Fields" fiori appScreenshort of "Configure Predefined Custom Fields" fiori app
The central object required to enable your application is the Predefined Fields Enabling. It's an ABAP repository object that describes the extended endpoints (extension include structure, business object view and consumption views) as well as the predefined custom fields (name, type, length and scale). Once you activate the object, the extensions (database appends as well as CDS extends) which contain the predefined custom fields are automatically generated. Preparation is required before creating the Predefined Fields Enabling. You can find the exact steps to enable your application in the SAP Help Portal.
RESTful ABAP Applications with Predefined Fields EnablingRESTful ABAP Applications with Predefined Fields Enabling
In this schematic diagram, you can see a simplified RESTful ABAP application and how the Predefined Fields Enabling interacts with the application.
Predefined custom fields are not specialized up until the service layer, where the metadata is adjusted automatically. This means that from a technical point of view, all predefined custom fields are automatically hidden in the OData service. Once the customer has configured a predefined custom field, the OData metadata is automatically adjusted. With this, the field is exposed and reflects the customer's configuration.
When integrating your application with an external remote service, in an SAP S/4HANA system, for example, it’s common to consume standard fields exposed by that service. Typically, these remote services are accessed using a Service Consumption Model, which serves as the interface between your SAP BTP ABAP environment application and the external service. Since these services are external, they are not necessarily maintained by your organization. They can either be extended using the Custom Fields SAP Fiori app or developer extensibility, or in a completely different way. In all scenarios, although the extension fields may be propagated through the external service, they are not automatically read, written, replicated, or used in another way. For developers this means that you need to enable your application to ensure these extension fields are properly handled alongside the standard fields during data consumption and processing.
Service Consumption Models with Extension FieldsService Consumption Models with Extension Fields
The support of service consumption models for predefined custom fields requires an enabling. You can find the detailed description on the SAP Help Portal.
Now, you are done! Congratulations!
You successfully enabled your application to support predefined custom fields, and also integrate an external service through a service consumption model.
Please note that this blog has been elaborated by a team of experts. I want to thank Yasmina van Rooij (@YasminavanRooij), Daniel Wachs (@DanielWachs), Robin Pfaff (@Robin-Pfaff) and Georg Wilhelm (@georg_wilhelm) for their extremely helpful contributions.
Feedback, Comments, or Questions:
You’re cordially invited to provide feedback, comments, or questions in the comments section below. Please follow our profiles to get updates when we publish more posts on these topics.
Feel invited to post and answer questions here (https://answers.sap.com/tags/270c4f37-c335-46e1-bfad-a256637d5e26) and read other posts on the topic (https://blogs.sap.com/tags/270c4f37-c335-46e1-bfad-a256637d5e26/).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |