ProcessReceivedDelivery

OAGIS BOD combining the Process verb with the ReceiveDelivery noun. Direct canonical equivalent of EDI EDIFACT RECADV and X12 861 messages in OAGIS 10.x's Logistics domain.

BOD purpose

The ProcessReceivedDelivery BOD records the physical reception of a delivery on the recipient warehouse side. Detail of received quantities, gaps vs ASN, packaging state, link to originating PO. Functional equivalent of EDIFACT RECADV or X12 861.

Structure (ApplicationArea + DataArea)

Like every OAGIS BOD, ProcessReceivedDelivery stacks an ApplicationArea technical envelope (Sender, BODID, CreationDateTime) and a business DataArea that contains the verb and the noun.

• ReceiveDeliveryHeader — references to the PO and ASN, effective receipt location and date.
• ReceiveDeliveryLine — received quantity, expected quantity, gap, lot, expiry.

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"?>
<ProcessReceivedDelivery
    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-processreceiveddelivery-2026-0014</BODID>
  </ApplicationArea>

  <DataArea>
    <Process>
      <ActionCriteria>
        <ActionExpression actionCode="Add"/>
      </ActionCriteria>
    </Process>
    <ReceiveDelivery>
      <ReceiveDeliveryHeader>
        <DocumentID><ID>RCV-2026-008771</ID></DocumentID>
        <DocumentDateTime>2026-05-15T14:00:00Z</DocumentDateTime>
        <ReceivedAtDateTime>2026-05-15T13:55:00Z</ReceivedAtDateTime>
      </ReceiveDeliveryHeader>
      <ReceiveDeliveryLine>
        <LineNumber>1</LineNumber>
        <Item><ItemIDs><ID>RBC-2200</ID></ItemIDs></Item>
        <ReceivedQuantity unitCode="EA">238</ReceivedQuantity>
        <ExpectedQuantity unitCode="EA">240</ExpectedQuantity>
      </ReceiveDeliveryLine>
    </ReceiveDelivery>
  </DataArea>
</ProcessReceivedDelivery>

Use case

A WMS scans 240 bearings on arrival, identifies two damaged pallets. ProcessReceivedDelivery is emitted to the ERP: 238 units accepted, 2 rejected with reason DamagedInTransit. The ERP corrects the stock and triggers the invoicing cycle.

EDI equivalences

On an EDI gateway, this BOD typically maps to:

• EDIFACT RECADV — EDIFACT equivalent.
• X12 861 — 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 RECADV.
• X12 on ediverse — functional equivalent X12 861.