ASCP Forecast Consumption
ASCP Forecast Consumption
ASCP Forecast Consumption
Consumption in ASCP, Saphran Forecast Netting in customization and Saphran Forecast Interface
Prepared by: Deepak Khosla and Shailender Pushkarna
Contents
Gentex EBS Forecasting Flow Forecasts for ASCP Forecast Consumption within ASCP: Options and Option Evaluation Saphran Forecast Interface, Saphran Netting against Radley, Derive Truncated Saphran Forecast Prior to ASCP Saphran data mapping- Requirements Forecasting- EBS Setups Action Items Conclusions Questions
Saphran Interface
Radley Interface Analyze consumption details, Compare Forecasts Analyze ASCP Forecast Consumption on the ASCP Workbench Consume Forecast against Sales orders at ItemCustomer level ASCP
MRP Report
Custom Report
ASCP
System
Note: Please refer to the MD50 for details on netting logic.
Planner/ Schedule r 3
Radley EDI Forecast Sales Orders Saphran-Truncated Forecast Manual Forecast Safety Stock Targets (Bucket days and Percent)
10
11
12
Pros:
1. This will reduce the number of records in the forecast set-up, which reduces lot of maintenance. 2. This will also reduce the risk of data not matching as it is at higher aggregation level. 3. Data mapping between Saphran and EBS forecast tables will be much easier. 4. Number of Forecast names to be set up required per Forecast Set = 1.
Cons:
1. If the same item belongs to multiple customer/ ship_tos, then the customer/ shipto-wise consumption comparison is not possible. 2. The logic of custom forecast consumption will change to item level. RIE needs modification. 3. The setup and logic of Saphran forecast toggle using DFF (no. of weeks) needs to be modified in the RIE.
The Saphran toggle weeks may have to be defined at item-Ship from org level rather than at customer ship-to level.
13
Assumption: If customer plant is used as mapping entity instead of customer, then each customer plant can not belong to more than one customer. Pros:
1. Consumption and Comparison of forecast will be at a ship-to site level granularity.
Cons:
1. Huge mapping and setup effort from Saphran as well as EBS side and may be incomplete. 2. This requires forecast data to be setup at customer ship-to level in EBS for both Radley and Saphran. Number of Forecast names to be set up required per Forecast Set = No. of Customer sites being shipped. 3. Mapping and data inaccuracies have direct impact on plan output. 4. The current Saphran Forecast interface and custom netting between Radley and Saphran may not be accurate due to mapping challenges.
14
Assumption: If customer plant is used as mapping entity instead of customer, then each customer plant can not belong to more than one customer. Pros:
1.
2.
3.
This will reduce the number of records in the forecast set-up, which reduces lot of maintenance. Number of Forecast names to be set up required per Forecast Set = No. of Customers being shipped. This will also reduce the risk of data not matching as it is at higher aggregation level, but at more granular level than Option1. Data mapping between Saphran and EBS forecast tables will be much easier, but effort will be more than Option1.
Cons:
1. 2. 3. If the same item belongs to multiple ship_tos, then the customer/ shipto-wise consumption comparison is not possible. The logic of custom forecast consumption will change to item-customer level. RIE needs modification. The setup and logic of Saphran forecast toggle using DFF (no. of weeks) needs to be modified in the RIE .
The Saphran toggle weeks should be defined at customer level. The toggle weeks will be unique for that customer, but applicable to all items under that customer.
15
Saphran Forecast Interface, Saphran Netting against Radley, Derive Truncated Saphran Forecast Prior to ASCP
Receive Flat file from Saphran Team with mapped entities Clear all the old entries and populate the new forecast data Send notifications for the failed/ error records This will be original Saphran Forecast.
17
Clear all the old entries and populate the new forecast data
18
Clear all the old entries in the truncated forecast set and
populate the new truncated forecast data.
19
20
21
Saphran Netting Earlier it was decided to have Saphran netting at customer plant level. AS ASCP consumption is recommended at item-Customer level, we will have the same consumption logic for the customized Saphran Netting. Saphran Forecast Interface and mapping: With Option2, the mapping file is expected to have the following minimum information: Ship from org (Gentex Plant) Customer Name Customer Plant Item Bucket Date Qty
with the following minimum entities matching exactly that in EBS: Ship from org (Gentex Plant) Customer Name (or Customer Plant) Item number
The Customer plant DFF in customer master will be used for mapping the Saphran Customer Name to the EBS customer Name. Assumption: If customer plant is used as mapping entity instead of customer, then each customer plant can not belong to more than one customer.
22
25
26
27
28
Summary
Forecast Consumption will be at item-Customer level (Option2) in both
ASCP and Custom netting of Saphran against Radley.
The Saphran Forecast Toggle will be at item-customer level. List of Action Items is acceptable and followed
29
QUESTIONS
30
Thank You