Hierarchy
⤷ CO-PC-OBJ (Application Component) Cost Object Controlling
⤷ KKP (Package) Cost Object Controlling for Repetitive Mfg: General
Basic Data
Data Element | HIBEA |
Short Description | With Hierarchy |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | With hier. |
Medium | 15 | With hierarchy |
Long | 20 | With hierarchy |
Heading | 0 |
Documentation
Definition
If this indicator is turned on, the cost object IDs can be put into hierarchies or all nodes of the hierarchy are processed.
Use
Cost object hierarchies are used to collect costs that cannot be traced to particular orders. During period-end closing, these costs can be:
- Distributed to the assigned orders in accordance with the target costs
If the actual costs are distributed to the orders, all activities in period-end closing (such as the calculation of overhead surcharges, the calculation of work in process, the calculation of variances, and settlement) are carried out with reference to the orders.
- Settled as price differences
If the actual costs are treated as price differences, overhead and variances are calculated at the level of the hierarchy. There are two different settlement procedures:
- All price differences are settled to the highest node of the cost object hierarchy from which a posting to Financial Accounting is generated.
- A separate settlement rule is created for each node of the cost object hierarchy. These settlement rules specify a price difference account as the settlement receiver.
Procedure
You must flag the highest cost object ID in the hierarchy as the top of the hierarchy by entering an asterisk (*) in its master record.
Examples
Dependencies
History
Last changed by/on | SAP | 19970902 |
SAP Release Created in |