AcknowledgeShipment
OAGIS BOD combining the Acknowledge verb with the Shipment noun. Direct canonical equivalent of EDI EDIFACT DESADV and X12 856 messages in OAGIS 10.x's Logistics domain.
BOD purpose
The AcknowledgeShipment BOD acknowledges on the recipient side the receipt of a ProcessShipment: confirmation of receive planning, optional change request (dock slot unavailable), rejection with reason.
Structure (ApplicationArea + DataArea)
Like every OAGIS BOD, AcknowledgeShipment stacks an ApplicationArea
technical envelope (Sender, BODID, CreationDateTime) and a business DataArea
that contains the verb and the noun.
ShipmentHeader+ applicationStatus(Accepted, RescheduleRequested, Rejected).ShipUnitdetailed if reception plans line by line.
XML example
Minimal OAGIS 10.x payload for didactic purposes. Structural elements (header + at least one line) are required in any conformant implementation.
<?xml version="1.0" encoding="UTF-8"?>
<AcknowledgeShipment
xmlns="http://www.openapplications.org/oagis/10"
releaseID="10.11" versionID="10.11">
<ApplicationArea>
<Sender>
<LogicalID>ERP-CENTRAL-EU</LogicalID>
<ComponentID>LogisticsModule</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2026-05-15T10:15:00Z</CreationDateTime>
<BODID>5a8f7d2e-2b15-4c1a-9e6f-acknowledgeshipment-2026-0014</BODID>
</ApplicationArea>
<DataArea>
<Acknowledge/>
<Shipment>
<ShipmentHeader>
<DocumentID><ID>SHP-2026-019823</ID></DocumentID>
<DocumentDateTime>2026-05-15T08:00:00Z</DocumentDateTime>
<ShipDate>2026-05-15</ShipDate>
<EstimatedDeliveryDate>2026-05-17</EstimatedDeliveryDate>
</ShipmentHeader>
<ShipUnit>
<ShipUnitIdentifier><ID>PAL-001</ID></ShipUnitIdentifier>
<PackagingDescription>Palette Euro</PackagingDescription>
</ShipUnit>
</Shipment>
</DataArea>
</AcknowledgeShipment> Use case
A warehouse WMS receives a ProcessShipment and responds with AcknowledgeShipment: accepted for the requested date, 2pm-4pm slot confirmed at dock 7. Planning is instant and does not wait for physical arrival.
EDI equivalences
On an EDI gateway, this BOD typically maps to:
- EDIFACT DESADV — EDIFACT equivalent.
- X12 856 — X12 equivalent.
Further reading
- OAGi — OAGIS 10.x — official spec page and free download.
- OAGi (OAGIS) — hub on ediverse — BOD architecture, verbs, canonical model.
- EDIFACT on ediverse — functional equivalent EDIFACT DESADV.
- X12 on ediverse — functional equivalent X12 856.