40 Critical SAP Authorization Objects Every Security Consultant Should Know - SAP SECURITY

Practical SAP Security & GRC Tutorials | S/4HANA | SU24 | SU25 | Fiori | GRC

40 Critical SAP Authorization Objects Every Security Consultant Should Know

 

In enterprise systems running SAP, authorization objects play a crucial role in controlling what users can access and perform. While transactions allow users to start programs, authorization objects control what actions users are allowed to execute within those programs.

SAP Security consultants frequently work with authorization objects when designing roles in PFCG, troubleshooting errors using SU53, or analyzing access risks in SAP Governance, Risk, and Compliance within systems such as SAP S/4HANA.

Below are 40 critical authorization objects every SAP Security consultant should understand, along with practical examples.


Financial Accounting Authorization Objects

1. F_BKPF_BUK

Controls posting authorization by company code.

Example:

BUKRS = 1000
ACTVT = 01

User can post financial documents only for company code 1000.


2. F_BKPF_KOA

Controls account type authorization.

Example:

KOART = D (Customer)

3. F_BKPF_GSB

Controls business area authorization.


4. F_LFA1_APP

Controls vendor master maintenance approval.

Example scenario: Vendor creation approval process.


5. F_KNA1_APP

Controls customer master maintenance approval.


6. F_LFA1_BUK

Controls vendor access by company code.


7. F_KNA1_BUK

Controls customer access by company code.


8. F_GL_ACC

Controls G/L account authorization.


Materials Management Authorization Objects

9. M_BEST_EKO

Controls purchasing organization access.

Example:

EKORG = 3000

User can create purchase orders only for purchasing org 3000.


10. M_BEST_WRK

Controls plant access for purchasing.


11. M_MATE_WRK

Controls material master authorization by plant.


12. M_MATE_STA

Controls material master status.


13. M_MSEG_BWA

Controls goods movement type authorization.

Example:

BWART = 101

14. M_RECH_WRK

Controls invoice verification by plant.


15. M_EINK_FRG

Controls purchase order release strategy.


Sales and Distribution Authorization Objects

16. V_VBAK_VKO

Controls sales organization access.

Example:

VKORG = 2000

17. V_VBAK_AAT

Controls sales document type authorization.


18. V_VBAK_AUF

Controls sales order authorization.


19. V_KNA1_VKO

Controls customer master access by sales organization.


20. V_LIKP_VST

Controls shipping point authorization.


Controlling Authorization Objects

21. K_CCA

Controls cost center authorization.

Example:

KOSTL = 5000

22. K_ORDER

Controls internal order authorization.


23. K_PCA

Controls profit center authorization.


Basis and Security Authorization Objects

24. S_TCODE

Controls transaction access.

Example:

TCD = SU01

25. S_USER_GRP

Controls user administration by user group.


26. S_USER_AGR

Controls role maintenance authorization.


27. S_USER_PRO

Controls profile assignment authorization.


28. S_USER_TCD

Controls transaction assignment to roles.


29. S_USER_AUT

Controls authorization profile management.


System Administration Authorization Objects

30. S_RFC

Controls remote function call access.

Example:

RFC_NAME = RFC_READ_TABLE

31. S_TABU_DIS

Controls table access by authorization group.


32. S_TABU_NAM

Controls table access by table name.


33. S_PROGRAM

Controls program execution.


34. S_BTCH_JOB

Controls background job processing.


35. S_BTCH_NAM

Controls job ownership authorization.


36. S_TRANSPRT

Controls transport request authorization.


37. S_DATASET

Controls file access on application server.


38. S_SERVICE

Controls web service access.


39. S_DEVELOP

Controls development object access.

Example:

ACTVT = 02

Allows program modification.


40. S_SPO_ACT

Controls spool request authorization.


How Security Consultants Use Authorization Objects

SAP Security consultants typically work with these objects during:

Role design

Roles created in PFCG contain authorization objects controlling user access.

Troubleshooting

Errors are analyzed using SU53 to identify missing authorizations.

Risk analysis

Access conflicts are detected using SAP Governance, Risk, and Compliance.


Real Project Example

User receives error while posting financial document in FB50.

SU53 shows:

Authorization Object: F_BKPF_BUK
BUKRS = 2000
ACTVT = 01

Resolution:

Update role authorization in PFCG and add company code 2000.


Conclusion

Understanding authorization objects is essential for SAP Security consultants working with SAP environments. These objects control business activities, enforce security policies, and prevent unauthorized access.

By mastering these 40 critical authorization objects, consultants can efficiently design secure roles, troubleshoot authorization errors, and maintain compliance in SAP systems.


No comments:

Post a Comment