ERP consumption timeout — working review
WORKING NOTES — review decisions belong in your controlled records.
Guide: https://seal.run/integrations/workflows/erp-bom-integration

Use one actual-consumption event and its uncertain outbound movement. Establish the exact operation’s recovery contract before deciding whether another send is appropriate.

1. Physical event and intended movement
Identify the source event, material, lot, plant/location, actual quantity and unit. Record the exact destination operation, movement meaning and any signed-quantity convention. Distinguish this event from reservations and issues.
Your evidence and observations:
[Not recorded]

2. Outbound identity and attempts
Retain the original transaction identity, payload/mapping revision, external reference and each attempt’s time and response classification. Record which attempt has an uncertain outcome; a timeout does not establish a rejection.
Your evidence and observations:
[Not recorded]

3. Supported lookup and retry rules
Cite the installed operation’s identity/idempotency behavior, retention period where relevant and supported destination query. Record query scope, time and any delay or incomplete visibility that limits interpretation.
Your evidence and observations:
[Not recorded]

4. Destination comparison
For each candidate, compare the agreed identity and all required material/location/lot/quantity/unit fields. Classify one complete match, field conflict, multiple matches or no currently visible match. Identical quantities alone do not identify a movement.
Your evidence and observations:
[Not recorded]

5. Recovery or correction decision
Record the responsible owner’s next action under the operation’s supported rules. Retain matched destination-document evidence. Treat a later source correction as separately authorized work linked to the original movement, not a silent payload edit.
Your evidence and observations:
[Not recorded]

EVIDENCE NEEDED TO FINISH
The physical quantity remains unchanged by delivery attempts. The destination outcome is supported or explicitly unresolved, and any retry follows the exact operation’s contract. A correction references the original posted document and has its own traceable decision.