Day 3: Authorization Concept, Objects, Fields, Activities and SU24 Proposal Logic

Detailed Concept Notes

SAP authorization is not simply a list of transaction codes. When a user performs an action, SAP checks authorization objects and fields. Common fields include ACTVT for activity, organizational values such as company code or plant, and object-specific fields such as authorization group or document type. 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 SU24, SU22 or SU53 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 user can open FB03 but cannot display a document for a specific company code. The transaction exists, but the authorization field value is missing. The consultant must identify object and field value, not randomly add roles.

Consultant Deep-Dive Notes

Business Context

Authorization Concept, Objects, Fields, Activities and SU24 Proposal Logic 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 SU24, then compare the finding with SU22 and validate using SU53. 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

Display and change access should be separated where required. 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 Authorization control map

01 User action

02 Transaction/app

03 Authorization object

04 Field values

05 Pass/fail

06 Trace evidence

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.

SU24SU22SU53STAUTHTRACEPFCG

Step-by-Step Implementation Playbook

Start from the failed business action, not only transaction code. Capture the request, approver and business reason before proceeding.
Capture SU53 immediately after failure or run STAUTHTRACE. Validate the SAP screen result and compare it with the expected business action.
Identify object, field and value. Document the before/after state so the next support person can understand the change.
Check if the role already has the object but wrong value. Capture the request, approver and business reason before proceeding.
Avoid manually adding unsupported objects unless design is reviewed. Validate the SAP screen result and compare it with the expected business action.
Use SU24 understanding when building roles from transaction menu. Document the before/after state so the next support person can understand the change.

Process Flow

User actionTransaction/appAuthorization objectField valuesPass/failTrace evidence

Comparison and Consultant Mapping Table

Area	Meaning	Consultant Tip
Authorization object	Groups related checks	Example: accounting, plant, role admin, HR.
Field	Specific control value	Company code, plant, activity, authorization group.
ACTVT	Activity field	01 create, 02 change, 03 display, 06 delete, etc.
SU24	Proposal values	Controls what enters PFCG from a transaction menu.

Real Project Workbook

Work Item	What To Capture	Why It Matters
Requirement	A user can open FB03 but cannot display a document for a specific company code. The transaction exists, but the authorization field value is missing. The consultant must identify object and field value, not randomly add roles.	Write the exact business action in one line.
System check	Use SU24, SU22, SU53 as the starting toolset.	Capture user, client, role/app and timestamp.
Risk check	Display and change access should be separated where required.	Confirm SoD, sensitive access or audit impact.
Resolution	Use SU24 understanding when building roles from transaction menu.	Retest with least privilege, not broad access.
Evidence	Create a sample authorization failure note with object, field, missing value, business impact and proposed fix.	Store notes in a ticket or access request record.

Consultant Field Notes

Do not treat authorization 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: Authorization object, Field, ACTVT. 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

SU24

Use this as the main starting screen for analysis.

SU22

Compare the result with business requirement and role design.

SU53

Capture proof for audit, support handover and interview learning.

Screenshot reference: SU24 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

Display and change access should be separated where required.
Sensitive objects need role owner approval.
Manual authorizations should be explainable.
Proposal changes should follow change control.

Common Mistakes

Thinking transaction access equals full authorization.
Adding all activities when only display is needed.
Ignoring organization-level restrictions.
Treating SU24 as configuration to casually change in production.

Troubleshooting Guidance

If SU53 is empty or misleading, use STAUTHTRACE for the specific user and time window. Check whether the failure is backend authorization, UI restriction or master-data issue.

Interview Questions

What is the difference between transaction code and authorization object?
What is the purpose of ACTVT?
How does SU24 help role build?

Practice and Interview Bank

Create a sample authorization failure note with object, field, missing value, business impact and proposed fix.

Explain Authorization Concept, Objects, Fields, Activities and SU24 Proposal Logic to a business user in simple process language.
List the main SAP screens or tools you would open first: SU24, SU22, SU53, STAUTHTRACE.
Write a ticket update for this scenario: A user can open FB03 but cannot display a document for a specific company code. The transaction exists, but the authorization field value is missing. The consultant must identify object and field value, not randomly add 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.