| Step | Action | Owner | System Signal | Direction |
|---|---|---|---|---|
| 1 | Demand & Supply Planning at FSL | Microsoft (IBP) | IBP Plan | Internal |
| 2 | Create STO Request | Microsoft (SAP ECC) | STO via UOS | MS → SI |
| 3 | Receive STO, create in SI systems | SI | STO Ack | SI → MS |
| 4 | Confirm STO to ship from factory | SI | STO Confirm | SI → MS |
| 5 | Send confirmed STO to TMC | Microsoft | STO to TMC | MS → TMC |
| 6 | Create load plan from STO | TMC | Load Plan signal | TMC → MS |
| 7 | Send Load Plan to SI | Microsoft | Load Plan | MS → SI |
| 8 | SI creates OBD from Load Plan | SI | OBD | SI → MS → SAP |
| 9 | Pick, Pack, Ship per STO + Load Plan | SI | PGI / Loaded ASN (with RSN) | SI → MS → DBS |
| 10 | Track in-transit milestones | TMC | Milestone signals | TMC → MS |
| 11 | Receive products at FSL | DBS (DSV) | GR @ FSL (with RSN) | DBS → MS |
| 12 | Send GR to SI | Microsoft | GR @ FSL | MS → SI |
| 13 | SI posts GR in their systems | SI | Internal GR | SI internal |
| 14 | E2E Serialization & Lifecycle tracking | All | RSN events | Cross-system |
| System | Purpose |
|---|---|
| SAP ECC | Core P2P, inventory, financials, returns |
| SAP IBP | Unified demand/supply planning |
| SAP MDG S/4 | Master data (+ OnePDM, D365, SKURef) |
| SAP CS (S/4 Add-On) | Corporate Serialization & asset lifecycle |
| SAP GTS | Global trade management & reporting |
| SAP Ariba SCC | Forecast/PO/RMA supplier collaboration |
| CSCP Sourcing 365 | Supplier negotiations, FG purchase prices |
| TMC (Navisphere) | Freight mgmt & carrier tracking |
| DBS WMS | 3PL warehouse inventory management |
| Stratus | Shipment tracking & milestone visibility |
| UOS | Unified Order Service (signal routing) |
| OSS | Order Status Service (tracking) |
| CO+I Apps | DC asset & inventory movements |
| CDE / EDL | Data lake reporting (Power BI) |
| MS-Auth / MS-Invoice | Contract approvals & supplier invoicing |
| Vertex | Tax calculation on procurement |
| Step | Action | Owner | System Signal |
|---|---|---|---|
| 1 | DC capacity planning & reservation | SCOM / CP | Demand signal |
| 2 | Create Ship PO | Microsoft (POA → SAP ECC) | Ship PO via UOS |
| 3 | Ship PO sent to SI (B2B) + TMC | UOS → Supplier Collab Gateway | Ship PO + Orders IDOC |
| 4 | TMC creates load plan | TMC | Load Plan to LP Service → SI + LSDO |
| 5 | DSV/DBS creates OBD from load plan | DBS (FSL) | OBD → Unified Shipment Service |
| 6 | DSV/DBS picks, packs, ships; sends ASN | DBS (FSL) | ASN (with RSN) → UOS → SAP (PGI) |
| 7 | TMC tracks in-transit milestones | TMC | Milestone signals → MS |
| 8 | DC receives goods (GDCO) | CO+I / DC Ops | GR signal → GR Service → SAP ECC |
| 9 | GR acknowledgment flows to SI + Stratus | SAP → Func. Ack → OSS → Gateway | GR Ack + Invoice trigger |
| 10 | Asset settlement & financial close | Microsoft (SAP ECC) | FG → MS books; invoice & payment |
Of ICMs generated in Mar-May 2025, 42% were for LP / OBD / ASN cleanup.
9 scenario types drive the current load plan cancellation and change-management workload.
0 automated — all LP change management remains manual and ICM-dependent today.
| Prio | ID | Requirement |
|---|---|---|
| P0 | 1 | Validate load plan quantity against PO / STO quantity; LP quantity must be less than or equal to the PO quantity. |
| P0 | 2 | Send RMS an error when LP quantity is incorrect so RMS can correct and resend the signal. |
| P0 | 3 | When a load plan is cancelled, Microsoft should automatically delete OBD and ASN, send the cancel signal to SI / DSV, and revert impacted RSNs back to ATP. |
| P0 | 4 | Partners (SI / DSV) must delete all associated OBD / ASN documents when they receive a load plan cancellation signal. |
| P0 | 5 | Retired in the June 2025 draft — internal auto-clear-on-partner-cancel language was struck through and superseded by the broader automation requirements above. |
| P0 | 6 | RSNs associated with the cancelled ASN must revert to ATP inventory status. |
| P0 | 7 | Block SI / DSV from uploading OBD / ASN documents against a cancelled load plan. |
| P0 | 8 | Send a NACK when SI / DSV attempts to upload OBD / ASN documents against a cancelled load plan. |
| P0 | 9 | Allow RMS to send create and cancel LP signals as required, while preventing status changes after a cancel signal is sent to Microsoft and SI. |
| P0 | 10 | Allow SI to update OBD prior to ASN submission when actual shipment execution differs from the original OBD. |
| P0 | 11 | Validate that OBD / ASN quantity equals LP quantity. |
| P0 | 12 | Differentiate secondary load plans for two-leg shipments so reverse logistics and similar patterns do not double count inventory. |
| P1 | 13 | Provide monitoring between the LP cancel signal sent to partner and partner acknowledgement, potentially through an actionable dashboard. |