ProcessPurchaseOrder

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

BOD purpose

The ProcessPurchaseOrder BOD is the canonical equivalent of an EDIFACT ORDERS or X12 850 in the OAGi ecosystem: a buyer issues a purchase order to a supplier. The DataArea contains the Process verb and the PurchaseOrder noun, with a header (parties, dates, currency, terms) and lines (item, quantity, unit price, taxes).

Structure (ApplicationArea + DataArea)

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

• PurchaseOrderHeader — header: DocumentID, DocumentDateTime, BuyerParty, SupplierParty, RequestedDeliveryDateTime.
• PurchaseOrderLine — line: LineNumber, Item (with ItemIDs/ID), Quantity (with unitCode), UnitPrice/Amount (with currencyID).
• Process verb with ActionCriteria/ActionExpression (typically actionCode='Add').

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"?>
<ProcessPurchaseOrder
    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-processpurchaseorder-2026-0014</BODID>
  </ApplicationArea>

  <DataArea>
    <Process>
      <ActionCriteria>
        <ActionExpression actionCode="Add"/>
      </ActionCriteria>
    </Process>
    <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>
</ProcessPurchaseOrder>

Use case

A central ERP distributes to its strategic supplier order system a ProcessPurchaseOrder BOD: 240 bearings at €8.40 delivered within three weeks. The canonical BOD is translated to EDI X12 850 in some channels, to EDIFACT ORDERS in others, but its OAGIS version remains the master on the ERP vendor side.

EDI equivalences

On an EDI gateway, this BOD typically maps to:

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