SAP Community - ABAP RESTful Application Programming Model

Extending S/4HANA Standard Event Header with SalesOrderType (AUART) for Event Mesh routing

2026-06-02T20:50:32.497000+02:00

Hi SAP Community,

I am working on an event-driven architecture using SAP S/4HANA and SAP Advanced Event Mesh and need some guidance on event extensibility -- unfortunately I did not find many information.

My business requirement is the following: "I want to implement event routing based on the sales order type (AUART) and the consumer destination, so that each system receives only the statuses applicable to its scope."

To achieve this via AEM topic subscriptions (wildcards), I need the SalesOrderType / AUART field to be present in the Header / Topic, not just inside the data payload.

I attempted to extend the standard event (sap.s4.beh.salesorder.v1.SalesOrder.Created.v1) using a Metadata Extension to apply the @event.context.attribute annotation. However, the underlying standard RAP BO (R_SALESORDERTP / D_SalesOrderCreated) does not have the @Metadata.allowExtensions: true annotation, which blocks this approach.
I also considered creating a custom RAP Event from scratch, but I've failed so far and did not find a good tutorial to help me on this.

My Questions:

What is the recommended Clean Core compliant approach to promote a payload field (SalesOrderType) into the Header?
Is it recommended to use BAdIs to intercept and enrich the header dynamically before it is dispatched? Or would it be more appropriate to create a custom event using the classic BOR approach?

Any advice, insights, or documentation references would be highly appreciated!

Thank you in advance.

How to extend manage customer line items app in clean core way to add other standard logical fields

2026-06-11T20:37:37.080000+02:00

Hello,

Another blocker of clean core way.
We are trying to extend the manage customer line items app to have few more fields from other data sources .

extending the i_arlineitem cds view with those fields does not reflect in the data source extension of CFL to enable them In app.

we created a custom app on top of i_arlineitem which is released C0 contract . Now the issue we are facing is in ATC check level 2 warning of “Usage of internal API” is coming and blocking this custom app way also .

Can anyone please help in adding other data source field in this manage customer line app or help in fixing that atc check .

No preview generated for RAP Application in ADT

2026-06-12T06:25:59.380000+02:00

App previewHello Gurus,

I can't see preview of my demo RAP application i created on ADT.

After scouring the app in ADT and inspecting the preview, few places where i found the issue is:

1) during the $metadata?sap_client call available in the network section of the inspect element

2) SQL error "SQL code: 1024" occurred while accessing table "AGR_USERS", available in the Feed Reader section of ADT.

The question here is, are these the real causes SAP is not generating the preview? Or, is it due to the downtime for the backend btp instance ?

While searching for the solution, one user had suggested to delete the current btp instance and re-create it for a new region. Is this a valid workaround? If this is case, probably, i will have to re-create my app from ground-up....

So guys, any other suggestions?

Best Regards....

Recommended naming convention for custom objects in ABAP Cloud

2026-06-12T19:15:28.924000+02:00

Hello SAP Community,

I am working with ABAP Cloud in the context of SAP S/4HANA Cloud Private Edition, and I would like to understand the recommended naming convention for custom development objects.

In classic ABAP development, custom objects are usually created using the Z* or Y* namespace, or a registered customer namespace. However, in ABAP Cloud, I would like to know what the recommended approach is for naming custom artifacts such as:

- Packages
- Classes and interfaces
- CDS views / CDS view entities
- Behavior definitions and behavior implementations
- Service definitions and service bindings
- Metadata extensions

Is there an SAP-recommended naming convention or best practice for these objects in ABAP Cloud?

For example, should we continue using Z*/Y*, use a specific prefix per application/domain, or follow a different convention aligned with Clean Core and ABAP Cloud development guidelines?

Any official SAP documentation, examples, or practical recommendations would be very helpful.

Thank you.

Issue dynamically hiding a column in an adaptation project

2026-06-15T12:13:44.128000+02:00

Hello,

I'm working on an adaptation project for a custom app I've developed in RAP with annotations. My requirement is to hide columns of a table created through annotations according to the value of virtual fields.

