PIP 3A9 — Request Purchase Order Cancellation

RosettaNet choreography in cluster 3 (Order Management), covering the XML exchange between Buyer ↔ Seller. Operational unit for order management on RNIF V02.00.

PIP purpose

PIP 3A9 requests the total or partial cancellation of an already-issued order. The seller responds with a confirmation that can be accepted, refused (order already in production), or partial (cancellation of lines still available).

Message structure

The 3A9 choreography follows the two-action (request / response) RosettaNet model:

Primary action: Purchase Order Cancellation Request Action
Signal: Receipt Acknowledgment
Response action: Purchase Order Cancellation Confirmation Action

Each action is wrapped in a multipart MIME RNIF V02.00 envelope signed with S/MIME. Here is a condensed view of the envelope:

text rnif-envelope-3A9.eml

MIME-Version: 1.0
Content-Type: multipart/related; type="application/xml";
  boundary="RN-BOUNDARY-2026"

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-Preamble.xml

<Preamble xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <standardName>RosettaNet</standardName>
  <standardVersion>V02.00</standardVersion>
</Preamble>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-ServiceHeader.xml

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalProcessIndicatorCode>3A9</GlobalProcessIndicatorCode>
</ServiceHeader>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: Pip3A9PurchaseOrderCancellationRequest.xml

<!-- payload PIP 3A9 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 3A9 payload for didactic purposes. The structural elements (fromRole, toRole, thisDocumentGenerationDateTime, and the PIP-specific business block) are required in any conformant implementation.

xml pip-3A9.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3A9PurchaseOrderCancellationRequest xmlns="http://www.rosettanet.org/PIP3A9">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <PurchaseOrderCancellation>
        <PurchaseOrderIdentifier>
          <ProprietaryDocumentIdentifier>PO-2026-987654</ProprietaryDocumentIdentifier>
        </PurchaseOrderIdentifier>
        <CancellationScope>
          <GlobalCancellationScopeCode>FullOrder</GlobalCancellationScopeCode>
        </CancellationScope>
        <CancellationReason>
          <GlobalCancellationReasonCode>BuyerRequested</GlobalCancellationReasonCode>
        </CancellationReason>
      </PurchaseOrderCancellation>
</Pip3A9PurchaseOrderCancellationRequest>

Transport and acknowledgment

Asynchronous cycle: RNIF V02.00, HTTPS POST or AS2. The cancellation reason is typically expected on the supplier audit side (churn analysis).

The transport channel is typically AS2 or direct HTTPS (RNIF over HTTP). For a reference of the security layers in use, see the AS2 on ediverse page.

Use case

An OEM must pull a product programme and requests full cancellation of an in-progress wafer order. PIP 3A9 is sent to the foundry; the PIP 3A9 confirmation response can partially accept (lines not yet in production cancelled) and refuse the rest.

Foundations

Standards

Flagship messages

Tools