5.1.0 Decision tree FG definition
The Decision Tree for FG, as conceived by Supply Chain Excellence, is as follows :
5.1.1 Decision tree in DynaSys
In DynaSys DiP, it corresponds to the tab "Decision tree FG" inside the workspace "PI - FG"
...
Proposed SHS
...
The Proposed Stock Holding Strategy (SHS) represents the output of the Decision tree in DynaSys by considering all the different criteria (see "Decision tree FG definition" above).
This Proposed SHS will be used into calculating the "Cycle Stock proposed", "Safety Stock proposed" and "Target stock proposed", and compare them to the existing current Cycle, Safety and Target stock.
Example values : for Finish Goods, possible values are MTS, MTO and MTO-FB.
...
Reason
...
It gives the reason of the proposed SHS, to guide the user as to why the SHS is proposed. It represents the different decision nodes of the Decision tree.
Example: for Proposed SHS = MTS, a reason code could be "Low Internal sales ; CLT<RLT" correspond to a . Another example, now for Proposed SHS = MTO-FB, it's the reason = "High Internal Sales".
...
Internal sales %
...
It's based only on the next 12 months and it's the results of dividing the Internal sales (to other Solvay sites) to the Total Sales (Internal + External).
Note:
- the term "Internal sales" includes the sales to other Solvay sites (either intra GBU or inter GBU).
- the term "External sales" includes only the sales to external Customers.
Example: if I'm in Clamecy site of Novecare, flows to Spartanburg site will be considered internal sales. Flows to a TS site will also be considered internal. Flows to any external customer will be external
...
Catalog lead time SAP
...
It represents the "Promised Lead time" to the Customer.
Source:
- For Novecare only, since the GBU wants to avoid having different values in TRLT and Catalog LT field, the "Catalog LT from SAP" is not used. The "Promised LT to the Customer" is coming instead from the SAP field TRLT (Total Replenishment LT, from MRP3 view).
- For other GBUs, the "Catalog lead time SAP" is coming from the new field "Catalog LT" from SAP Material Master > MRP2 view.
...
SHS RLT
...
It's calculated in DynaSys and represents the Strategy-dependent Replenishment Lead time.
Represents the total time between placing a production / replenishment order and the availability date. It considers other BOM levels lead times (multi level) + distribution network (multi sites) and stock holding strategies.
More info in: put link
...
Volume Category
...
It's calculated in DynaSys and represents the classification of the Material in a given site due to its volume (a classic Pareto analysis).
Possible values : High volumes (top 80% volume), Medium volume (next 15% volume), Low volume (last 5 % volume).
...
It's calculated in DynaSys and represents the classification of the Material in a given site due to its contribution margin (a classic Pareto analysis).
Possible values : High Margin (top 80% margin), Medium margin (next 15% margin), Low margin (last 5 % margin).
...
It's calculated in DynaSys based on last 12 months demand, and represents Number of weeks with Demand / Number of weeks in the year.
The Demand includes both Independent demand (InterCo + External demand) + Dependent demand (internal consumption/use inside a site).
...
It's calculated inside DynaSys based on the next 12 months and represents the number of Sold-to for which we have a demand (demand > 0).
If there is only one Sold-to, the Material is considered Monocustomer. If there are 2 or more, it's a Polycustomer.
Procurement LT for PI" will be the one used to calculate the "Procurement LT" used for P&I.
The final value of the “Procurement LT for P&I” will be the result of the following values, each with different priorities.
More information about each lead time below:
> Historical median Procurement LT : this is only displayed as information. It's median value calculated from historical Purchase Orders in SAP in the last 12 calendar months (we take the median of the lead times of each PO, this lead time being = date of PO reception - date of PO creation).
It is calculated in BW taking the rule : for every Material x Plant, we extract all the stock entries (Quantity) from Material Documents of MB51 due to a PO and we calculate the lead time ( Lead time = Posting date - Date of PO creation). Then, we calculate the Median value
Note: the median is the middle number in a sorted, ascending or descending, list of values.
Example: RHODIASOLV RPDE FUTS METAL 225 KG @ Clamecy / 10454 @ 7512
In this case, this Material has 3 entries (Posting Date = 27/03/2020) for a PO created in 26/12/2019
Historical median Planned delivery time value = 27/03/2020 - 26/12/2019 = 92 days
> Planned delivery time from MRP2 : this is the initial value taken into account to determine the "Procurement LT for P&I". It takes the Pld Delivery time from SAP MRP2 view. For more information about MRP2 Pld Delivery time, please refer to: SAP Purchase LT
> Planned Delivery time from PIR: If available, this value becomes prioritary to the one above from MRP2. This LT coming from the Purchase Info Record. For more information about PIR Pld Delivery time, please refer to: SAP Purchase LT
> Proc LT override: user can override the value (Optional, not mandatory).
> Procurement LT for P&I: this will be the result of the logic from previous lines (refer to schema below)
Note:
a> if "PIR Pld Delivery time" and "MRP Pld Delivery time" are both empty, the "Procurement LT for P&I" will be 0 (unless the User keys in a value in the datafield "Pld Delivery time override").
b> the "Historical median Planned delivery time" is only displayed as information and can be used as referent of a historical value by the user. It means that it's not automatically considered in the final value of "Procurement LT for P&I".
This is a design choice and the rationnel behind it is that this "historical median value", even though is a good reference, can sometimes be inflated.
=> To help detect the cases where neither PIR Pld Delivery time nor MRP2 Pld Delivery time is maintained, tere is an alert at the beginning of P&I Process : in the WS "SAP Data Quality", the Alert "SKU Purchased without Pld Delivery time". The missing values can be shared with the Site SC department.
=> The Mass upload from a .xlm file could help speed up extraction/upload part.5.2 Decision tree Raw Material & Intermediates