PIP 3B2 — Notify of Advance Shipment

RosettaNet choreography in cluster 3 (Order Management — Shipment), covering the XML exchange between Shipper ↔ Receiver. Operational unit for order management — shipment on RNIF V02.00.

PIP purpose

PIP 3B2 is the equivalent of EDIFACT DESADV or X12 856: the seller or 3PL notifies the recipient of the detail of an upcoming shipment — parcels, pallets, containers, detailed content (LineItem → Package). Enables reception planning and matching validation on arrival.

Message structure

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

Action: Advance Shipment Notification 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-3B2.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>3B2</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3B2.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3B2AdvanceShipmentNotification xmlns="http://www.rosettanet.org/PIP3B2">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Shipper</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Receiver</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <Shipment>
        <ShipmentIdentifier>
          <ProprietaryDocumentIdentifier>ASN-2026-019823</ProprietaryDocumentIdentifier>
        </ShipmentIdentifier>
        <shipDate>
          <DateStamp>20260710</DateStamp>
        </shipDate>
        <ShipmentPackageInformation>
          <numberOfPackages><ProductQuantity>10</ProductQuantity></numberOfPackages>
          <PackageTotalGrossWeight>
            <PhysicalDimensionValue>250.0</PhysicalDimensionValue>
            <PhysicalDimensionUnitOfMeasure>kg</PhysicalDimensionUnitOfMeasure>
          </PackageTotalGrossWeight>
        </ShipmentPackageInformation>
      </Shipment>
</Pip3B2AdvanceShipmentNotification>

Transport and acknowledgment

Typical asynchronous case: RNIF V02.00 over HTTPS POST or AS2. PIP 3B2 is often duplicated with an EDI ASN sent to 3PLs and warehouses that have not migrated to RosettaNet.

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

A foundry ships 50,000 wafers in ten refrigerated containers. PIP 3B2 is generated at loading time and sent ahead of the carrier. The OEM recipient provisions its clean room and syncs its ERP upon receipt of the notification.

Foundations

Standards

Flagship messages

Tools