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 | KHINR |
| Short Description | Standard Hierarchy Area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SETNR | |
| Data Type | CHAR | Character String |
| Length | 12 | |
| Decimal Places | 0 | |
| Output Length | 12 | |
| 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 | Std Hier. |
| Medium | 15 | Std. Hierarchy |
| Long | 20 | Hierarchy Area |
| Heading | 12 | Area |
Documentation
Definition
Use
To create cost centers, you require a structure in master data maintenance to which you can assign cost centers. You create this CO structure, the standard hierarchy, when you create a controlling area. If this hierarchy is not present during controlling area maintenance, the system automatically creates the highest node there.
Use group maintenance to construct the structure of the standard hierarchy. This is possible in both application and customizing menus.
- About the Application Menu
- About the Customizing Menu
Note
- You may create as many alternative groups as you wish. You cannot create new cost centers in groups, but you can enter existing cost centers and cost centers that are to be created.
- The direct assignment to the controlling area guarantees that all cost centers of a controlling area are collected together.
Supplementary Documentation - KHINR 0001
Dependencies
You can use an existing hierarchy as a standard hierarchy only if the following conditions apply.
- It must be unique; it is not used for another controlling area;
- It may not contain any single values.
- It must be classified as a cost center hierarchy; another hierarchy, such as a cost element hierarchy, may not be defined with the same name.
If a standard hierarchy does not yet exist, you receive a message when processing the basic data asking whether a standard hierarchy should be created. If yes, the SAP System notes the hierarchy name and creates a standard hierarchy for the controlling area as the top node when you save the data.
You can change the standard hierarchy name only if no cost centers have been created in the standard hierarchy and the new hierarchy meets the conditions described above. If this is the case, the SAP System creates a new hierarchy when you save the data.
You can set up a standard hierarchy with the maintenance transaction for cost center groups.
Supplementary Documentation - KHINR 0004
Use
The hierarchy area determines the highest point of the hierarchy to be summarized. As a rule this is the standard hierarchy of the controlling area. Summarization proceeds in all subordinate areas from top to bottom.
The system stores data in respective area cost centers, called representative cost centers. You determine the representative cost center for an area in cost center group maintenance by entering this cost center as a representative value for the group (choose "Details -> Report information"). Enter the cost center in the representative value field. If the cost center is to be solely an area cost center, lock lock the cost center to prevent plan or actual postings.
After carrying out summarization, you cannot change the saved hierarchy area due to data consistency. However, you can continue to add subhierarchies if required.
Supplementary Documentation - KHINR 0009
Notes
Field Changes
This field can be changed at any time.
Time Dependency
Changes to this field apply to all periods, including past periods. If you change the content, the old content is overwritten. The new content then applies to both current and past periods.
Use
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
