PIP 2A2 — Query Product Information

RosettaNet choreography in cluster 2 (Product Introduction), covering the XML exchange between Product Information Requester ↔ Product Information Provider. Operational unit for product introduction on RNIF V02.00.

PIP purpose

PIP 2A2 queries a manufacturer product database in pull mode: a distributor, EMS, or buyer requests the current details of one or more identified products (GTIN, MPN). The response returns the same structure as a PIP 2A1, scoped to the requested selection.

Message structure

The 2A2 choreography follows the two-action (request / response) RosettaNet model:

Primary action: Query Product Information Request Action
Signal: Receipt Acknowledgment
Response action: Query Product Information 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:

text rnif-envelope-2A2.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>2A2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 2A2 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-2A2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip2A2QueryProductInformationRequest xmlns="http://www.rosettanet.org/PIP2A2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ProductInformationRequester</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>ProductInformationProvider</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <QueryCriteria>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141000017</GlobalProductIdentifier>
        </ProductIdentification>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141000024</GlobalProductIdentifier>
        </ProductIdentification>
      </QueryCriteria>
      <RequestedInformationScope>
        <GlobalRequestedScopeCode>FullProductInformation</GlobalRequestedScopeCode>
      </RequestedInformationScope>
</Pip2A2QueryProductInformationRequest>

Transport and acknowledgment

Typical synchronous use case: direct HTTPS, request and response in the same TCP cycle. AS2 also works but synchronous mode is no longer guaranteed.

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

Avnet must confirm before a quote that a precise MPN is still active at the manufacturer. It emits a PIP 2A2 to Texas Instruments. The synchronous response, in under two seconds, confirms Active status and standard delivery lead time.

Foundations

Standards

Flagship messages

Tools