Your developer has created a new custom transaction tor your sap S/4HANA on-premise system and has provided you a list of the authorizations needed to execute the new ABAP program. What must you do…

Question

Options

• AMaintain each authorization in transaction SU22 and set the Check Indicator value to "Check".
• BMaintain each authorization object in transaction SU22 and set the Default Status to "Yes".
• CMaintain each authorization in transaction SU24 and set the Default Status to "Yes".
• DMaintain each authorization object in transaction SU24 and set the Default Status to "Yes"

• B
  15% (2)
• C
  8% (1)
• D
  77% (10)

Explanation

D is correct because SU24 is the designated transaction for maintaining authorization check indicators and default values for custom (customer-developed) programs. Setting the Default Status to "Yes" on an authorization object tells the PFCG role framework to automatically propose and generate that authorization every time the transaction is inserted into a role - exactly the behavior required.

Why the others are wrong:

• A is wrong on two counts: SU22 is SAP's own maintenance transaction for standard (SAP-delivered) programs, not custom ones, and the "Check Indicator" value controls whether the check occurs at runtime - it doesn't drive automatic proposal in PFCG.
• B uses the right field (Default Status) but the wrong transaction - SU22 is SAP-maintained and not the appropriate place for customer custom transactions.
• C has the right transaction (SU24) but wrong object type - you maintain authorization objects in SU24, not individual authorizations (which are instances of objects with specific field values). Terminology precision matters in SAP authorization.

Memory tip: Think "SU24 = For You (the customer)" - it's your copy of the authorization check data, where you control defaults for your custom transactions. SU22 is SAP's master list; SU24 is your editable layer on top of it.

No community discussion yet for this question.