Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO (Application Component) Logistics - General⤷
DIMP_STD (Package) Standard Objects of DIMP Industries
Basic Data
| Data Element | ISA_ESCR5 |
| Short Description | Lower Tolerance Limit for Checking Period 2 |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC3 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
Indicates the percentage by which the scheduled quantities of the release to be newly transmitted may differ from the schedule lines in the last-transmitted release without a release being stopped.
Use
You can define tolerance limits for a maximum of three checking periods.
As a rule, you define smaller tolerance limits for the near future and larger tolerance limits for the distant future.
Prerequisites
The tolerance check is only carried out if SA releases are subject to dynamic stopping. In other words, the indicator Activate Stop (static stopping) is not selected in the additional data of the scheduling agreement item.
Dependencies
So that releases are only stopped in the event of major changes in the delivery schedule situation, the system can carry out a tolerance check when the release creation program is run (Scheduling Agreement -> Create Release).
For this to occur, you must use a creation profile specifying that releases are to be stopped in the event of tolerance violations.
The tolerance check starts with the date of release creation or at a later date om the event of overdelivery.
During the tolerance check, the system can consider every single schedule line or the total scheduled quantity of a checking period:
- If the creation profile provides for an individual check, then for each schedule line of a checking period, the system checks whether the new scheduled quantity differs from the quantity already transmitted.
- If the creation profile provides for an overall check for a checking period, then the total quantity of the new schedule lines to be transmitted is compared with the total quantity that already transmitted for this period.
- If the cumulative quantity reached is selected in the creation profile, then at the end of the checking period the system checks the cumulative released quantity of the release created and compares it with the cumulative released quantity of the last transmitted release.
If the values determined lie outside the specified tolerance, a release is stopped.
Note
The system never checks tolerances in the case of SA releases containing backlogs or immediate requirements.
For more information, refer to the SAP Library under mySAP Automotive -> MM Scheduling Agreement Enhancements.
Note
If releases have been created and stopped with the release creation report, the MRP controller responsible can be informed about this with the Workflow.
More information is available in the SAP Library under SAP Automotive -> MM Scheduling Agreements Enhancements -> SA Releases: Process -> Workflows for the MRP Controllers.
History
| Last changed by/on | SAP | 20041209 |
| SAP Release Created in | 46C |
