Even though these alerts could be used to have a starting overview of new Sites for P&I, they are more intended for Sites who have already gone in the past though the methodology, because they are based on the "SHS" and "Catalog LT" (which are themselves output of the P&I process <=> for new sites they are still to be defined).
(Please compare to the case of Control checks #1 & #2 which are supposed to be checked Before P&I).
| Alert # | Explanations |
|---|---|
| Control check #6: SKUs without SHS | This alert will show you for a given a site all the SKUs without a SHS in SAP |
| Control check #7: SKUs with Ext demand should have a Catalog LT | Alert showing the list of SKUs with existing Future Demand (external + internal). without Catalog LT in SAP. We consider the Internal demand to include also InterCo flows or Internal use. |
| Control check #8: For MTO/MTO-FB, Catalog LT must be higher than SHS RLT | Alert showing the list of MTO/MTO-FB SKUs where the Catalog LT from SAP < SHS RLT. (for a site that has never gone through P&I, this alert will be empty since we exclude lines where Catalog LT is not defined or 0). |
Note: these alerts are mostly meant for Sites which had already gone through P&I (after P&I results have been uploaded back to SAP): to double check the consistency of SAP data vs what was defined in P&I DynaSys).
However, they can still be be used at the beginning of P&I process: like a warning to highlight the cases where Catalog LT is not consistent with the current SHS (that might need more attention later).