1. User Gets “You Are Not Authorized to Use Transaction”
Issue: User cannot run T-code after role assignment.
Root Cause: Missing authorization object ACTVT value.
Fix:
-
Run SU53 immediately.
-
Identify missing authorization object.
-
Maintain correct ACTVT value in PFCG role.
-
Regenerate role and perform user comparison.
SU53 shows the last failed authorization check for a user, helping identify missing objects quickly.
Role & Authorization Issues
2. SU53 Shows No Authorization Error
Issue: User gets error but SU53 is blank.
Root Cause: Error occurred on different application server.
Fix:
Use STAUTHTRACE or ST01 trace to capture authorization checks.
3. Authorization Error After S/4 Upgrade
Issue: Transaction working in ECC fails in S/4.
Root Cause: New implicit authorization checks after upgrade.
Fix:
Check SE97 or TCDCOUPLES table and maintain correct authorization settings.
4. SU24 Proposal Missing Authorization Object
Issue: Authorization object not proposed in role.
Fix:
Maintain authorization object in SU24 and regenerate role.
5. Authorization Object Exists but Still Fails
Issue: Authorization object assigned but access denied.
Root Cause: Incorrect field values.
Fix:
Check SU53 → update field values in PFCG.
6. User Has SAP_ALL but Still Cannot Access
Issue: Access denied despite SAP_ALL profile.
Root Cause: Authorization buffer issue.
Fix:
Run SU56 → Reset User Buffer.
7. Authorization Object with “Do Not Check” Still Checked
Issue: Authorization fails despite SU24 set to "Do Not Check".
Fix:
Check USOBX_C configuration and transport corrections.
8. Missing Authorization Object Appears in SU53 but Object Doesn't Exist
Issue: SU53 shows unknown object.
Fix:
Run STAUTHTRACE to identify real authorization check.
Fiori Security Issues
9. Fiori Tile Not Visible
Root Cause: Missing catalog or group assignment.
Fix:
Assign catalog in Fiori role via PFCG.
10. Fiori App Opens but Authorization Error Appears
Root Cause: Missing OData authorization.
Fix:
Maintain S_SERVICE authorization object.
11. Fiori Catalog Not Loading
Root Cause: Missing Fiori user roles.
Fix:
Assign roles:
-
SAP_UI2_USER_700
-
SAP_UI2_USER_750
12. Launchpad Loads but No Tiles Visible
Root Cause: Missing Fiori group assignment.
Fix:
Add group to role and perform user comparison.
13. Fiori Search Authorization Errors
Issue: SU53 shows many failed checks during search.
Root Cause: Enterprise search authorization checks.
Fix:
Assign missing business object authorization.
PFCG Role Issues
14. Role Generated but Authorization Not Working
Root Cause: Authorization buffer not refreshed.
Fix:
Run PFUD → User comparison.
15. Transported Role Not Working in QA
Root Cause: Missing SU24 entries in target system.
Fix:
Transport SU24 proposals.
16. Authorization Object Greyed Out in PFCG
Root Cause: Maintained via SU24 proposal.
Fix:
Adjust SU24 check indicator.
17. Composite Role Not Working
Root Cause: Child role missing authorization.
Fix:
Check single roles assigned.
18. Derived Role Authorization Not Updating
Root Cause: Parent role changed but derived role not regenerated.
Fix:
Regenerate derived roles.
User Administration Issues
19. User Locked Automatically
Root Cause: Incorrect login attempts.
Fix:
Unlock in SU01.
20. User Roles Not Updated
Root Cause: Buffer issue.
Fix:
Run SU56 reset.
21. New Role Assigned but Access Denied
Root Cause: User comparison not done.
Fix:
Execute PFUD.
RFC Security Issues
22. RFC User Access Denied
Root Cause: Missing S_RFC authorization object.
Fix:
Add function group authorization.
23. RFC Destination Not Working
Root Cause: Incorrect technical user authorization.
Fix:
Maintain roles for RFC user.
24. Critical RFC Authorization Risk
Issue: RFC allows ABAP execution.
Fix:
Restrict access to sensitive function modules.
Some vulnerabilities can allow code injection via RFC if authorization checks are bypassed, which is considered critical.
GRC Related Issues
25. Access Request Not Provisioning Role
Fix:
Check BRM role mapping.
26. Firefighter ID Not Working
Fix:
Check owner assignment.
27. Firefighter Log Not Generated
Fix:
Enable firefighter logging.
SOD Issues
28. Critical Role Assigned to User
Fix:
Perform SOD analysis in GRC.
29. Audit Finding: SAP_ALL Assigned
Fix:
Replace with controlled roles.
30. Direct Table Access Risk
Fix:
Restrict SE16/SE16N authorization.
Transport Security Issues
31. User Cannot Transport Objects
Fix:
Assign S_TRANSPRT authorization.
32. Developer Cannot Modify Object
Fix:
Assign S_DEVELOP authorization.
33. Transport Import Failed
Fix:
Check transport authorization.
Workflow Security Issues
34. Workflow Approval Fails
Root Cause: Missing authorization for WF user.
Fix:
Maintain role for WF-BATCH user.
35. Workflow Stuck in Error
Fix:
Check workflow logs.
Table Access Issues
36. SE16 Access Denied
Fix:
Assign S_TABU_DIS authorization.
37. Table Maintenance Denied
Fix:
Maintain authorization group.
38. SM30 Authorization Failure
Fix:
Assign correct authorization group.
System Security Issues
39. Debug Authorization Risk
Fix:
Restrict S_DEVELOP DEBUG access.
40. Background Job Authorization Error
Fix:
Assign S_BTCH_JOB authorization.
41. User Cannot Schedule Job
Fix:
Maintain S_BTCH_ADM.
Fiori & Gateway Issues
42. OData Service Authorization Error
Fix:
Maintain S_SERVICE object.
43. Gateway Authorization Error
Fix:
Assign SAP_GW_USER role.
44. Fiori App Works in DEV but Not PRD
Fix:
Transport catalog and roles.
HANA Security Issues
45. CDS View Authorization Error
Fix:
Assign proper analytical privileges.
46. Fiori Analytical App Not Working
Fix:
Maintain S_RS_COMP authorization.
Audit Findings
47. Excessive Authorization in Role
Fix:
Apply least privilege principle.
48. Emergency Access Misuse
Fix:
Monitor firefighter logs.
49. Critical Authorization Object Assigned
Example:
-
S_USER_ALL
-
S_DEVELOP
Fix:
Remove from business roles.
50. Authorization Trace Required for Issue
Fix:
Run STAUTHTRACE for detailed analysis when SU53 is insufficient.
✅ These 50 issues are common in real S/4HANA projects and typically come from:
-
Production support tickets
-
Security audits
-
GRC findings
-
Go-live hypercare incidents

No comments:
Post a Comment