Developing authorizations for business users in SAP Business AI Platform, ABAP environment
A Devtoberfest 2026 session that walks the places an authorization check has to be written when a RAP business object is implemented, which is the whole of the authorizationAuthorizationDeciding who may read or change what, at service, entity and instance level — role checks, forwarded user context, and restrictions evaluated as query filters rather than after the fact.SAP and community, unassessed edge: read restrictions as DCL access controls that become a filter at query time, a child entity inheriting its parent's conditions through an association, the projection layer inheriting rather than changing them, and the same check repeated on the draft side. The ABAP CDSABAP CDSThe modelling layer of ABAP Cloud — view entities, projections and annotations defined above database tables, delivered with the platform rather than installed.sap official, abap edge holds on that draft half — until 2608 a draft query view was needed above the draft table so a DCL had something to attach to, while a draft table entity is already on CDS level and takes the DCL directly, as long as the associations used in the inherited conditions are redefined on it. Create, update and delete are then taken handler by handler, including the trap that instance authorization reads the buffer and so cannot see the new value a pre-check would reject, and the session closes on in local mode and privileged EML calls.
Where it sits
Who is behind it
In the atlas: contributes to 19, wrote 5@anfiscauthor
Properties
About this work
For authorization
Details
Graph
Source
History
- Entered the atlasDiscovered via YouTube — SAP Developers playlists · devtoberfest-2026.
For your agent
- Ref
content:devtoberfest-2026-rap-authorizations-business-users- JSON
- /content/devtoberfest-2026-rap-authorizations-business-users.json
- MCP
- Connecting an agent