Unfortunately as I've seen in other posts that using a boolean virtual element with a LineItem.hidden(#virtelementname) doesn't work, so I've moved to an adaptation project. My approach is to read the virtual fields from the odata4 model through typescript, get the columns from the table through and hide them through setVisible. This is the function that I attach this to the event modelContextChange of the table (the columns are visible for some objects and invisible for others) in the code file generated by the adaptation editor.

	setColumnsVisible = async function (this: ControllerExtension, table: Table ) {
		const bindingContext = this.getView().getBindingContext();
		if (!bindingContext) {
			return;
		}
		const path = `${bindingContext.sPath}`;
		const context : Context = this.getView().getModel().bindContext(path);
		interface VisibilityResponse {Column1Hidden: boolean; };
		const res = await context.requestObject() as VisibilityResponse;
		const columns: Column[] = table.getColumns();
		const columnToHide = columns.find( curr => curr.getPropertyKey().includes("ColumnToHide") );
		columnToHide.setVisible(!res.Column1Hidden);
	};

The result of this is that when Column1Hidden is true the label of the column is hidden but the values are still there. My objective is to hide the whole column including the values.

As a sidenote, just for kicks I tried getting the index of the column, removing it from the table with removeColumn, setting visible to false (on the column) and inserting it back at the right index, it didn't work either. I also tried to call invalidate() on the Table and Column controls after setting the visibility (in case it's evaluated during rendering) and still no luck.

Does anybody have any ideas how to achieve this?

Thanks,

Ben

Error when trying to create a service entry sheet (SES) via i_serviceentrysheettp_2

2026-06-15T22:13:21.393000+02:00

Hello,

I am encountering an error when trying to create a new service entry sheet (SES) with a position and two cost centers in one position (account assignment).
In this case, there are 3 entities involved (header, item, and account assignment).

When I have more than 1 account assignment position, I am always getting the following error:
411 06 Sum of quantities >3,000< larger than total quantity

Although my quantities are okay - 2 in item and 1 + 1 in account assignment positions.

Code example:

METHOD if_oo_adt_classrun~main.

DATA:
ls_header_data TYPE i_serviceentrysheettp_2,
ls_item_data TYPE i_serviceentrysheetitemtp_2,
ls_acc_ass TYPE I_SesAccountAssignmentTP_2,

lt_header_crt TYPE TABLE FOR CREATE i_serviceentrysheettp_2\\serviceentrysheet,
lt_item_cba TYPE TABLE FOR CREATE i_serviceentrysheettp_2\\serviceentrysheet\_serviceentrysheetitem,
lt_acc_ass_cba TYPE TABLE FOR CREATE i_serviceentrysheettp_2\\ServiceEntrySheetItem\_AccountAssignment,
ls_acc_ass_cba LIKE LINE OF lt_acc_ass_cba,
lv_item_cid TYPE string,
lv_accass_cid TYPE string.

m_out = out.

ls_header_data-serviceentrysheetname = 'Demo SES'.
ls_header_data-purchaseorder = '4500001414'.
ls_header_data-sesoriginobjecttype = `EX`.
ls_header_data-PurgDocExternalReference = 'FA163E5F512FEFE199B52BA24E8069BE'.
ls_header_data-PostingDate = '20260527'.

APPEND INITIAL LINE TO lt_header_crt ASSIGNING FIELD-SYMBOL(<ls_hdr_crt>).
<ls_hdr_crt> = CORRESPONDING #( ls_header_data CHANGING CONTROL ).
<ls_hdr_crt>-%cid = `HEADER_1` .

APPEND INITIAL LINE TO lt_item_cba ASSIGNING FIELD-SYMBOL(<ls_itm_cba>).
<ls_itm_cba>-%cid_ref = 'HEADER_1'.

lv_item_cid = |Item_2|.
lv_accass_cid = |Accass_2|.

CLEAR: ls_item_data, ls_acc_ass_cba.
ls_item_data-purchaseorderitem = '00020'.
ls_item_data-confirmedquantity = '2.000'.
ls_item_data-accountassignmentcategory = 'K'.
ls_item_data-multipleacctassgmtdistribution = '1'.
ls_item_data-ServicePerformanceDate = '20260610'.
ls_item_data-ServicePerformanceEndDate = '20260610'.

