PIP 4B2 — Notify of Shipment Receipt

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

PIP purpose

PIP 4B2 confirms on the recipient side the reception of a shipment announced by a PIP 3B2. Detail of quantities actually received, gaps (missing, overage, damaged), effective receipt date and location. Closes the loop with the ASN.

Message structure

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

Action: Notify of Shipment Receipt 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-4B2.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>4B2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4B2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4B2NotifyOfShipmentReceipt xmlns="http://www.rosettanet.org/PIP4B2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ShipmentReceipt>
        <ShipmentIdentifier>
          <ProprietaryDocumentIdentifier>ASN-2026-019823</ProprietaryDocumentIdentifier>
        </ShipmentIdentifier>
        <receiptDate>
          <DateStamp>20260714</DateStamp>
        </receiptDate>
        <ProductLineItem>
          <ProductIdentification>
            <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
          </ProductIdentification>
          <expectedQuantity>
            <ProductQuantity>50000</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </expectedQuantity>
          <receivedQuantity>
            <ProductQuantity>49997</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </receivedQuantity>
        </ProductLineItem>
      </ShipmentReceipt>
</Pip4B2NotifyOfShipmentReceipt>

Transport and acknowledgment

Asynchronous emission, RNIF V02.00 over HTTPS POST or AS2. Often automated via WMS scan at the receiving dock.

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

An OEM warehouse checks on arrival a foundry delivery: 49,997 wafers counted against 50,000 expected. A PIP 4B2 is generated to notify the supplier; a gap of 3 units is flagged and triggers a partial credit via PIP 3C3.

Foundations

Standards

Flagship messages

Tools