An EDI purchase order starts a business process; it does not prove that every connected
system completed it. Build the journey around explicit source ownership and retained
identities, then qualify each integration with a representative test exchange.
Assign responsibility
See the OMS → WMS → TMS integration guide for source ownership.
Services have different hosts, credentials, and records. Shared names or generated API
pages do not establish deployed connectors or an automatic end-to-end workflow.
The arrows describe integrations to configure and qualify, not a claim that all are
active in your workspace.
Receive and correlate
Use the first PO cycle to validate and process approved test wire.
Retain workspace, partner, PO, document, event, and correlation IDs. A complete processing
response exposes accepted/rejected document outcomes and acknowledgment artifacts;
HTTP 200 alone is insufficient.
For EDI-to-Sync, configure separate test/production bindings in Connections. The setup
probe is a no-op. Inspect the original connection’s delivery receipt, StateSet order ID,
and related connector outcome. Check the actual ERP object and its duplicate-handling
result before recording downstream acceptance. Changes/cancellations and remote-commit
response loss require their own qualification.
Execute physical fulfillment
Pass the qualified commercial order through your WMS/TMS integration. Retain warehouse,
shipment, carton, SSCC and carrier identities alongside the original partner/PO. A booking
or queued task is not proof of physical shipment. Check actual quantities and partial
fulfillment before preparing outbound documents.
If orchestration uses Workstream/Temporal, configure the real workflow and activities.
The EDI gateway does not automatically create a workflow merely because an event exists.
Customer callbacks and the event outbox have different destination/signature contracts;
verify the correct scheme.
Respond and reconcile
Prepare 855/856/810 through the reviewed-order workflow.
Persist exact overrides, order revision and key. Response loss must recover that original
operation rather than minting another document. Reconcile transport receipts, functional
acknowledgment, and actual downstream processing separately.
An 820/REMADV, invoice, or clean acknowledgment list is evidence to match, not automatic
proof of cash settlement. Compare the intended invoice, remittance, applied payment, and
ledger balance. Use partner scope where business references repeat.
Before production, qualify duplicates, rejection, delayed acknowledgment, partial shipment,
change/cancel, and recovery after an external commit. Agree on operational ownership and
service targets; deployment evidence does not
supply a customer-specific acceptance result. Last modified on October 20, 2026
