SAP ABAP Data Element BRGHIENR (Hierarchy number for settlement)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
KABR (Package) Appl. development: R/3 Cost Accounting order settlement
⤷
⤷
⤷
Basic Data
| Data Element | BRGHIENR |
| Short Description | Hierarchy number for settlement |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BRGHIENR | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 no. |
| Medium | 15 | Hierarchy no. |
| Long | 20 | Hierarchy number |
| Heading | 3 | HNo |
Documentation
Definition
Defines the sequence in which objects are settled and thus ensures that all objects are settled to zero during a production run.
Example
In a settlement run, you want to settle order 1 to order 2 and order 2, in turn, to order 3.
Order 1 must be settled first, then order 2 (including the debits from the settlement of order 1), and finally order 3 (including the debits from the settlement of order 1 and order 2).
To achieve this, order 1 must have the highest hierarchy number and order 3 the lowest - for example: 300, 200, 100.
History
| Last changed by/on | SAP | 20020107 |
| SAP Release Created in |