Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KBAS (Package) Overhead Cost Controlling
Basic Data
| Data Element | AUTH_USE_ADD2 |
| Short Description | Use Second Alternative Hierarchy for Authorizations |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Hier. 2 |
| Medium | 15 | Hierarchy 2 |
| Long | 22 | Hierarchy 2 |
| Heading | 10 | Hier. 2 |
Documentation
Definition
Since the new authorization concept was introduced in Overhead Cost Controlling for Release 4.0, it has been possible to inherit authorizations in a hierarchy. The authorization objects K_CCA, K_PCA, K_ABC and K_ORDER enable you to enter standard hierarchy groups. If a user is authorized for one of these groups then this user is also authorized for all objects in this group (for more information see note no. 370082).
This inheritance logic, however, previously only applied to the standard hierarchy. You can now use the setting in the controlling area to name up to two more alternative hierarchies by fiscal year. These are then used in the same way as the standard hierarchy for the authorization check (with authorization logic). You can also deactivate the standard hierarchy as the authorization hierarchy and just use the alternative hierarchies.
This logic has been implemented for cost centers (K_CCA and K_ORDER) and profit centers (K_PCA).
The system has an F4 help (linked to customizing) for authorization maintenance. All hierarchies that were entered for the last five years and the next five years in customizing for the controlling area can be used in authorization maintenance.
When authorizations are checked, the system always uses the current calendar year and the hierarchies valid in that year in the order in which they were entered. Thus it checks the standard hierarchy first followed by the first alternative and then the second. It is not possible to determine the year using the transaction.
Note that the more alternative hierarchies you have, the longer the runtime.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in | 470 |