APPEND INITIAL LINE TO <ls_itm_cba>-%target ASSIGNING FIELD-SYMBOL(<item_data>).
<item_data> = CORRESPONDING #( ls_item_data CHANGING CONTROL ).
<item_data>-%cid = lv_item_cid. " 'Item_1'.

ls_acc_ass_cba-%cid_ref = lv_item_cid.
DATA(lv_accass_cid_2) = 'ACCASS_2_1'.

CLEAR ls_acc_ass.
ls_acc_ass-GLAccount = '0021351301'.
ls_acc_ass-CostCenter = '2000B11020'.
ls_acc_ass-MultipleAcctAssgmtDistrPercent = '50'.
ls_acc_ass-Quantity = '1.000'.

APPEND INITIAL LINE TO ls_acc_ass_cba-%target ASSIGNING FIELD-SYMBOL(<accass_data>).
<accass_data> = CORRESPONDING #( ls_acc_ass CHANGING CONTROL ).
<accass_data>-%cid = lv_accass_cid_2.

lv_accass_cid_2 = 'ACCASS_2_2'.

CLEAR ls_acc_ass.
ls_acc_ass-GLAccount = '0021351301'.
ls_acc_ass-CostCenter = '2000B16110'.
ls_acc_ass-MultipleAcctAssgmtDistrPercent = '50'.
ls_acc_ass-Quantity = '1.000'.

APPEND INITIAL LINE TO ls_acc_ass_cba-%target ASSIGNING <accass_data>.
<accass_data> = CORRESPONDING #( ls_acc_ass CHANGING CONTROL ).
<accass_data>-%cid = lv_accass_cid_2. " 'Accass_1'.

APPEND ls_acc_ass_cba TO lt_acc_ass_cba.

MODIFY ENTITIES OF i_serviceentrysheettp_2
ENTITY serviceentrysheet
CREATE
FROM lt_header_crt
CREATE BY \_serviceentrysheetitem
FROM lt_item_cba
ENTITY ServiceEntrySheetItem
"CREATE
" FROM lt_item_cba
CREATE BY \_AccountAssignment
FROM lt_acc_ass_cba
FAILED DATA(ls_failed_crt)
REPORTED DATA(ls_reported_crt)
MAPPED DATA(ls_mapped_crt).

COMMIT ENTITIES
RESPONSE OF i_serviceentrysheettp_2
FAILED DATA(ls_failed_commit)
REPORTED DATA(ls_reported_commit).

Maybe someone will see an error in my code and provide me a hint. Thank you.

Use nextlink/skiptoken in RAP custom entity

2026-06-16T09:22:22.107000+02:00

Dear all,

is somebody aware of support in RAP for OData's nextlink/skiptoken feature in a custom entity? Ofc one would need to implement parts of it by oneself but I was wondering whether SAP provides an API to facilate the implementation.

Kind regards

Nick

RAP Navigation

2026-06-17T10:01:29.329000+02:00

Hello All,

I had a scenario in which I had to make a column clickable in an RAP list report , and when clicked the control should be navigated to the object page of that column(In my case material).

I browsed the net and found that such functionality is maybe possible by #WITH_NAVIGATION_PATH.I implemented it in the following way

After this , the column indeed became clickable however nothing happens after the click

Anything which I am missing, any annotations, your help is very much appreciated.

Thanks in Advance

RAP - Behavior projection - Error on activating Behavior projection

2026-06-18T19:54:07.341000+02:00

Hi All,

Managed scenario - Created three levels of RAP BO.

Behavior definition is successfully activated however could not able to activate the "Behavior Projection". Follwing is the error under ADT Problem -

The association "_CUSTOMER" cannot be used as a transactional association since the target entity "ZSRA_R_CUSTTP" is not redirected to "ZSRA_C_CUST" in the CDS definition.

define root view entity ZSRA_C_CUST
provider contract transactional_query
as projection on ZSRA_CUSTTP
{
key CustomerId,
      CustomerName,
      CreatedBy,
      CreatedAt,
      LastChangedBy,
      ChdLocalLastChangedAt,
      LastChangedAt,
      /* Assoziationen */
      _project : redirected to composition child ZSRA_C_PRJ
}

------------

