ABAPEML_PRIVILEGED - EML PRIVILEGED

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

- 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 CDS BDL documentation for with privileged mode.

The addition is currently possible for the following 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 ...

• Dynamic forms:

• MODIFY ENTITIES PRIVILEGED OPERATIONS ...

• READ ENTITIES PRIVILEGED OPERATIONS ...

• GET PERMISSIONS PRIVILEGED ... OPERATIONS ...

Note

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) ).

The example Using the addition PRIVILEGED with an Statement demonstrates the addition PRIVILEGED using an action and a managed RAP BO.

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3418 Date: 20230201 Time: 103415     sap01-206 ( 37 ms )