Day 13: UAR and Access Certification: Periodic Review of User Access

Detailed Concept Notes

User Access Review asks business owners to confirm whether users still need assigned roles. The review is only valuable when owners understand the roles, decisions are recorded and removals are completed. 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 GRC UAR, SUIM or PFCG 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 department changed responsibilities during reorganization. UAR helps identify users who still hold old finance approval roles.

Consultant Deep-Dive Notes

Business Context

UAR and Access Certification: Periodic Review of User Access 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 GRC UAR, then compare the finding with SUIM and validate using PFCG. 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

Who reviewed access? 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 UAR control map

01 Select users

02 Generate review

03 Owner decision

04 Remove/retain

05 Validate

06 Close

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.

GRC UARSUIMPFCGSU01AGR_USERS

Step-by-Step Implementation Playbook

Define review scope and frequency. Capture the request, approver and business reason before proceeding.
Ensure reviewer data is accurate. Validate the SAP screen result and compare it with the expected business action.
Provide role descriptions that business users understand. Document the before/after state so the next support person can understand the change.
Require meaningful comments for critical access. Capture the request, approver and business reason before proceeding.
Track removals until complete. Validate the SAP screen result and compare it with the expected business action.
Report overdue reviews. Document the before/after state so the next support person can understand the change.

Process Flow

Select usersGenerate reviewOwner decisionRemove/retainValidateClose

Comparison and Consultant Mapping Table

Area	Meaning	Consultant Tip
Reviewer	Manager or role owner	Must understand business responsibility.
Decision	Approve/remove/comment	Generic approvals weaken review.
Removal	Actual access cleanup	Review is incomplete without action.
Evidence	Review history	Needed for audit.

Real Project Workbook

Work Item	What To Capture	Why It Matters
Requirement	A department changed responsibilities during reorganization. UAR helps identify users who still hold old finance approval roles.	Write the exact business action in one line.
System check	Use GRC UAR, SUIM, PFCG as the starting toolset.	Capture user, client, role/app and timestamp.
Risk check	Who reviewed access?	Confirm SoD, sensitive access or audit impact.
Resolution	Report overdue reviews.	Retest with least privilege, not broad access.
Evidence	Write a business-friendly description for five SAP Security roles.	Store notes in a ticket or access request record.

Consultant Field Notes

Do not treat uar 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: Reviewer, Decision, Removal. 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

GRC UAR

Use this as the main starting screen for analysis.

SUIM

Compare the result with business requirement and role design.

PFCG

Capture proof for audit, support handover and interview learning.

Screenshot reference: GRC UAR 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

Who reviewed access?
What was approved or removed?
Were overdue reviews escalated?
Were critical roles handled carefully?

Common Mistakes

Reviewers approve everything without checking.
Role descriptions are too technical.
Removal actions are not completed.
Review scope excludes critical access.

Troubleshooting Guidance

If reviewers cannot decide, improve role naming, role descriptions, business process mapping and provide access usage context.

Interview Questions

What is UAR?
Why do access reviews fail in real projects?
How do you make role descriptions business-friendly?

Practice and Interview Bank

Write a business-friendly description for five SAP Security roles.

Explain UAR and Access Certification: Periodic Review of User Access to a business user in simple process language.
List the main SAP screens or tools you would open first: GRC UAR, SUIM, PFCG, SU01.
Write a ticket update for this scenario: A department changed responsibilities during reorganization. UAR helps identify users who still hold old finance approval roles.
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.