What must you do if you want to enforce an additional authorization check when a user starts an SAP transaction?
A.
Assign authorization object S_START to the chosen transaction code with transaction SU24 and specify the Program ID and Object Type.
B.
Assign the authorization object to be checked to the chosen transaction code in the SAP Default authorization data using transaction SU22 and set Check Indicator to "Check".
C.
Assign the authorization object and permissions to the chosen transaction code using transaction SE93.
D.
Assign the authorization object to be checked to the chosen transaction code with transaction SU24 and set Default Status to "Yes".
To enforce an additional authorization check when a user starts an SAP transaction, you must assign the relevant authorization object and its permissions to the transaction code using transaction SE93. This transaction allows you to define or modify the properties of a transaction, including specifying authorization objects that must be checked when the transaction is executed. By linking the authorization object directly to the transaction in SE93, the system enforces the additional check at the point of transaction execution, ensuring that only authorized users can proceed. Transactions SU24 and SU22 are used for maintaining authorization defaults, but they do not directly enforce checks at transaction start, and S_START is specific to Fiori app authorizations, not general transactions.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit