ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.
BOD GetSalesOrder

GetSalesOrder

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

BOD purpose

The GetSalesOrder BOD queries the ERP to retrieve an existing sales order. Response: ShowSalesOrder (not separately covered here, see mirror with ShowPurchaseOrder).

Structure (ApplicationArea + DataArea)

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

  • Get verb with Expression on DocumentID, period, customer, status.
  • SalesOrder noun partial to specify return scope.

XML example

Minimal OAGIS 10.x payload for didactic purposes. Structural elements (header + at least one line) are required in any conformant implementation.

xml GetSalesOrder-OAGIS-10.xml
<?xml version="1.0" encoding="UTF-8"?>
<GetSalesOrder
    xmlns="http://www.openapplications.org/oagis/10"
    releaseID="10.11" versionID="10.11">

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

  <DataArea>
    <Get>
      <Expression expressionLanguage="XPath">//SalesOrder[Status='New']</Expression>
    </Get>
    <SalesOrder>
      <SalesOrderHeader>
        <DocumentID><ID>SO-2026-019200</ID></DocumentID>
        <DocumentDateTime>2026-05-15T11:00:00Z</DocumentDateTime>
        <CustomerParty>
          <PartyIDs><ID>CUST-009912</ID></PartyIDs>
        </CustomerParty>
      </SalesOrderHeader>
      <SalesOrderLine>
        <LineNumber>1</LineNumber>
        <Item><ItemIDs><ID>RBC-2200</ID></ItemIDs></Item>
        <Quantity unitCode="EA">12</Quantity>
        <UnitPrice><Amount currencyID="EUR">11.20</Amount></UnitPrice>
      </SalesOrderLine>
    </SalesOrder>
  </DataArea>
</GetSalesOrder>

Use case

A customer support team needs the detail of an order mentioned in a ticket. GetSalesOrder with DocumentID is sent to the ERP; the returned ShowSalesOrder directly feeds the response screen.

EDI equivalences

On an EDI gateway, this BOD typically maps to:

Further reading

Last updated: May 15, 2026

Official source: OAGi — OAGIS 10.x — OAGi — OAGIS, free distribution via oagi.org