PIP 3A6 — Distribute Order Status

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

PIP purpose

PIP 3A6 is the push equivalent of PIP 3A5: the seller distributes to the buyer the current status or a state change of an order (move to Production, Stock allocation, imminent shipment). Often emitted on a business event (status change, date drift).

Message structure

The 3A6 choreography follows the one-action (notification) RosettaNet model:

• Action: Distribute Order Status Action
• Signal: Receipt Acknowledgment

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

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>3A6</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

<?xml version="1.0" encoding="UTF-8"?>
<Pip3A6DistributeOrderStatus xmlns="http://www.rosettanet.org/PIP3A6">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <PurchaseOrderIdentifier>
        <ProprietaryDocumentIdentifier>PO-2026-987654</ProprietaryDocumentIdentifier>
      </PurchaseOrderIdentifier>
      <OrderStatus>
        <GlobalOrderStatusCode>InProgress</GlobalOrderStatusCode>
        <StatusDateTime>
          <DateTimeStamp>20260515T091000Z</DateTimeStamp>
        </StatusDateTime>
      </OrderStatus>
</Pip3A6DistributeOrderStatus>

Transport and acknowledgment

Asynchronous emission by default, RNIF V02.00 over HTTPS POST or AS2. Receipt Acknowledgment confirmed back, no response payload.

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

AMD switches order PO-2026-987654 from Accepted to In Progress. A PIP 3A6 is generated automatically and sent to TSMC. The buyer system updates its tracking dashboard without any human intervention.

Further reading

• RosettaNet Standards Programme — GS1 US — official PIP catalogue.
• RosettaNet PIP Catalog (web.archive.org) — historical version of the rosettanet.org catalogue before its 2013 retirement.
• RosettaNet — hub on ediverse — overview, PIP / RNIF architecture, and clusters.
• AS2 on ediverse — alternative transport compatible with RNIF.