PIP 4C1 — Distribute Inventory Report

RosettaNet choreography in cluster 4 (Inventory Management), covering the XML exchange between Inventory Holder ↔ Inventory Consumer. Operational unit for inventory management on RNIF V02.00.

PIP purpose

PIP 4C1 distributes in push an inventory report (per MPN, per lot, per location) between a stock holder (supplier, distributor, 3PL) and a consumer (buyer, brand). Fundamental unit of VMI and sell-through tracking in semiconductor distribution.

Message structure

The 4C1 choreography follows the one-action (notification) RosettaNet model:

Action: Distribute Inventory Report 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:

text rnif-envelope-4C1.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>4C1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 4C1 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4C1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4C1DistributeInventoryReport xmlns="http://www.rosettanet.org/PIP4C1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>InventoryHolder</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>InventoryConsumer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <InventoryReport>
        <ReportIdentifier>
          <ProprietaryDocumentIdentifier>INV-RPT-2026-W21</ProprietaryDocumentIdentifier>
        </ReportIdentifier>
        <reportDate>
          <DateStamp>20260518</DateStamp>
        </reportDate>
        <InventoryLineItem>
          <ProductIdentification>
            <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
          </ProductIdentification>
          <onHandQuantity>
            <ProductQuantity>3200</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </onHandQuantity>
          <reservedQuantity>
            <ProductQuantity>800</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </reservedQuantity>
        </InventoryLineItem>
      </InventoryReport>
</Pip4C1DistributeInventoryReport>

Transport and acknowledgment

Periodic emission (weekly or daily), RNIF V02.00 over HTTPS POST or AS2. Often high payload volume: transport-level compression recommended.

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 distributes every Monday morning to its partner manufacturers a consolidated inventory report: MPN, available quantity, reserved quantity, allocated quantity. PIP 4C1 feeds forecasting and reallocation models on the brand owner side.

Foundations

Standards

Flagship messages

Tools