ProcessSalesOrder

OAGIS BOD combining the Process 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 ProcessSalesOrder BOD records on the seller side a sales order issued by a commercial channel (e-commerce, sales force, EDI). It is the internal mirror of the buyer-side ProcessPurchaseOrder: same nature, opposite direction.

Structure (ApplicationArea + DataArea)

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

• SalesOrderHeader — DocumentID, parties, currency, terms.
• SalesOrderLine — item, ordered quantity, net price.

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"?>
<ProcessSalesOrder
    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-processsalesorder-2026-0014</BODID>
  </ApplicationArea>

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

Use case

A B2B e-commerce site confirms a basket of 12 item lines: ProcessSalesOrder is generated on the platform side and emitted to the back-office ERP, which creates the corresponding sales order within seconds.

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.