Which optional components can be included when transporting a role definition from the development system to the quality assurance system? Note: There are 3 correct answers to this question.

Question

Options

• ADirect user assignments
• BGenerated profiles of dependent roles
• CGenerated profiles of single roles
• DIndirect user assignments Personalization data

• A
  74% (20)
• B
  26% (7)

Explanation

When transporting a role in SAP (via transaction PFCG), three optional components can be included alongside the role definition itself: direct user assignments (A), which are the users explicitly assigned to the role; generated profiles of single roles (C), which are the authorization profiles automatically generated for the role; and indirect user assignments and personalization data (D), which covers users assigned via organizational management and any user-specific settings.

Option B (Generated profiles of dependent roles) is incorrect because a composite role's dependent single roles are separate objects - their profiles belong to those individual single roles and must be transported independently as part of those roles, not as an optional component of the parent composite role transport.

Memory tip: Think "what is owned by this role vs. what belongs to other roles." A single role owns its own profile (C), its direct user list (A), and personalization/indirect assignments (D) - all transportable optionally. But a composite role does not own the profiles of its child roles (B); those profiles live with the child roles themselves.

No community discussion yet for this question.