Day 20: S/4HANA Security Migration, Simplification and Role Conversion Thinking

Detailed Concept Notes

S/4HANA projects often require role redesign because transactions, Fiori apps, business roles and data models change. A consultant should analyze current roles, usage, simplification impact, Fiori requirements and cleanup opportunities. 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 ST03N 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 legacy ECC role contains many old transactions. During S/4HANA migration, some transactions are obsolete and some processes move to Fiori apps.

Consultant Deep-Dive Notes

Business Context

S/4HANA Security Migration, Simplification and Role Conversion Thinking 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 ST03N. 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

Migration is a chance to remove excessive 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 S/4HANA control map

01 Legacy role

02 Usage analysis

03 Simplification check

04 Fiori mapping

05 Role redesign

06 Testing

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.

PFCGSUIMST03NFiori Apps LibrarySU25

Step-by-Step Implementation Playbook

Collect current role inventory. Capture the request, approver and business reason before proceeding.
Review transaction usage. Validate the SAP screen result and compare it with the expected business action.
Identify obsolete and changed transactions. Document the before/after state so the next support person can understand the change.
Map Fiori apps and catalogs. Capture the request, approver and business reason before proceeding.
Redesign roles by business process. Validate the SAP screen result and compare it with the expected business action.
Run regression testing and SoD analysis. Document the before/after state so the next support person can understand the change.

Process Flow

Legacy roleUsage analysisSimplification checkFiori mappingRole redesignTesting

Comparison and Consultant Mapping Table

Area	Meaning	Consultant Tip
Usage analysis	What users actually use	Helps remove old access.
SU25	Upgrade authorization steps	Important after upgrade/migration.
Fiori mapping	App-based access	Requires frontend/backend design.
Testing	Business process validation	Must involve process owners.

Real Project Workbook

Work Item	What To Capture	Why It Matters
Requirement	A legacy ECC role contains many old transactions. During S/4HANA migration, some transactions are obsolete and some processes move to Fiori apps.	Write the exact business action in one line.
System check	Use PFCG, SUIM, ST03N as the starting toolset.	Capture user, client, role/app and timestamp.
Risk check	Migration is a chance to remove excessive access.	Confirm SoD, sensitive access or audit impact.
Resolution	Run regression testing and SoD analysis.	Retest with least privilege, not broad access.
Evidence	Create a migration checklist for one ECC display role moving to S/4HANA.	Store notes in a ticket or access request record.

Consultant Field Notes

Do not treat s/4hana 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: Usage analysis, SU25, Fiori mapping. 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.

ST03N

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

Migration is a chance to remove excessive access.
Role changes need approval and testing.
Fiori access should be documented.
SoD analysis should be rerun after redesign.

Common Mistakes

Copying ECC roles into S/4HANA without cleanup.
Ignoring Fiori requirements.
No usage analysis.
Underestimating testing effort.

Troubleshooting Guidance

If post-migration access fails, check removed transactions, changed authorization objects, SU25 steps, Fiori service activation and backend role gaps.

Interview Questions

Why should roles be redesigned during S/4HANA migration?
What is SU25 used for?
How does Fiori affect security design?

Practice and Interview Bank

Create a migration checklist for one ECC display role moving to S/4HANA.

Explain S/4HANA Security Migration, Simplification and Role Conversion Thinking to a business user in simple process language.
List the main SAP screens or tools you would open first: PFCG, SUIM, ST03N, Fiori Apps Library.
Write a ticket update for this scenario: A legacy ECC role contains many old transactions. During S/4HANA migration, some transactions are obsolete and some processes move to Fiori apps.
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.