In Public Cloud both requirements need to be designed using the released Public Cloud extensibility options
For the API requirement, the first option is to use the Custom Fields app. A custom field can be added to the relevant business context and then enabled for the relevant released OData API, provided that the API and business context support custom-field extensibility. After publishing the field the API metadata should be checked again to confirm that the field is available
If the required standard API or business context does not support the custom field the standard API should not be modified directly. In that case, the clean-core approach is to build a custom API using Developer Extensibility / RAP in the SAP S/4HANA Cloud ABAP Environment, based only on released SAP objects
For the ABAP report requirement, this should not be approached as a classic SE38-style ABAP report. In Public Cloud the right solution depends on the business purpose:
for analytical reporting, use Custom Analytical Queries and Services
for an interactive custom report, build a RAP / SAP Fiori elements app
for scheduled or background processing, use an Application Job Catalog Entry and Application Job Template
for external consumption, expose a custom RAP/OData API
In Public Cloud, custom fields can be added to a standard API only where the released API and business context support extensibility. For the ABAP report, the recommended Public Cloud approach is not a classic on-premise ABAP report but a Custom Analytical Query, RAP/Fiori app, Application Job or custom RAP/OData API, depending on the requirement
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.