PIP 3A5 — Query Order Status

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 3A5 lets the buyer query at any time the current state of an already-issued order, by identifier. The seller responds with the global status (Accepted, In Progress, Shipped, Closed) and line-by-line detail. It is the pull equivalent of the push PIP 3A6.

Message structure

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

• Primary action: Query Order Status Request Action
• Signal: Receipt Acknowledgment
• Response action: Query Order Status Response 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:

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

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

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

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 3A5 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"?>
<Pip3A5QueryOrderStatusRequest xmlns="http://www.rosettanet.org/PIP3A5">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <PurchaseOrderIdentifier>
        <ProprietaryDocumentIdentifier>PO-2026-987654</ProprietaryDocumentIdentifier>
      </PurchaseOrderIdentifier>
      <QueryRequestedScope>
        <GlobalQueryScopeCode>FullOrder</GlobalQueryScopeCode>
      </QueryRequestedScope>
</Pip3A5QueryOrderStatusRequest>

Transport and acknowledgment

Typical synchronous mode: direct HTTPS, ideal for ERP-to-ERP integration. AS2 used when a middleware sits on the path.

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

A buyer ERP periodically queries (every 4 hours) the status of open orders with a strategic supplier. The outbound PIP 3A5 triggers a PIP 3A5 response on the seller side, which feeds the buyer dashboard near real-time.

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.