X12 940 — Warehouse Shipping Order
Inbound demand creates or updates warehouse shipping work after tenant, partner, identifier, line, and payload validation.
Trading-partner integration
Turn EDI documents into controlled warehouse and shipment work.
Available through EDI
XMS Cloud implements ANSI X12 004010 payload flows for warehouse orders, advance ship notices, shipping advice, shipment status, and functional acknowledgement. Trading-partner mapping and transport remain deployment-specific.
Document scope
Each transaction set has one operational consequence.
Inbound
X12 856 — Advance Ship Notice
Inbound item and handling-unit expectations feed receiving preparation without replacing physical receipt truth.
X12 945 — Warehouse Shipping Advice
Outbound confirmation reports warehouse shipment execution back to the trading partner.
X12 214 — Transportation Carrier Shipment Status
Outbound transport milestones communicate normalized shipment status from the canonical movement.
X12 997 — Functional Acknowledgement
Outbound acknowledgement reports interchange and transaction acceptance or rejection at the EDI boundary.
Partner onboarding
Qualify the envelope, map, and failure path—not only a sample file.
Identify
Bind sender, receiver, client, partner, warehouse, control numbers, transaction type, version, and business identifiers.
Map
Approve segment, qualifier, unit, product, address, date, reference, handling-unit, shipment, and status crosswalks.
Rehearse
Test valid, duplicate, late, partial, unknown-SKU, malformed, oversized, rejected, reprocessed, and out-of-sequence documents.
Operate
Monitor interchange, transaction, quarantine, acknowledgement, replay, correction, evidence, and owner queues.
Transport and security boundary
Document format and transport are separate integration layers.
X12 004010
The transaction-set implementation targets ANSI X12 004010; other versions use their own mapping and regression validation.
File or API payload
AS2, value-added networks, mailbox polling, SFTP, and certificates are configured independently from document parsing and generation.
Separate EDIFACT integration
EDIFACT syntax, messages, implementation guidelines, and partner maps follow a separate integration scope.
Partner and client binding
Envelope identity never authorizes cross-client data. Tenant context, row-level controls, idempotency, and audit remain mandatory.
Operational evidence
Keep the source document attached to the work it created.
Inbound and outbound records should retain interchange, transaction, partner, control number, source payload hash, correlation, status, error, acknowledgement, and replay history.
Document identity
Preserve envelope and transaction references without treating a filename as business identity.
Canonical object link
Relate order, ASN, receipt expectation, shipment, milestone, and acknowledgement to the source exchange.
Correct and replay visibly
Quarantined records retain reason and attempt history; idempotency prevents ordinary replay from duplicating work.
EDI compatibility review
Bring the implementation guide, samples, transport, partner identities, and acknowledgements.
Define exact version, direction, maps, validation, security, replay, monitoring, and support ownership.