PIP 4B3 — Notify of Consumption

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

PIP purpose

PIP 4B3 notifies an inventory consumption as part of a VMI (Vendor-Managed Inventory) or consignment programme. The buyer signals to the seller the quantity consumed at a given location, which triggers a downstream PIP 3A4 or 3B12 replenishment. No business confirmation.

Message structure

The 4B3 choreography follows the RosettaNet action model:

Primary action: Consumption 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-4B3.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>4B3</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4B3.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4B3ConsumptionNotification xmlns="http://www.rosettanet.org/PIP4B3">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <ConsumptionDocument>
      <consumptionIdentifier>
        <ProprietaryDocumentIdentifier>CONS-2026-D138-PEO</ProprietaryDocumentIdentifier>
      </consumptionIdentifier>
      <ConsumptionLineItem>
        <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141222225</GlobalProductIdentifier>
        </ProductIdentification>
        <consumedQuantity>
          <ProductQuantity>320</ProductQuantity>
          <unitOfMeasure>EA</unitOfMeasure>
        </consumedQuantity>
        <consumptionLocation>
          <GlobalLocationIdentifier>0061414155551</GlobalLocationIdentifier>
        </consumptionLocation>
      </ConsumptionLineItem>
    </ConsumptionDocument>
</Pip4B3ConsumptionNotification>

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 4B3 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

Caterpillar sends Bosch a daily PIP 4B3 consumption notification covering actual sensor usage at its Peoria assembly site, triggering the downstream consignment replenishment chain.

Foundations

Standards

Flagship messages

Tools