Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MD01 (Package) Appl. dev. R/3 consumption driven gen. requirements planning
Basic Data
| Data Element | INPUTQUAN |
| Short Description | Required quantity in pegged requirements |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MENGV13 | |
| Data Type | QUAN | Quantity field, points to a unit field with format UNIT |
| Length | 13 | |
| Decimal Places | 3 | |
| Output Length | 18 | |
| 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 | Quantity |
| Medium | 15 | Required qty |
| Long | 20 | Required Quantity |
| Heading | 18 | Required Quantity |
Documentation
Definition
The required quantity specifies the quantity from the receipt element at lower BOM level (often raw material) needed for a particular requirement of a finished product. The unit of measure of the required quantity is the unit of measure of the material at lower BOM level.
If the receipt element in question is required for several different requirements of the finished product, the required quantity can provide a note stating which requirement can be covered if the complete quantity of the receipt element is not available.
The total of the required quantity plus the quantity without requirements always results in the receipt quantity of the receipt element in question.
The required quantity is calculated as follows: at the lowest level, the required quantity is either the receipt quantity or the dependent requirements quantity that is covered by the receipt element. The required quantity is the smallest of these two quantities. At the higher BOM levels, the required quantity is calculated recursively using the required quantity of the lower BOM level multiplied by the requirement quantity and divided by the order quantity.
Example 1
Two requirements of the finished product for 10 and 35 pieces are covered by one planned order for 45 pieces. The finished product has a BOM. One component in the BOM has a BOM factor of 2. Therefore, in the planning run, the system created a dependent requirement quantity of 90 pieces. This dependent requirement is covered by a planned order or by another receipt element amounting to 100 pieces.
The required quantity of the lower level is 90 pieces. The required quantity of the first requirement of 10 pieces for the finished product is 90 * 10 / 45 = 20 and the required quantity of the second requirement of 35 pieces is 90 * 35 / 45 = 70. Twenty pieces from the receipt element of the component are required to cover the first requirement of the finished product and 70 pieces are required to cover the second requirement.
Example 2
In the above example, the dependent requirement for the component amounting to 90 pieces is covered by two receipt elements. The first of these two receipt elements has a receipt quantity of 50 pieces. The pegged requirements displayis now accessed for this receipt element.
The required quantity of the lower level is now 50 pieces. The required quantity of the first requirement of 10 pieces for the finished product is 50 * 10 / 45 = 11,111. 11,111 pieces from the receipt element for the component in question are required to cover the first requirement of the finished product.
Note:
No rounding is carried out even for units of measure that do not allow decimal places. The required quantity is only displayed for information purposes and is not used in any operative transactions. Therefore, no rounding - either up or down - is required. This would in fact reduce the quality of information.
History
| Last changed by/on | SAP | 20040819 |
| SAP Release Created in |
