Hierarchy
BBPCRM (Software Component) BBPCRM⤷
SRM-EBP (Application Component) Enterprise Buyer⤷
BBP_APPLICATION (Package) Structure Package EBP⤷
ME (Package) Application development R/3 Purchasing
Basic Data
| Data Element | FOTO1 |
| Short Description | Upper Tolerance Limit for JIT Schedules in Checking Period 1 |
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 | Upper TL |
| Medium | 15 | Upper Tol. Lim. |
| Long | 20 | Upper Tol. Limit |
| Heading | 0 |
Documentation
Definition
Use
Definition
Indicates the percentage by which the scheduled quantities of the next scheduling agreement release to be transmitted may vary from the scheduled quantities of the last-transmitted SA release before the next release is actually created.
Use
You can define tolerance limits for a maximum of three checking periods.
As a rule, you will define smaller tolerance limits for the near future and larger ones for the more distant future.
Prerequisites
The tolerance check is only performed when agreement lines have been changed, and when the creation strategy allows that releases are created due to changed agreement lines (Creation strategy 'Changed' on tab page Gen. parameters).
Dependencies
In order that SA releases are only created in the event of major changes to the current overall schedule, the system can carry out a tolerance check when the release creation report is run (Scheduling agreement -> Create release).
For this purpose, you must use a creation profile causing releases to be generated in the event of changes to the overall schedule in the system. The tolerance check begins with the date of release creation or at a later date if there is an overdelivery.
In carrying out the tolerance check, the system can take into account each individual schedule line, or the total scheduled quantity for a checking period:
- If the creation profile provides for an individual check, the system checks every single schedule line within the checking period to see whether the new scheduled quantity varies from the scheduled quantity already transmitted to the vendor.
- If the creation profile provides for an overall check for a checking period, the total quantity of all the lines of the next schedule to be transmitted is compared with the already-transmitted total scheduled quantity for this period.
If the values determined are beyond the specified tolerance, an SA release is created.
Note
The system never checks tolerances in the case of releases created due to changes which contain an immediate requirement.
For more information, see the documentation Purchasing (MM-PUR), section Creation Profile.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19980414 |
| SAP Release Created in |
