Solution : https://service.sap.com/sap/support/notes/370082 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the application of the "Responsibility Area" authorization logic introduced in Release 4.0, particularly how it impacts transactions and authorization checks across modules like CO. Starting with Release 4.0, users can define authorization for grouped objects through the new "Responsibility Area", which simplifies hierarchy-based authorizations. Detailed scenarios describe authorization checks for various cases including different hierarchy nodes and group maintenance scenarios for standard and non-standard objects. Also included are instructions for configuring custom hierarchies through transaction OKKP, reflecting system changes post-Release 4.5 and leading up to Release 4.70's enhancements that support up to three hierarchies with inheritance mechanics.
Key words :
resparea = ks0001cc1 resparea = hi0001a3 resparea = hi0001a2 resparea = hi0001a1, k_cca co_action=0002 resparea=hi00010001 kstar=, k_cca co_action=0003 resparea=hi00010001 kstar=, k_cca co_action=0003 resparea=hi00010001-01 kstar=, k_cca co_action=0003 resparea=hi00010001-02 kstar=, k_cca co_action=0003 resparea=ks0001a kstar=, k_cca co_action=0003 resparea=ks0001b kstar=, k_cca co_action=0003 resparea=ks0001c kstar=, year-independent basic data, cost center standard hierarchy node
Related Notes :
| 1462516 | Authorizations: Profit centers / groups |
| 1090429 | OKEON: Restrict authorization check to top node only |
| 400142 | OKEON: Authorization check when creating groups |
| 391305 | INFORMATION: CO-OM (Customizing & master data) |