define view entity ZSRA_C_PRJ
as projection on ZSRA_R _PRJTP
{
key CustomerId,
key ProjectId,
      ProjectName,
      Project,
      ProjectType,
      Data,
      Exporter,
      CreatedBy,
      CreatedAt,
      LastChangedBy,
      PrjLocalLastChangedAt,
      LastChangedAt,
      /* Associations */
      _customer : redirected to parent /OSGMBH/ ZSRA_C_CUST,
      _sys: redirected to composition child ZSRA_C_SYS

}

------------
define view entity ZSRA_C_SYS as projection on ZSRA_ R_SYS
{
    key ProjectId,
key SystemId,
    key CustomerId,
    SystemName,
    Service,
    Tenant,
    CreatedBy,
    CreatedAt,
    LastChangedBy,
    SysLocalLastChangedAt,
    LastChangedAt,
    /* Associations */
    _project: redirected to parent ZSRA_C_PRJ,
     _customer
}

Behavior Projection –

projection;
strict ( 2 );
use draft;
define behavior for ZSRA_C_CUST alias Customer
{
use create;
use update;
use delete;
use action Edit;
use action Activate;
use action Discard;
use action Resume;
use action Prepare;
use association _project { create; with draft; }
}

define behavior for ZSRA_C_PRJ alias Project
{
use update;
use delete;
use association _customer { with draft; }
use association _sys { create; with draft; }
}
define behavior for ZSRA_C_SYS alias System
{
use update;
use delete;
use association _project { with draft; }
use association _customer { with draft; } <-- Error
}

Thanks & regards

Shobhan Rana

SAP PO 7.5 REST Receiver - Capture HTTP 500 response in Asynchronous Interface and send via alert

2026-06-30T06:17:43.512000+02:00

Hi Experts,

I have an asynchronous interface in SAP PO 7.5 from SAP to D365(proxy to rest) using the REST Receiver Adapter.

When the target REST API (D365) returns HTTP 500, the response contains a useful JSON error like this:

{
"Message": "Receipt processing failed for Purchase Order "5*********"
}
I can see this response in the Message Monitor under the server response, but it is not available as the XI message payload.

My requirement is to automatically send this business error to users by email instead of manually copying it from Message Monitor.

My questions are:

Can SAP PO capture the HTTP 500 response body in a standard asynchronous REST receiver?
Can the REST Result Handler be used to extract the Message field and use it for email notifications?
If not, what is the SAP-recommended approach?

Issue in activating ZDMO_RAP_GENERATOR in ABAP Cloud

2026-07-03T12:21:32.469000+02:00

In Cloud ABAP RAP I have pulled the abapgit files from cloud-abap-rap/README.md at main · SAP-samples/cloud-abap-rap · GitHub.

However, when I try to activate the ZDMO_RAP_GENERATOR I have errors in activation.

Can someone provide a solution to activate the ZDMO_RAP_GENERATOR.

How to make specific fields read-only in an Action Parameter Popup (Abstract Entity) - ABAP 8.16

2026-07-04T04:30:41.729000+02:00

I am working in an ABAP Release 8.16 environment using the RAP (ABAP RESTful Application Programming Model).

I have a requirement where a custom action button on the UI triggers a popup dialog. This popup uses a custom Abstract Entity to define its input parameter fields.

My Requirement:

When the user clicks the action button and the custom abstract entity popup appears, only the "Quantity" field should be editable. Every other field in that structure needs to be read-only.

Here is a simplified version of my Abstract Entity:

@EndUserText.label: 'Action Parameter Popup'

define abstract entity ZC_MyActionParameter

{

@EndUserText.label: 'Material ID'

MaterialID : matnr;

@EndUserText.label: 'Desired Quantity'

Quantity : kwmeng;

@EndUserText.label: 'Plant'

Plant : werks_d;

}

And here is how it's defined in my Behavior Definition (BDEF):

action MyCustomAction parameter ZC_MyActionParameter result [1] $self;

Currently tried creating bdef for abstract entity and make feild readonly but not working

And try to use object readonly UI annotation but is not available in this release

How to use privileged Mode in a RAP Cross-BO Scenario for reading instance Features

2026-07-09T17:09:05.722000+02:00

Hi everybody,

