Perimeter:
Included in calculation | Excluded from calculation |
|---|---|
- Deliveries to final customer- Customer Pick-up- Deliveries to warehouses / storages as long as the inventory belongs to the customer
|
=> please think of those exclusions when running the BW query to be aligned with the dashboard |
Formula
OTIF Customer - Requested: we compare the Achieved Delivery date(c) and the the Requested Delivery date (d) + we compare the requested quantity and the delivered quantity
OTIF Customer - 1st Confirmed: we compare the Achieved Delivery date(c) and the 1st confirmed Delivery date (d) + we compare the confirmed quantity and the delivered quantity
OTIF Customer - Last Confirmed: we compare the Achieved Delivery date(c) and the Last confirmed Delivery date (d) + we compare the confirmed quantity and the delivered quantity
________________________________________________________________________________________________________________________________________
OTIF Departure Plant - Requested: we compare the Achieved shipment date (a) and the Requested GI date (b) + we compare the requested quantity and the delivered quantity
OTIF Departure Plant - 1st Confirmed: we compare the Achieved shipment date (a) and the 1st confirmed GI date (b) + we compare the confirmed quantity and the delivered quantity
OTIF Departure Plant - Last confirmed: we compare the Achieved shipment date (a) and the Last confirmed GI date (b) + we compare the confirmed quantity and the delivered quantity
- 1st ATP GI date = 1st ATP date - Route Transit Time
- Last ATP GI date = Last ATP date - Route Transit Time
(a) Achieved shipment date:
Achieved Shipment Date: actual GI date (or equivalent) - detailed definition here
For “PICK UP” transportation mode : Last transfer order confirmation date for the order line if it is a date and Actual Good Issue date for the order line if there is no transfer order (should normally never be in RCS).
For other transportation mode: The last “Actual Good Issue” date
(b) Requested/1st Confirmed/Last Confirmed Good Issue date:
Requested GI date = Requested Delivery date (d) – standard transit time of the route
First Confirmed GI date = 1st Confirmed Delivery date (d) – standard transit time of the route
Last Confirmed GI date = Last Confirmed Delivery date (d) – standard transit time of the route
For Specialty Polymers:
Requested GI date = Requested Delivery date (at the order header level in SAP)
1st confirmed delivery date = 1st committed delivery date (in SAP, see "Additional Data B tab at the orderline level)
Last confirmed GI date = Delivery date (at the orderline level in SAP - Confirmed Schedule Line)
(c) Achieved delivery date:
Achieved Delivery Date: actual or estimated delivery date at customer side - detailed definition here
For “PICK UP” transportation mode : Last transfer order confirmation date of the order line if it is a date and Last Good Issue date of the order line if there is no transfer order (should normally never be in RCS).
For other transportation mode: The last “Actual Shipment end” if it exists, else the last “Planned shipment end” (automatically filled in at planning step of shipment, using planned shipment completion + transit time from the SAP ROUTE or updated manually at shipment completion) if it exists and else the last “Actual Good Issue” date (normally should not happen).
Tolerances:
For quantity:
For In Full tolerances, if there is a tolerance defined in the order then we consider it, ie : 5%, 10% even 20%.
Else it's +/- 0%.
Warning: For some GBU this is one of the main causes to be NON OTIF on the reporting, even if in reality they were.
For time:
This is the standard proposition from EC. However some GBU wanted to have their owns specifications by transport mode, that's why from we include in the new Global SC dashboard their requirements: Tolerances days by GBU
On Time - Criteria | Tolerance SCE |
|---|---|
Road | +/- 1 days |
Rail | +/- 3 days |
Sea | +/- 7 days |
Barge | +/- 3 days |
Multimodal | +/- 2 days |
Air | +/- 0 days |
Reprocessing root causes ( from NON OTIF to OTIF)
In cases of Non OTIF due to time issues, front Office and Back Office can use reason codes: 740, 745, 750 to force the order line status to On Time.
Reprocessing root causes ( from OTIF to NON OTIF)
In cases of OTIF that suppose not to be due to time issues, front Office and Back Office can use reason codes: 755 to force the order line status to Non OTIF.
*You'll find the Guidelines done by SBS & EC end of 2018 : Reason codes guidelines
Plant Category (WP1 only):
PROD = Production plant
NDIR = Direct Trading : shipment from third party suppliers to customer (Order Type TAS will be used for this type of plant)
NDEP = Warehouse : physical Solvay stock location to store purchased materials from Solvay or 1/3 party supplier or Solvay produced materials
NDC = Customer consignment warehouse: stock held at customer address (purchased or produced materials)
SSTT = Sub contracting
| Technical Documentation | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Source:Global Sales - QVSCE_BW_QRY_MVSDSO51_0001 => please think of those exclusions when running the BW query to be aligned with the dashboardFor operational purposes, please open the global sales query used BW_QRY_MVSDSO51_0001 and do the following filter to extract the same info that Global SC dashboard. This query will bring to you Sales orders and Replenishment orders. Thus please follow the next steps:
Update: DailyOrder Types included:Query filters applied:Dimensions:Global Overview of Dimensions
|
Not able to find the solution? Contact SBS Support.
Page
viewed times