PIP 4A4 — Distribute Planning Release Forecast

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 4A4 distributes a detailed planning release forecast from buyer to seller: planned quantity, delivery window, product identifier (GTIN). The seller receives a planning horizon that guides their internal procurement. There is no business confirmation signal, only an RNIF Receipt Acknowledgment is expected.

Message structure

The 4A4 choreography follows the RosettaNet action model:

Primary action: Planning Release Forecast 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-4A4.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>4A4</GlobalProcessIndicatorCode>
</ServiceHeader>

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

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

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-4A4.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip4A4PlanningReleaseForecastNotification xmlns="http://www.rosettanet.org/PIP4A4">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <PlanningReleaseForecast>
      <forecastReleaseIdentifier>
        <ProprietaryDocumentIdentifier>PRF-2026-W20-014</ProprietaryDocumentIdentifier>
      </forecastReleaseIdentifier>
      <ProductLineItem>
        <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
        </ProductIdentification>
        <forecastQuantity>
          <ProductQuantity>120000</ProductQuantity>
          <unitOfMeasure>EA</unitOfMeasure>
        </forecastQuantity>
        <plannedDeliveryDate>
          <DateStamp>20260612</DateStamp>
        </plannedDeliveryDate>
      </ProductLineItem>
    </PlanningReleaseForecast>
</Pip4A4PlanningReleaseForecastNotification>

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

Apple transmits a weekly PIP 4A4 planning forecast to Foxconn covering 12 million iPhones planned over the next 13 weeks, broken down by colour and capacity.

Foundations

Standards

Flagship messages

Tools