ABAP Addition 1 ... WITH AUTHORITY-CHECK> 2 ... WITHOUT AUTHORITY-CHECK>
What does it do? These additions control the authorization checks when the statement CALL TRANSACTION>> is executed.
Latest notes: The use of the statement CALL TRANSACTION> without one of the additions WITH AUTHORITY-CHECK> or WITHOUT AUTHORITY-CHECK> is obsolete>. ABAP_HINT_END
ABAP Addition
What does it do? If this addition is specified, the authorization of the current user to execute the called transaction is checked using the following authorization objects> before the transaction call is executed:
The authorization object S_TCODE>.
Any authorization object specified in the definition of the transaction code (transaction SE93>>). Fields of the authorization object for which no value is specified here are not checked. If no authorization exists, a catchable exception of the class CX_SY_AUTHORIZATION_ERROR> is raised.
Latest notes: The use of the addition WITH AUTHORITY-CHECK> is the recommended method of checking the authorizations of the current user. It replaces the preceding checks using the statement AUTHORITY-CHECK>>, the function module AUTHORITY_CHECK_TCODE> >, and checks that depend on the content of the DDIC database table TCDCOUPLES>>. ABAP_HINT_END
ABAP Addition
What does it do? If this addition is specified, the authorization of the current user to execute the called transaction is not checked.
Latest notes:
The addition WITHOUT AUTHORITY-CHECK> indicates explicitly that no authorization check is necessary for the transaction call. It prevents the corresponding error message from the security test> in the extended program checks >.
If the addition WITHOUT AUTHORITY-CHECK> is specified, the content of the DDIC database table TCDCOUPLES >> is ignored. ABAP_HINT_END