GetPurchaseOrder
OAGIS BOD combining the Get 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 GetPurchaseOrder BOD requests the current read of one or more existing orders. The target system returns a ShowPurchaseOrder with the requested data, identified by DocumentID, date range, or status.
Structure (ApplicationArea + DataArea)
Like every OAGIS BOD, GetPurchaseOrder stacks an ApplicationArea
technical envelope (Sender, BODID, CreationDateTime) and a business DataArea
that contains the verb and the noun.
Getverb withExpression(XPath filter or criterion).PurchaseOrdernoun typically empty or partially filled to specify the response detail.ResponseCriteria— specifies the depth of the response (header only, header + lines).
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"?>
<GetPurchaseOrder
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-getpurchaseorder-2026-0014</BODID>
</ApplicationArea>
<DataArea>
<Get>
<Expression expressionLanguage="XPath">//PurchaseOrder[Status='New']</Expression>
</Get>
<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>
</GetPurchaseOrder>Use case
A supplier portal queries the ERP customer system every hour to fetch any new PO not yet acknowledged. A GetPurchaseOrder is emitted with a Status='New' filter; the ERP responds with a ShowPurchaseOrder listing the new orders.
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.