PIP 4C2 — Distribute Inventory Status

RosettaNet choreography in cluster 4, transported on RNIF V02.00 and signed with S/MIME. Operational unit between Seller and Buyer across the high-tech supply chain.

PIP purpose

PIP 4C2 distributes a detailed inventory status from seller to buyer: current stock level, incoming stock (open PO), committed allocations. A B2B supply-chain visibility building block. No business confirmation, just a Receipt Acknowledgment.

Message structure

The 4C2 choreography follows the RosettaNet action model:

Primary action: Inventory Status Notification Action
Signal: Receipt Acknowledgment (RNIF)
Response action: Receipt Acknowledgment

The 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-4C2.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>4C2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- PIP 4C2 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4C2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4C2InventoryStatusNotification xmlns="http://www.rosettanet.org/PIP4C2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <InventoryStatusReport>
      <reportIdentifier>
        <ProprietaryDocumentIdentifier>INV-STATUS-2026-138</ProprietaryDocumentIdentifier>
      </reportIdentifier>
      <reportPeriod>
        <DateStamp>20260516</DateStamp>
      </reportPeriod>
      <InventoryStatusLineItem>
        <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141333333</GlobalProductIdentifier>
        </ProductIdentification>
        <onHandQuantity><ProductQuantity>3200</ProductQuantity></onHandQuantity>
        <onOrderQuantity><ProductQuantity>12000</ProductQuantity></onOrderQuantity>
        <committedQuantity><ProductQuantity>2000</ProductQuantity></committedQuantity>
      </InventoryStatusLineItem>
    </InventoryStatusReport>
</Pip4C2InventoryStatusNotification>

Transport and acknowledgment

Core of the standard: HTTPS POST to the partner endpoint or via AS2. S/MIME signature and Receipt Acknowledgment are systematic. PIP 4C2 is typically transported asynchronously.

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

ASE Group distributes a daily PIP 4C2 inventory status to TSMC for wafers in assembly: 3,200 available, 12,000 incoming within 14 days, 2,000 allocated to TSMC over the next 7 days.

Foundations

Standards

Flagship messages

Tools