Hierarchy
⤷ CRM-MD-PRO (Application Component) Products
⤷ CS (Package) R/3 Application development: PP Bills of Material
Basic Data
Data Element | HISTU |
Short Description | Level (in Multi-Level BOM Explosions) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC2 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Level |
Medium | 15 | Level |
Long | 20 | Level |
Heading | 3 | Lev |
Documentation
Definition
The BOM level and the path are only relevant for planning with phantom assemblies.
The BOM level and the path together identify the exact position of a phantom assembly in a BOM.
Example
A BOM contains the following phantom assemblies (Phan.Ass.) and materials:
Material A
_________________________|__________________
| | |
| | |
Phan.Ass. B Phan.Ass. C Material D
_____|________ _____|______
| | | |
| | | |
Phan.Ass. E Mat. F Mat. G Mat. H
|
|
Mat. J
To enable the user to trace the positions of phantom assemblies in the BOM, the BOM levels and paths are assigned according to the following logic:
- Each BOM level is assigned a number
- Each path in the BOM is assinged a number
In the following BOM, the first number indicates the BOPM level, and the second indicates the path. Materials that are not phantom assemblies are assigned level and path number 0. However, if a material is a component of a phantom assembly, it inherits the level and path numbers from the phantom assembly.
Material A
(0/0)
_________________________|__________________
| | |
| | |
Phan.Ass. B Phan.Ass. C Material D
(1/1) (1/2) (0/0)
_____|________ _____|______
| | | |
| | | |
Phan.Ass. E Mat. F Mat. G Mat. H
(2/1) (1/1) (1/2) (1/2)
|
|
Mat. J
(2/1)
Supplementary Documentation - HISTU 0010
Definition
Example
Use
Dependencies
Example
History
Last changed by/on | SAP | 19981210 |
SAP Release Created in |