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 CancelPurchaseOrder

CancelPurchaseOrder

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

BOD purpose

The CancelPurchaseOrder BOD totally or partially cancels an order already emitted by ProcessPurchaseOrder. The buyer identifies the PO by its DocumentID and specifies the scope (FullOrder, SpecificLines), with a reason (BuyerCancelled, BuyerProgramRetired, BuyerForecastDecrease).

Structure (ApplicationArea + DataArea)

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

  • PurchaseOrderHeader/DocumentID — reference to the PO to cancel.
  • CancellationScope — FullOrder or SpecificLines.
  • CancellationReason — code and free description.
  • Cancel verb.

XML example

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

xml CancelPurchaseOrder-OAGIS-10.xml
<?xml version="1.0" encoding="UTF-8"?>
<CancelPurchaseOrder
    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-cancelpurchaseorder-2026-0014</BODID>
  </ApplicationArea>

  <DataArea>
    <Cancel>
      <CancellationReason>BuyerProgramRetired</CancellationReason>
    </Cancel>
    <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>
</CancelPurchaseOrder>

Use case

A product programme is cancelled following a strategic review. The ERP emits a CancelPurchaseOrder to the supplier, scope FullOrder, reason BuyerProgramRetired. The supplier withdraws lines not yet in production and confirms with an AcknowledgePurchaseOrder.

EDI equivalences

On an EDI gateway, this BOD typically maps to:

  • EDIFACT ORDCHG — EDIFACT equivalent.
  • X12 860 — X12 equivalent.

Further reading

Last updated: May 15, 2026

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