ProcessShipDelivery — Ship delivery
On this page
OAGIS BOD combining the verb Process and the noun ShipDelivery. Business cornerstone of the logistics domain in the OAGIS 10.x ecosystem.
BOD purpose
The ProcessShipDelivery BOD transmits a ship-delivery order between an ERP (which decides) and a WMS (which prepares and ships). It covers the physical shipment details: pallets, carrier, pickup window.
Structure (ApplicationArea + DataArea)
As every OAGIS BOD, ProcessShipDelivery stacks an
ApplicationArea technical envelope (Sender, BODID, CreationDateTime) and
a DataArea business payload containing the verb Process
and the noun ShipDelivery.
XML example
Minimal OAGIS 10.x payload for didactic purposes. The structural elements (header + business line) are required in any conformant implementation.
<?xml version="1.0" encoding="UTF-8"?>
<ProcessShipDelivery
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-16T10:15:00Z</CreationDateTime>
<BODID>5a8f7d2e-2b15-4c1a-9e6f-processshipdelivery-2026-0014</BODID>
</ApplicationArea>
<DataArea>
<Process>
<ActionCriteria>
<ActionExpression actionCode="Add"/>
</ActionCriteria>
</Process>
<ShipDelivery>
<ShipDeliveryHeader>
<DocumentID><ID>SDEL-2026-04785</ID></DocumentID>
<DocumentDateTime>2026-05-16T10:00:00Z</DocumentDateTime>
<CarrierReference><ID>SCH-DB</ID></CarrierReference>
<PickupDateTime>2026-05-17T14:00:00Z</PickupDateTime>
<NumberOfPallets>12</NumberOfPallets>
</ShipDeliveryHeader>
<ShipDeliveryLine>
<LineNumber>1</LineNumber>
<Item><ItemIDs><ID>RBC-2200</ID></ItemIDs></Item>
<Quantity unitCode="EA">240</Quantity>
</ShipDeliveryLine>
</ShipDelivery>
</DataArea>
</ProcessShipDelivery> Use case
Acme's Oracle Fusion ERP pushes a ProcessShipDelivery to its WMS for 12 pallets of bearing RBC-2200, carrier DB Schenker, pickup on 2026-05-17 at 14:00.
EDI equivalents
No direct EDI counterpart on the gateway: this BOD is strictly internal to the OAGIS / ERP ecosystem, with no openly standardised EDIFACT or X12 counterpart.
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 — comparison baseline for BODs with EDIFACT counterpart.
- X12 on ediverse — comparison baseline for BODs with X12 counterpart.