42%
ICMs for LP / OBD / ASN cleanup
42% of ICMs generated in Mar–May 2025 were opened to clean up LP / OBD / ASN milestones.
9
Change types driving LP cancellations
9 change types in the documented current-state matrix trigger load plan cancel, change, or cancel → new handling.
Manual
Cleanup path in use today
OBD / ASN cleanup is a manual process handled through email and ICM after post-OBD cancel / change events.
5–15
OBD / ASNs manually deleted per day
Cloud Logistics Ops is asked to manually delete 5–15 OBD / ASNs per day via email or ICM in the documented current state.
🔄 Normal LP Lifecycle
Current-state signal chain from the FSL Architecture Design Review. Selecting a cancellation scenario highlights the steps touched by the documented reservation, Ship PO, and load plan actions.
1
IBP STRIBP generates the replenishment trigger.→
2
SAP ECC STOSTR becomes a blocked STO and is sent to TMC.→
3
SI STO AckSI creates the STO in their system and returns STO Ack.→
4
SI ConfirmSI confirms the STO is ready to ship from factory.→
5
TMC Load PlanCarrier is assigned and route is planned from the confirmed STO.→
Point of No Change
6
LP Distributed to SIMS sends the LP to SI, unblocks the STO, and OBD creation starts.→
7
RSN AssignmentSI assigns RSNs; current-state rule is 1 OBD per LP and 1 line per RSN.→
8
PGI + Loaded ASNSI picks, packs, ships, and sends PGI plus loaded ASN.→
9
In-Transit MilestonesTMC tracks the shipment while it moves to the receiving location.→
10
GR with RSNDBS receives at FSL and posts goods receipt with RSN.→
11
GR Sent to SIMicrosoft sends GR to SI and SI posts GR in their system.Documented point of no change: once the load plan is distributed, downstream OBD / SN documents already exist. Cancel / change activity after this point drives the manual cleanup process documented in the Architecture Review and JCAB playbook.
🏭 SI Response Behavior
Current-state response from Architecture Review slides 58–59. The dividing line is whether OBD already exists at the SI.
Before OBD exists
Positive FACK| Ingrasys | Always positive if STO FACK was positive |
| Lenovo | Positive only |
| ZT | Positive only |
Automatic LP cancel / change prior to OBD is documented as Yes for all three SIs.
After OBD exists
Negative FACK| Ingrasys | Negative — OBD already exists |
| Lenovo | Negative — OBD already exists |
| ZT | Negative — OBD already exists |
Post-OBD LP cancel / change moves into manual cleanup because the SI cannot auto-process the request after OBD creation.
Document relationships supported today: 1:1 (STO → LP → OBD → ASN) and 1:N delivery splits are supported. N:1 consolidation and partial / short ship are not in scope, and multiple ASNs sharing one LP fail in DBS because DBS cannot change an existing LP.
🧭 Cancellation Scenario Matrix
Documented current-state change triggers from the BRD current-state section. Click a row to highlight the lifecycle steps touched by that scenario.
| Change Type | DC Reservation Action | Ship PO Action | Load Plan Action |
|---|
| MSF / MSPN Change | Cancel → New | Change | Cancel → New |
| Quantity Change | Cancel → New | Change | Cancel → New |
| Ship-from Change | Cancel → New | Change | Cancel → New |
| Destination / DC Change | Cancel → New | Same country: Change
Diff country: Cancel → New | Cancel → New |
| Supplier ID Change | Cancel → New | Cancel → New | Cancel → New |
| PO Cancellation | None | Cancel | Cancel |
| DC ETA Date Change | Change | None | Threshold: GT X → Cancel → New (if not picked up); LT X → Change |
| Price Change | None | Threshold: GT X → Cancel → New; LT X → Change | None |
| Carrier Change | None | None | Change |
Select a current-state scenario to highlight the lifecycle steps touched by the documented reservation, Ship PO, and load plan actions.