Day 5: Derived Roles, Composite Roles, Organizational Values and Role Naming Standards

Detailed Concept Notes

Derived roles help reuse a parent role design while changing organization-level values such as company code, plant or purchasing organization. Composite roles group single roles for user assignment convenience, but poor design can hide risk. In a live project, the important skill is to connect the screen, the business process, the authorization object, the approval trail and the audit evidence. A learner should not memorize only transaction names. They should understand why the user needs access, what can go wrong if the access is too wide and how the final assignment will be defended during audit.

Start every analysis with three questions: who is asking, what business activity are they trying to complete and what risk is created by allowing it. Then move into the system using PFCG, SUIM or AGR_1251 only after the process is clear. This habit prevents random role assignment and builds consultant-level confidence.

A good SAP Security note should always show four layers: business request, technical authorization, control owner approval and evidence. If any one layer is missing, the work may pass a quick test but fail during user review, SoD review, support handover or external audit.

In implementation work, document both the happy path and the exception path. The happy path explains how the user should complete the activity after access is corrected. The exception path explains what to check when the same problem returns after transport, role comparison, user buffer refresh, catalog sync, workflow approval or organizational-level changes.

For support work, never close the issue only because the immediate error disappeared. Verify the user can complete the business activity, confirm no additional risky access was added, record the test evidence and mention the exact object, role, app, catalog, workflow rule or control area that was touched. This is what separates a professional consultant note from a short helpdesk answer.

Real-time scenario: A company has the same sales display access for India and Germany, but each region should see only its own sales organization. A parent role plus derived roles can control this cleanly.

Consultant Deep-Dive Notes

Business Context

Derived Roles, Composite Roles, Organizational Values and Role Naming Standards should be understood from the business user's activity first. In real support calls, the user normally describes a blocked transaction, missing tile, failed approval, denied report or compliance issue. The consultant must translate that symptom into access requirement, process owner approval and technical evidence.

Technical Analysis Pattern

Begin with PFCG, then compare the finding with SUIM and validate using AGR_1251. Do not jump directly into broad role changes. Check user validity, lock status, assigned business role, authorization object values, organization levels, catalog/group assignment, workflow stage and any emergency access context.

Configuration and Design Thinking

A clean design separates display, change, approval, administration and audit access. When the same role contains too many unrelated activities, it becomes hard to troubleshoot, hard to review and risky during SoD analysis. Keep the access model modular, named clearly and mapped to a business owner.

Testing Approach

Test with the exact user type, client, system and process step. A role that works in a test user may fail for the real user if organization levels, parameter values, catalog sync, user comparison, workflow agent rules or backend role assignments are different. Always test the final business action, not only the login or screen opening.

Audit and Control View

Can the role owner explain the role content? Evidence should include request ID, approver, reason, old access state, new access state, test result and review date. This protects the consultant during internal audit, external audit, GRC review and handover to the support team.

Support Troubleshooting View

If the issue repeats, check whether the change was moved by transport, overwritten by role comparison, affected by user buffer, blocked by missing Fiori catalog, restricted by organizational value, delayed by workflow approval or caused by an integration user. This structured path saves time compared with random role additions.

Diagrammatic View

Consultant view Role Design control map

01 Parent role

02 Derived child role

03 Org values

04 Generate

05 Assign

06 Review

Business lane

Requirement, user responsibility, process impact and owner approval.

Security lane

Role, object, field value, trace result, SoD risk and restriction design.

Audit lane

Ticket evidence, review note, expiry date, logs and exception approval.

PFCGSUIMAGR_1251AGR_USERSPFUD

Step-by-Step Implementation Playbook

Identify which values vary by organization. Capture the request, approver and business reason before proceeding.
Keep parent role clean and stable. Validate the SAP screen result and compare it with the expected business action.
Create derived roles for org-specific values. Document the before/after state so the next support person can understand the change.
Avoid creating large composite roles that no one can explain. Capture the request, approver and business reason before proceeding.
Review composite role content before assignment. Validate the SAP screen result and compare it with the expected business action.
Document naming convention and owner. Document the before/after state so the next support person can understand the change.

Process Flow

Parent roleDerived child roleOrg valuesGenerateAssignReview

Comparison and Consultant Mapping Table

Area	Meaning	Consultant Tip
Single role	Real authorization container	Best unit for access control.
Derived role	Same menu, different org values	Useful for regional/company-code design.
Composite role	Bundle of single roles	Convenient but can become too broad.
Business role	Job responsibility grouping	Should map to real work performed.

Real Project Workbook

Work Item	What To Capture	Why It Matters
Requirement	A company has the same sales display access for India and Germany, but each region should see only its own sales organization. A parent role plus derived roles can control this cleanly.	Write the exact business action in one line.
System check	Use PFCG, SUIM, AGR_1251 as the starting toolset.	Capture user, client, role/app and timestamp.
Risk check	Can the role owner explain the role content?	Confirm SoD, sensitive access or audit impact.
Resolution	Document naming convention and owner.	Retest with least privilege, not broad access.
Evidence	Create a role naming format for module, process, activity, region and environment.	Store notes in a ticket or access request record.

Consultant Field Notes

Do not treat role design as an isolated topic. It connects with user lifecycle, role design, SoD risk, approvals and ongoing monitoring.
When discussing this with a functional consultant, use business words first and SAP technical words second. For example, explain the process impact, then mention the related transaction, role or object.
Keep a small evidence pack for every important change: request reason, approver, role/user before state, role/user after state, trace or testing result and rollback note.
Watch these focus areas carefully: Single role, Derived role, Composite role. They usually decide whether the design is clean or risky.
For interviews, answer with a real sequence: requirement, analysis, transaction/tool, correction, testing and documentation. This sounds more practical than only defining the term.

Screen and Visual References

PFCG

Use this as the main starting screen for analysis.

SUIM

Compare the result with business requirement and role design.

AGR_1251

Capture proof for audit, support handover and interview learning.

Screenshot reference: PFCG main screen or equivalent SAP Fiori/BTP screen.
Capture: request/role/user/action context without exposing client-sensitive data.
Diagram: show where authorization, approval, risk or audit evidence fits in the process.

Best Practices

Can the role owner explain the role content?
Are org values appropriate for the user's job?
Is the composite role hiding conflicting access?
Are derived role changes controlled?

Common Mistakes

Using composite roles as dumping grounds.
Manually changing derived role menu incorrectly.
Not regenerating derived roles after parent changes.
Role names that do not reveal module, action or restriction.

Troubleshooting Guidance

When a derived role fails, compare the parent and derived role, check inherited menu, org values, generated profile and user comparison.

Interview Questions

When should derived roles be used?
What is the risk of composite roles?
How do naming standards help support teams?

Practice and Interview Bank

Create a role naming format for module, process, activity, region and environment.

Explain Derived Roles, Composite Roles, Organizational Values and Role Naming Standards to a business user in simple process language.
List the main SAP screens or tools you would open first: PFCG, SUIM, AGR_1251, AGR_USERS.
Write a ticket update for this scenario: A company has the same sales display access for India and Germany, but each region should see only its own sales organization. A parent role plus derived roles can control this cleanly.
Create a before/after evidence checklist for the change.
Mention two risks if the consultant gives broad access instead of controlled access.
Prepare one interview answer using this sequence: requirement, analysis, transaction, fix, test and evidence.
Create one audit question and answer for this topic.
Write one resume bullet showing practical work on this topic.
Identify one common mistake and how you would prevent it.
Create one mini test case that proves the business activity works after correction.