We have created in SAP BTP ABAP Environment two RAP Business Object with the following properties

A business Object ZAK_CommentTP
- Having an authorization context NoCheckWhenPrivileged
- with privileged mode disabling NoCheckWhenPrivileged;
- The key field is called CommentId
A business Object ZAK_MainTP
- enabled for Cross-BO Scenarios source resolved, e.g. there is a field CommentId in the entity.

What we want to achieve is that authorization checks are performed for reading, creating the comments in ZAK_CommentTP.

However, if a user is authorized for an instance of ZAK_MainTP , then he can read and create comments in ZAK_CommentTP which refer to this instance without being explicitly authorized for the ZAK_CommentTP RAP BO.

To achieve this, we have created actions and functions in the behavior of ZAK_MainTP, which then call the corresponding EML statements in ZAK_CommentTP in Privileged Mode.

This works well for creating comments. Here, we have created an action createComment in ZAK_MainTP which uses the operation create-by-association for ZAK_CommentTP and the EML Statement

MODIFY ENTITIES OF ZAK_CommentTP PRIVILEGED

ENTITY CommentHeader

CREATE BY \_CommentChild ….

For Reading the Comments we have created a function which then uses Read Entities OF ZAK_CommentTP PRIVILEGED.

Now, we would like to know when a comment can be deleted. Therefore we can use the EML Statement

GET PERMISSIONS PRIVILEGED ONLY INSTANCE FEATURES OF ZAK_CommentTP ENTITY ….

to get the result of the feature control in ZAK_CommentTP .

The result of this EML Statement is of type structure for permissions result ZAK_CommentTP .

However, there is no possibility of creating a function in ZAK_MainTP which has this as result structure.

So, I am searching for a way to create a function in the behavior for ZAK_MainTP whose parameters are the same as for the get_instance_features method in the ZAK_CommentTP .

Any help and suggestions are welcome

Repeated RAP update of business partner is causing error

2026-07-13T15:32:26.497000+02:00

Hi All,

I'm trying to update tax numbers of business partners using RAP. It is working if there is a single update. If multiple updates I'm trying each with its own commit then the following error is coming.

Parameter IV_X_SAVE is '' for FM BUPA_CENTRAL_CHANGE. It should be 'A'.

Anyone faced this error. Any solution for this.

Aravind

In RAP how to filter an association via button

2026-07-14T16:42:48.019000+02:00

Hello All,

I do not find any answer online. So I hope you can help me out.
I got a RAP app which contains of some CDS Views in parent child relation and some "normal" associations.
Each Entity has its own UUID and a reference to the root entity.
This root UUID is used to associate to a foreign CDS and all entries are displayed within all entities.
I now want one button which takes the UUID of the specific entity and filters the data of the association accordingly
A short coding example

define root table entity rootEntity
{
  key key  : key;
      uuid : uui;

      @ObjectModel               : {
        sort.enabled             : false,
        filter.enabled           : false
      }
      _Child : composition of exact one to many children;
     
      @ObjectModel               : {
       sort.enabled              : false,
       filter.enabled            : false
      }
      _foreign : association of exact one to many foreigns on $projection.uuid = _Activities.uuid_root_reference;
}

Child

define table entity child
{
  key parent_key : key;
  key key        : key;
      uuid       : /uuid;

      @ObjectModel:{
        sort.enabled: false,
        filter.enabled: false
      }
      _parent : association to parent parent on $projection.parent_key = parent.key;
      
}

on Consumption level

root

define root view entity c_parent
  provider contract transactional_query
  as projection on parent

{
  key     key   as Key,
          uuid  as UUID,
          @ObjectModel:{
             sort.enabled: false,
             filter.enabled: false
           }
          _Child : redirected to composition child c_children;

          @ObjectModel:{
            sort.enabled: false,
            filter.enabled: false
          }
          _foreign : redirected to c_foreign

}

child

define view entity c_children
  as projection on children

  association of exact one to many c_foreigns as _foreigns on $projection.parentUUID = _foreigns.UUIDRootReference

{
  key key as Key,
  key parent_key as ParentKey,
      _parent.uuid as parentUUID,
      uuid,
         
      _parent : redirected to parent  c_parent,
      _foreigns
  
}

