Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MD03 (Package) Appl. development R/3 MPS/determin. requirements planning
Basic Data
| Data Element | TOLUN |
| Short Description | Planning file entry: underdelivery tolerance |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PROZENT100 | |
| 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 | Underdel. |
| Medium | 15 | Underdelivery |
| Long | 23 | Underdeliv. tolerance |
| Heading | 10 | Underdel. |
Documentation
Definition
If an undelivery is made for a material in a goods movement and the final delivery indicator has been set, you use this indicator to determine when the system is to create an entry in the planning file for MRP.
Here, you can enter the tolerated difference (as a percentage) from the original quantity of the procurement element (purchase order, production order, reservation). If this tolerance is exceeded then a planning file entry is created.
In the standard system, the value "zero" is preset, that is, an entry is always made if an overdelivery exists. No entry is made if the exact required quantity is delivered. If, in this case, you also want the system to create an entry in the planning file, you must enter the value "100" that usually has the same effect as "zero".
Definition
History
| Last changed by/on | SAP | 19960103 |
| SAP Release Created in |
