AcknowledgePurchaseOrder

OAGIS BOD combining the Acknowledge verb with the PurchaseOrder noun. Direct canonical equivalent of EDI EDIFACT ORDRSP and X12 855 messages in OAGIS 10.x's Procurement domain.

BOD purpose

The AcknowledgePurchaseOrder BOD confirms on the supplier side the receipt of a ProcessPurchaseOrder. It is the canonical equivalent of an EDIFACT ORDRSP or X12 855, with line-by-line detail (acceptance, quantity or date adjustment, rejection with reason).

Structure (ApplicationArea + DataArea)

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

• PurchaseOrderHeader — references the originating PO DocumentID, adds Status with a code (Accepted, AcceptedWithChanges, Rejected).
• PurchaseOrderLine — details per line the accepted, changed, or rejected status, with OriginalQuantity and AcknowledgedQuantity if different.
• Acknowledge verb without condition, simple acknowledgment.

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"?>
<AcknowledgePurchaseOrder
    xmlns="http://www.openapplications.org/oagis/10"
    releaseID="10.11" versionID="10.11">

  <ApplicationArea>
    <Sender>
      <LogicalID>ERP-CENTRAL-EU</LogicalID>
      <ComponentID>ProcurementModule</ComponentID>
      <ConfirmationCode>OnError</ConfirmationCode>
    </Sender>
    <CreationDateTime>2026-05-15T10:15:00Z</CreationDateTime>
    <BODID>5a8f7d2e-2b15-4c1a-9e6f-acknowledgepurchaseorder-2026-0014</BODID>
  </ApplicationArea>

  <DataArea>
    <Acknowledge/>
    <PurchaseOrder>
      <PurchaseOrderHeader>
        <DocumentID><ID>PO-2026-000871</ID></DocumentID>
        <DocumentDateTime>2026-05-15T10:00:00Z</DocumentDateTime>
        <BuyerParty>
          <PartyIDs><ID>4012345678901</ID></PartyIDs>
          <Name>Acme Industries</Name>
        </BuyerParty>
        <SupplierParty>
          <PartyIDs><ID>5790000123456</ID></PartyIDs>
          <Name>Northern Components</Name>
        </SupplierParty>
        <RequestedDeliveryDateTime>2026-06-04T08:00:00Z</RequestedDeliveryDateTime>
      </PurchaseOrderHeader>
      <PurchaseOrderLine>
        <LineNumber>1</LineNumber>
        <Item>
          <ItemIDs><ID>RBC-2200</ID></ItemIDs>
          <Description>Roulement à billes 22 mm</Description>
        </Item>
        <Quantity unitCode="EA">240</Quantity>
        <UnitPrice><Amount currencyID="EUR">8.40</Amount></UnitPrice>
      </PurchaseOrderLine>
    </PurchaseOrder>
  </DataArea>
</AcknowledgePurchaseOrder>

Use case

A supplier receives a PO for 240 bearings and confirms acceptance of 200 for the requested date, plus 40 for a one-week-later delivery. The AcknowledgePurchaseOrder BOD is routed to the buyer ERP, which updates its receiving window.

EDI equivalences

On an EDI gateway, this BOD typically maps to:

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