Warranty fulfillment lag
Support → ERP
Approved warranty claims have remedies sent from Support, but ERP has not produced the corresponding replacement order or credit note for the lagging claims.
Condition: approved claim before replacement/credit
The hand-off that is missing
Present · Support Warranty Claim
Short shipment confirmed against the packing list.
WCL-2026-000004 · FULFILLMENT_PENDING
ERP
EXPECTED · NOT PRESENT
SCN-X10 is declared across Support and ERP; this record carries no operational link to ERP.
Present · Support Warranty Claim
Finish failure inside the warranty period; part discontinued.
WCL-2026-000003 · FULFILLMENT_PENDING
ERP
EXPECTED · NOT PRESENT
SCN-X10 is declared across Support and ERP; this record carries no operational link to ERP.
The scenario catalogue names the destination system. No counterpart record exists at Day-0, and none is implied here.
Evidence anchors
Evidence
Support Warranty Claim WCL-2026-000004 · Short shipment confirmed against the packing list. · FULFILLMENT_PENDING
replacement sent; refused BLOCKED_ON_CUSTOMER_IDENTITY
Support Warranty Claim WCL-2026-000003 · Finish failure inside the warranty period; part discontinued. · FULFILLMENT_PENDING
refund sent; refused BLOCKED_ON_ORIGINAL_INVOICE_LINEAGE
Comparison case
Support Warranty Claim WCL-2026-000001 · Clamp failed within the warranty period. · COMPLETED
replacement settled as SO-2026-000008
Support Warranty Claim WCL-2026-000005 · Crossbar cracked at the clamp seat inside the warranty period. · COMPLETED
refund settled as CN-2026-000001
Why this is here
Metrolane Day-0 deliberately includes realistic cross-system delays, duplicate source records and event-ordering conditions. They are verified parts of the frozen reference estate, not accidental data corruption.