in parent and child bdef I now want to have this:

 action (features : instance) filterByUUID result [0..*] entity c_foreigns;
side effects {
    action filterByUUID affects entity _foreigns;
  }

The foreigns association is linked as line item reference and does not contain a filterbar.

{
        id                : 'Foreigns',
        purpose           : #STANDARD,
        position          : 10,
        label             : 'Foreigns',
        type              :  #LINEITEM_REFERENCE,
        targetElement     : '_foreigns'
      },

In coding i want somethind like this:

READ ENTITIES OF parent IN LOCAL MODE
      ENTITY parent
      FIELDS ( uuid )
      WITH CORRESPONDING #( keys )
      RESULT DATA(lt_parents).

        LOOP AT keys ASSIGNING FIELD-SYMBOL(<ls_key>).

          LOOP AT lt_parents REFERENCE INTO DATA(lr_parent).

            SELECT
              *

            FROM
              foreigns

            WITH PRIVILEGED ACCESS

            WHERE
              uuid_root_reference = @LR_parent->uuid

            APPENDING TO TABLE
              @result.


          ENDLOOP.

      ENDLOOP.

any hint how to achieve that I can filter the foreigns for the current entities uuid would be nice.
Thank you in advance and best regards.

Matthias

Is it possible to dynamically determine OAuth Client ID and Client Secret in SAP PI/PO REST Adapter?

2026-07-19T12:20:11.927000+02:00

Hi everyone,

I have a requirement in SAP Process Integration / Process Orchestration (SAP PI/PO 7.5) and would appreciate your guidance on the recommended approach.

We are using the REST Receiver Adapter with OAuth 2.0 Client Credentials Grant to call an external REST API.

The communication channel is configured with OAuth authentication, where the following parameters are maintained statically in the receiver communication channel:

OAuth 2.0 Client Credentials Grant
Authorization Server URL
Scope
Client ID
Client Secret

The current design works correctly. However, we have a scalability requirement.

Current Requirement

We need to integrate approximately 30 different company codes.

Each company code has:

Its own Client ID
Its own Client Secret
The same OAuth flow and API structure

At the moment, because the OAuth credentials are maintained in the communication channel, we would need to create separate PI/PO configurations for every company code.

This would result in maintaining approximately:

3 ESR objects per company code
3 Communication Channels per company code

For around 30 company codes, this means maintaining approximately 90 ESR objects and 90 Communication Channels, which significantly increases implementation effort and ongoing maintenance.

What we are looking for

We would like to know whether there is a standard SAP-supported approach to dynamically determine the OAuth Client ID and Client Secret at runtime based on the incoming company code (or another business parameter), instead of maintaining separate communication channels.

Some possible approaches we were considered are:

Dynamic Configuration
Adapter Modules
Java Mapping
User-Defined Functions
Lookup from a database or secure credential store
Any other SAP-recommended mechanism

Questions

Is it possible to make the Client ID and Client Secret dynamic in the PI/PO REST Receiver Adapter?
Can the REST Adapter retrieve OAuth credentials dynamically during runtime?
Has anyone implemented a similar scenario where multiple business entities use different OAuth credentials while minimizing the number of communication channels?
What would be the SAP-recommended best practice for this type of requirement?

Our goal is to keep the solution scalable and maintainable while following SAP best practices and avoiding a large number of ESR objects and Communication Channels.

Any implementation experience, SAP Notes, blogs, or documentation references would be greatly appreciated.

Thank you!

Praveen de Silva

Problem with discarding entity using CAP as a proxy of RAP V4 Service

2026-07-20T10:05:47.997000+02:00

Hello Experts,

i've built an App on the Public Cloud, using RAP V4 Service for data persistence and also using determinations, validations etc.
I'm then using a CAP Service to add custom functionality with accessing external/SAP API's. I added my RAP V4 Service using basic entity projection and a little more complicated event handlers. Most of it works good when consumed by Fiori Elements App, but i am facing an issue, where i discard the entity i am editing (not when creating), it successfully discard its, but then fails to read and rebind to the "active" Entity.

From the UI Console and Network Tab, aswell as debugging for hours i'm certain that the discard action works, but the two GET requests fired by FE are running on errors.

