SAP BDL ACTIONS AUTH



Get Example source ABAP code based on a different SAP table
  


• AUTHORIZATION NONE ABAP_BDL_BODY

ABAP_RAP - authorization:none

ABAP_SYNTAX
... (authorization:none) ...

What does it do?
The RAP BO operation addition authorization:none excludes the operation in question from authorization checks. As a prerequisite, authorization control must be defined and implemented.
authorization:none can be used for the following operations:
the standard operations create and delete ABAP_NOTE For the standard operation create, the addition authorization:none is only available in case of global authorization.
operations for associations
actions ABAP_NOTE For static actions, the addition authorization:none is only available in case of global authorization.
determine actions
the draft action Edit
For actions and determine actions, the addition (authorization:none) can be used in authorization master and authorization dependent entities.
For create, delete, operations for associations, and the draft action Edit, this addition can only be used in the authorization master entity.

ABAP_AVAILABILITY
Managed RAP BO
Unmanaged RAP BO
Projection BO. For details, see RAP BDL - authorization, Projection BDEF.
ABAP_AVAILABILITY_END

ABAP_FURTHER_INFO
Development guide for the ABAP RESTful Application Programming Model, section Authorization Definition.



Latest notes:

For details on authorization control in RAP, see topic TITLE .
NON_V5_HINTS
ABAP_HINT_END

ABAP_EXAMPLE_VX5
This example demonstrates the notation in the RAP behavior definition.
Standard operation: delete (authorization:none);
Association: association _MyAssoc { create(authorization:none); }
Action: action (authorization:none) MyAction;
Determine action: determine action (authorization:none) MyDetAction { ... }
Draft action: draft action (authorization:none) Edit;
ABAP_EXAMPLE_END