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_ADD1 |
| Short Description | Use First 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. 1 |
| Medium | 15 | Hierarchy 1 |
| Long | 22 | Hierarchy 1 |
| Heading | 10 | Hier. 1 |
Documentation
Definition
Since the new authorization concept was introduced in Overhead Cost Controlling for Release 4.0, you can now inherit authorizations within 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, this applies to all objects in this group (for more information, see note no. 370082).
This inheritance logic only applied to the standard hierarchy. The setting in the controlling area enables you to name up to two more alternative hierarchies (according to fiscal year), which can be used for the authorization check in the same way as the standard hierarchy (meaning, that inheritance logic is used). You can also deactivate the standard hierarchy as an authorization hierarchy, and use only the alternative hierarchy.
This logic has been implemented for cost centers (K_CCA and K_ORDER) and profit centers (K_PCA).
The system provides you with F4 help related to customizing for when you maintain authorizations. All hierarchies that were entered for five years ago or for five years in the future in the customizing controlling area can be used for authorization maintenance.
When authorizations are checked, the current calendar year and the corresponding valid hierarchies are also checked in the order in which they were entered. This means that the standard hierarchy is checked first, followed by the first alternative and then the second. A year specification that depends on the transaction is not possible.
Note that the more alternative hierarchies you use, the longer the runtime.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in | 470 |
