Get Example source ABAP code based on a different SAP table
ID MODIFY-BEHV-PRIVI ID READ-BEHV-PRIVI ID GET-PERMISSIONS-PRIVI • PRIVILEGED READ ENTITIES • PRIVILEGED READ ENTITY • PRIVILEGED MODIFY ENTITIES • PRIVILEGED MODIFY ENTITY • PRIVILEGED GET PERMISSIONS • PRIVILEGED GET PERMISSIONS OF
ABAP_EML - PRIVILEGED The addition PRIVILEGED is used for a privileged access to a RAP BO, for example, to circumvent authority checks. The addition can only be used if the RAP BO entity is defined with with privileged mode .... See the details in the RAP BDL documentation for with privileged mode. The addition is currently possible for the following ABAP_EML statements:
Short forms
MODIFY ENTITY PRIVILEGED bdef ...
READ ENTITY PRIVILEGED bdef ...
GET PERMISSIONS PRIVILEGED ... ENTITY bdef ...
Long forms:
MODIFY ENTITIES OF bdef PRIVILEGED ENTITY ...
READ ENTITIES OF bdef PRIVILEGED ENTITY ...
GET PERMISSIONS PRIVILEGED ... OF bdef ENTITY ... BEGIN_SECTION VERSION 5 OUT
Dynamic forms:
MODIFY ENTITIES PRIVILEGED OPERATIONS ...
READ ENTITIES PRIVILEGED OPERATIONS ...
GET PERMISSIONS PRIVILEGED ... OPERATIONS ... END_SECTION VERSION 5 OUT
Latest notes: Using the method get_current_context of class CL_ABAP_BEHV_AUX, you can receive context information. Among others, you can determine if the running handler is running in privileged mode, e. g. as follows: cl_abap_behv_aux=>get_current_context( IMPORTING privileged = DATA(priv) ). NON_V5_HINTS ABAP_HINT_END
ABAP_EXAMPLE_ABEXA The example Using the Addition PRIVILEGED with an ABAP_EML Statement demonstrates the addition PRIVILEGED using an action and a managed RAP BO. ABAP_EXAMPLE_END