My guess to what happens is, that the Draft is discarded before the Read triggers, therefore Entity with "isActiveEntity"=false cannot be accessed and the query fails. The weird thing about that is, that this should be dafault Draft Logic and works everywhere else. So i feel like i am missing something.

Also i am not using @odata.draft.enabled, because that would then use the CAP Default but we have all our data on the RAP Service and need to proxy the requests the way i do (please correct me if i'm wrong here).

Help is greatly appreciated and i will provide any further information you might need.

Cheers, Henrik

F1861 - Display Supplier List : Change Responsive Table to Grid Table Using Adaptation Project.

2026-07-20T15:27:26.939000+02:00

Hi Experts,

I am working on standard Sap Fiori app F1861 In S/4 Hana 2022 FPS02. Business wants to replace the responsive table with a grid table so user can a horizontal scrollbar and view all columns at ones. I tried changing the table type from all responsive to grid using an adaptation project, and also tried controller extension and manifest change, but the app fails at runtime with error

"getTable().setFixedLayout is not a function",

and doesn't load properly. I also checked SAP KBA 3460918, and it says F1861 uses a responsive table by design, and no horizontal scroll is provided. Is there any officially supported way to change it to a grid table, maybe via CDS annotation or a sap note? Any guidance would be appreciated.

SAPUI5 SAP Fiori SAP Fiori Elements

How can I deploy an SAP RAP application for third-party users without providing SAP credentials?

2026-07-22T08:57:42.134000+02:00

Hi Experts,

I have developed an application using the ABAP RESTful Application Programming Model (RAP) on SAP S/4HANA Public Cloud.

My requirement is to make this application accessible to third-party users (such as vendors or customers) without creating SAP user accounts or sharing SAP credentials.

For example, I want to build a vendor portal where external vendors can:

View RFQs assigned to them.
Submit quotations.
Update the status of their responses.

The business users do not want external users to log in directly to SAP.

I would like to understand the recommended approach for this scenario:

What is the best architecture for exposing a RAP application to external users?
Can SAP Build or SAP BTP be used as the frontend while RAP remains the backend?
Should I expose RAP business objects using OData/REST APIs and implement authentication using SAP Cloud Identity Services (IAS) or OAuth?
Are there any SAP-recommended best practices or reference architectures for this use case?
How are security, licensing, and authorization typically handled for external users?

If anyone has implemented a similar solution or can share documentation or architecture diagrams, I would greatly appreciate your guidance.

Thank you!
Omkar

What SAP's Standard RAP Applications Can Teach Every ABAP Developer (S/4HANA 2023)

2026-07-22T17:19:33.979000+02:00

Target Audience: Intermediate to Advanced SAP ABAP Developers

Prerequisites:

SAP S/4HANA 2023, ADT (ABAP Development Tools), Basic RAP knowledge, CDS Views, Fiori Elements

Introduction

Most RAP tutorials demonstrate how to create a Business Object from scratch. But there is a much better teacher: SAP itself.

Every new release of SAP S/4HANA contains hundreds of applications built using the same RAP framework that customers use for custom development. Instead of treating them as black boxes, we can study their architecture to understand how SAP engineers design scalable, upgrade-safe business applications.

This article explains a systematic approach to exploring standard RAP applications in SAP S/4HANA 2023 and highlights practical design patterns that you can adopt in your own projects.

Why Study Standard Applications?

Imagine two developers.
Developer A learns RAP by following tutorial examples.
Developer B studies production applications built by SAP.
Who is likely to write better enterprise software?

Production applications solve problems that tutorials rarely cover:

Large data volumes
Performance
Authorization
Extensibility
Maintainability
Upgrade stability
Multi-user consistency

Studying SAP's design decisions helps you understand not just how RAP works, but why it is structured the way it is.

Finding a Standard RAP Application

The first challenge is determining whether a Fiori application is RAP-based.
A practical starting point is the SAP Fiori Apps Reference Library. Applications implemented as transactional SAP Fiori elements with OData V4 service bindings are strong candidates, although some Fiori elements applications are still based on older frameworks such as SADL/Gateway. Always verify the implementation details in your system.

Example:

This path reveals almost the complete RAP architecture.

Lesson 1 — Separate Data Model from UI

One of the first observations is that SAP rarely exposes database tables directly.

Instead, several CDS layers are used.

Example structure:

Database Table-->Interface CDS-->Projection CDS-->Service Definition

Why?

Because each layer has a distinct responsibility.

Layer	Purpose
Database	Physical persistence
Interface CDS	Business semantics
Projection CDS	UI/API exposure
Service	External contract

This separation allows SAP to evolve the backend while keeping public APIs stable.

Lesson 2 — Keep Business Logic Out of the UI

A common beginner mistake is putting validations in UI code.

SAP instead keeps business rules inside the Behavior Implementation.

Examples include:

Validation
Determination
Default values
Authorization checks
Actions

The UI simply consumes the service.

Benefits include:

Reusable APIs
Consistent validation
Easier testing
Cleaner architecture

Lesson 3 — CDS Does More Than Read Data

Many developers initially think of CDS as an SQL replacement.

Standard applications demonstrate that CDS also provides:

Semantic modeling
Associations
Calculated fields
Value helps
Search configuration
UI metadata through annotations

The result is a richer domain model that reduces imperative coding.

Lesson 4 — Projection Views Protect Internal Objects

A common question is:

Why doesn't SAP expose the interface view directly?

The answer lies in encapsulation.

Projection views define exactly what consumers can see.

Benefits include:

Hide technical fields
Rename fields for consumers
Restrict operations
Simplify future changes

Think of them as the public API of your business object.

Lesson 5 — Behaviors Describe Capabilities

Behavior Definitions communicate what an application supports.

Typical capabilities include:

Create
Update
Delete
Locking
Draft
Actions
Validations
Determinations

This declarative approach allows the RAP runtime to orchestrate transactional behavior consistently.

Lesson 6 — Think in Business Objects, Not Tables

Traditional ABAP development often starts from tables.

RAP encourages a business-object-centric mindset.

Instead of asking:

Which table should I update?

Ask:

Which business object owns this transaction?

This shift improves consistency and aligns with domain-driven design principles

Lesson 7 — Favor Composition Over Joins

In many standard RAP models, parent-child relationships are represented through compositions rather than arbitrary joins.

Example:

Compositions provide:

Lifecycle management
Transaction consistency
Cleaner navigation
Better draft handling

Lesson 8 — Services Are Intentionally Small

Another interesting observation is that SAP often exposes focused services rather than one large "everything" service.

Instead of:

Sales API

You may find multiple services dedicated to specific business scenarios.

Advantages:

Better security
Easier maintenance
Lower coupling
Smaller payloads

Lesson 9 — Design for Extensibility

SAP standard applications are built with extension in mind.

Rather than modifying delivered objects, customers are expected to:

Extend CDS views
Use released APIs
Add custom fields
Implement enhancement points where available

This aligns with the Clean Core strategy for upgrade-safe extensions.

Lesson 10 — The Framework Does More Than You Think

When you press Save in a RAP application, much more happens than a simple database update.

A simplified flow looks like this:

A Practical Exploration Checklist

When studying a standard RAP application, consider the following questions:

Which CDS entity is the root?
Which projection view is exposed?
What behavior is implemented?
Which actions are available?
Where are validations implemented?
Is draft enabled?
How are associations modeled?
How is authorization handled?
What extension points are provided?
Which service binding exposes the API?

Documenting your observations builds a valuable reference for future projects

Key Takeaways

Studying SAP's standard RAP applications is less about copying implementations and more about understanding architectural decisions.

Some recurring principles include:

Layered CDS architecture
Business-object-centric design
Declarative behaviors
Focused service contracts
Encapsulation through projections
Upgrade-safe extensibility
Consistent transaction management

By adopting these practices, custom RAP applications become easier to maintain, extend, and evolve alongside future SAP releases.

Conclusion

RAP is not merely a framework for generating CRUD services. It embodies a set of architectural patterns that SAP applies across modern SAP S/4HANA applications.

The next time you encounter a standard Fiori application, don't stop at using it. Open it in ADT, trace its service binding, inspect its CDS layers, and study its behavior model. Every standard application is an opportunity to learn from production-grade engineering.

You may discover that the best RAP tutorial is already installed in your SAP system.