Hierarchy
⤷ SD-BF-SMI (Application Component) Supplier Managed Inventory
⤷ VSMI (Package) Supplier-Managed Inventory (SNC-ERP)
Basic Data
Data Element | SMI_HIGH_PERC |
Short Description | Upper Tolerance (%) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DEC3_1 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 4 | |
Decimal Places | 1 | |
Output Length | 5 | |
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 | Up. Tol. % |
Medium | 15 | Upper Tol. Prc. |
Long | 25 | Upper Tolerance Percent. |
Heading | 35 | Upper Tolerance Percentage |
Documentation
Definition
The amount by which an incoming demand is allowed to exceed the usual previous demand in percentage.
Use
The percentage can be set for short-term, mid-term, and long-term periods (in days) within the replenishment planning horizon.
If you leave the field empty, it means the upper tolerance will not be checked.
Dependencies
Example
The customer sends the following demand forecast:
Current Message Preceding Message Period
(sent on 02. Feb.) (sent on 01.Feb)
01. Feb. 10 pcs.
02. Feb. 15 pcs. 02. Feb. 10 pcs. Short-term
03. Feb. 15 pcs. 03. Feb. 10 pcs. Short-term
04. Feb. 15 pcs. 04. Feb. 10 pcs. Short-term
05. Feb. 6 pcs. 05. Feb. 10 pcs. Mid-term
06. Feb. 6 pcs. 06. Feb. 10 pcs. Mid-term
07. Feb. 6 pcs. 07. Feb. 10 pcs. Mid-term
08. Feb. 6 pcs. 08. Feb. 10 pcs. Mid-term
09. Feb. 12 pcs. 09. Feb. 10 pcs. Long-term
10. Feb. 12 pcs. 10. Feb. 10 pcs. Long-term
11. Feb. 12 pcs. 11. Feb. 10 pcs. Long-term
12. Feb. 12 pcs. 12. Feb. 10 pcs. Long-term
13. Feb. 12 pcs. 13. Feb. 10 pcs. Long-term
The supplier maintained 3 days for the short-term period with an upper tolerance of 40%, 4 days for the mid-term period with a lower tolerance of 30%, and 5 days for the long-term period with an upper tolerance of 30%.
The system executes the following calculations:
Short-term period:
Sum of current demands, starting with the first day :
02. Feb. = 15 pcs., 03. Feb. = 15 pcs., 04. Feb. = 15 pcs. ==> 45 pcs.
Sum of preceding demands, comparing the same dates:
02. Feb. = 10 pcs. , 03. Feb. = 10 pcs., 04. Feb. = 10 pcs. ==> 30 pcs.
Result: The demands for the short-term period increased by 50%, which violates the tolerance of 40% specified for the short-term period.
Mid-term period:
Sum of current demands, starting with the first day after the short-term period:
05. Feb. = 6 pcs. , 06. Feb. = 6 pcs., 07. Feb. = 6 pcs., 08. Feb. = 6 pcs. ==> 24 pcs.
Sum of preceding demands, comparing the same dates:
05. Feb. = 10 pcs. , 06. Feb. = 10 pcs., 07. Feb. = 10 pcs., 08. Feb. = 10 pcs. ==> 40 pcs.
Result: The demands for the mid-term period decreased by 40%, which violates the tolerance of 30% specified for the mid-term period.
Long-term period:
Sum of current demands, starting with the first day after the mid-term period:
09. Feb. = 12 pcs. , 10. Feb. = 12 pcs., 11. Feb. = 12 pcs., 12. Feb. = 12 pcs., 13. Feb. = 12 pcs. ==> 60 pcs.
Sum of preceding demands, comparing the same dates:
09. Feb. = 10 pcs. , 10. Feb. = 10 pcs., 11. Feb. = 10 pcs., 12. Feb. = 10 pcs., 13. Feb. = 10 pcs. ==> 50 pcs.
Result: The demands for the long-term period increased by 20%, which does not violate the tolerance of 30% specified for the long-term period.
If the stop indicator is set, the processing of the item is stopped as soon as the demand change of at least one period leads to a tolerance violation. The supplier has to react manually via the SD SMI Monitor.
Note
Once a customer has finished a production preparation/test phase, they can start the series production. However, extraordinary demands influence the series production. To enable the supplier to react to this situation, they need to be informed. Then the supplier is able to adapt their production/procurement processes and fulfill the demands within the SMI process.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 604 |