PIP 3A8 — Request Purchase Order Change

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 3A8 is the inverse of 3A7: the buyer requests a change to an ongoing order (quantity revision, delivery change, line addition). The seller responds with an accepted or rejected confirmation, line by line.

Message structure

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

Primary action: Purchase Order Change Request Action
Signal: Receipt Acknowledgment
Response action: Purchase Order Change 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-3A8.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>3A8</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3A8.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3A8PurchaseOrderChangeRequest xmlns="http://www.rosettanet.org/PIP3A8">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <PurchaseOrderChange>
        <PurchaseOrderIdentifier>
          <ProprietaryDocumentIdentifier>PO-2026-987654</ProprietaryDocumentIdentifier>
        </PurchaseOrderIdentifier>
        <ProductLineItem>
          <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
          <requestedQuantity>
            <ProductQuantity>60000</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </requestedQuantity>
          <ChangeReason>
            <GlobalChangeReasonCode>BuyerRequestedQuantityIncrease</GlobalChangeReasonCode>
          </ChangeReason>
        </ProductLineItem>
      </PurchaseOrderChange>
</Pip3A8PurchaseOrderChangeRequest>

Transport and acknowledgment

Standard asynchronous cycle: RNIF V02.00, HTTPS POST or AS2. The PIP 3A8 confirmation can, in some profiles, be returned synchronously (urgent pricing negotiation).

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 raises its production forecast and requests to bump the order from 50,000 to 60,000 wafers. PIP 3A8 describes the new requested quantity per line and the reason (forecast increase). The foundry responds with a PIP 3A8 confirmation within hours.

Foundations

Standards

Flagship messages

Tools