Hierarchy
⤷ SD-BF-SMI (Application Component) Supplier Managed Inventory
⤷ VSMI (Package) Supplier-Managed Inventory (SNC-ERP)
Basic Data
Data Element | SMI_HORIZON_SHORT |
Short Description | Short-Term Period in Days |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | NUMC | Character string with only digits |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Short |
Medium | 15 | Short Period |
Long | 30 | Short-Term Period in Days |
Heading | 26 | Short-Term Period in Days |
Documentation
Definition
The SMI_HORIZON_SHORT field indicates the number of days you use to specify the short-term period for demand comparisons.
Use
You can specify the number of days in this field.
The supplier sets the short-term period to n days. The demand deviation check adds up the demands of the first n days of the material in the current message. The system compares this result with the sum of the first n days of the preceding message (of this material) while considering the upper and lower tolerances set in the profile for the short-term period.
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 carries out 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.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 604 |