After you maintained authorization object S_TABU_DIS and ACTVT field value 02 as authorization defaults for transaction SM30 in your development system, what would be the correct option for…

The correct answer is B. Save your changes to a Workbench transport request and transport using the Transport. Option B is correct because authorization default data maintained via the profile generator (SU24/SU25) is stored in the customer tables USOBT_C and USOBX_C, which are repository objects treated as workbench data - not client-specific customizing. When you save these changes in…

Identity and Access Management

Question

After you maintained authorization object S_TABU_DIS and ACTVT field value 02 as authorization defaults for transaction SM30 in your development system, what would be the correct option for transporting only these changes to your quality assurance system?

Options

ASave your changes and use the transport interface in SU25 to transport the changes using the
BSave your changes to a Workbench transport request and transport using the Transport
CSave your changes to a Customizing transport request and transport using the Transport
DSave tables USOBT_C and USOBX_C to a transport request and transport using the Transport

How the community answered

(23 responses)

A
4% (1)
B
78% (18)
C
13% (3)
D
4% (1)

Explanation

Option B is correct because authorization default data maintained via the profile generator (SU24/SU25) is stored in the customer tables USOBT_C and USOBX_C, which are repository objects treated as workbench data - not client-specific customizing. When you save these changes in the development system, SAP assigns them to a Workbench transport request, which is then moved to QA via the Transport Management System (TMS/SE09).

Why the distractors are wrong:

A is wrong because SU25's built-in transport interface is used to upgrade/copy SAP standard data into customer tables - it is not the mechanism for transporting your own custom authorization default changes between systems.
C is wrong because Customizing transport requests are for IMG/client-specific configuration. Authorization defaults, despite being client-dependent in practice, are classified as workbench (repository) objects in SAP's transport framework.
D is wrong because you never transport entire tables (USOBT_C / USOBX_C) wholesale - you transport only the specific changed entries recorded in the workbench request, not the full table objects.

Memory tip: Think "Authorization = Always Workbench." Anything touched by the Profile Generator (SU24/SU25) lives in the ABAP repository world → Workbench request. If you see "Customizing" paired with authorization defaults on an exam, it's a trap.

Topics

#authorization defaults#transport management#SU25#workbench transport

Community Discussion

No community discussion yet for this question.

Full C_SEC_2405 Practice