RosettaNet - Document Structure

RosettaNet is a set of open XML-based standards designed to align processes and enable seamless communication between businesses, particularly in the supply chain and electronic components industry. The RosettaNet standard is widely adopted in industries such as electronics, telecommunications, and IT for business-to-business (B2B) document exchanges.

RosettaNet defines Partner Interface Processes (PIPs) that describe specific business processes and document structures to automate and standardize transactions like purchase orders, invoices, and shipping notices.

1. RosettaNet PIP Document Structure

A RosettaNet message is typically made up of two parts:

1. Service Header: Contains information about the transaction, including the sender, receiver, and message type.
2. Service Content: Contains the actual business information (such as an order or invoice).

Each document is formatted in XML and follows a hierarchical structure based on predefined PIP specifications. A PIP generally includes:

• Business action request (e.g., placing an order).
• Business action response (e.g., confirming the order).

2. Structure Components

2.1 Service Header

The Service Header provides essential information about the business transaction, such as:

• Message ID: A unique identifier for the transaction.
• Sender and Receiver Information: Identifies the business entities involved.
• Timestamp: When the message was sent.
• PIP Identifier: Specifies the business process the message relates to (e.g., Purchase Order, Invoice).

Example:

<ServiceHeader>
  <MessageID>1234567890</MessageID>
  <Timestamp>2024-09-10T12:00:00Z</Timestamp>
  <Sender>
    <PartnerIdentification>
      <PartnerID>SenderCompanyID</PartnerID>
    </PartnerIdentification>
  </Sender>
  <Receiver>
    <PartnerIdentification>
      <PartnerID>ReceiverCompanyID</PartnerID>
    </PartnerIdentification>
  </Receiver>
  <PIPCode>3A4</PIPCode> <!-- PIP for Purchase Order Request -->
</ServiceHeader>

• MessageID: Unique ID of the message.
• PIPCode: Identifies the PIP (e.g., "3A4" for Purchase Order Request).

2.2 Service Content

The Service Content section contains the actual business data related to the PIP. Depending on the PIP being used, this could be details about an order, an invoice, or shipment status.

Example for PIP 3A4 (Purchase Order Request):

<ServiceContent>
  <PurchaseOrderRequest>
    <OrderHeader>
      <OrderNumber>PO123456</OrderNumber>
      <OrderDate>2024-09-10</OrderDate>
    </OrderHeader>
    <OrderItems>
      <Item>
        <LineNumber>1</LineNumber>
        <PartNumber>ABC123</PartNumber>
        <Quantity>100</Quantity>
        <UnitPrice>15.00</UnitPrice>
      </Item>
      <Item>
        <LineNumber>2</LineNumber>
        <PartNumber>XYZ456</PartNumber>
        <Quantity>50</Quantity>
        <UnitPrice>20.00</UnitPrice>
      </Item>
    </OrderItems>
    <ShippingInformation>
      <ShipTo>
        <Company>ReceiverCompany</Company>
        <Address>
          <Street>Main Street 123</Street>
          <City>CityName</City>
          <CountryCode>US</CountryCode>
        </Address>
      </ShipTo>
      <ShipDate>2024-09-15</ShipDate>
    </ShippingInformation>
  </PurchaseOrderRequest>
</ServiceContent>

• OrderHeader: Contains metadata about the purchase order, such as the order number and date.
• OrderItems: Contains individual items in the order, each with details like the part number, quantity, and price.
• ShippingInformation: Provides shipping details, including the shipping address and the expected ship date.

3. RosettaNet PIPs

RosettaNet defines several PIPs for different types of transactions, categorized into clusters and segments based on the type of business process. Common PIPs include:

• PIP 3A4: Purchase Order Request.
• PIP 3B2: Invoice.
• PIP 3B12: Advanced Shipment Notification.

Each PIP has its own document structure and guidelines for how the transaction should be handled.

4. Example of a Complete RosettaNet PIP Message (PIP 3A4 - Purchase Order)

<BusinessMessage>
  <ServiceHeader>
    <MessageID>1234567890</MessageID>
    <Timestamp>2024-09-10T12:00:00Z</Timestamp>
    <Sender>
      <PartnerIdentification>
        <PartnerID>SenderCompanyID</PartnerID>
      </PartnerIdentification>
    </Sender>
    <Receiver>
      <PartnerIdentification>
        <PartnerID>ReceiverCompanyID</PartnerID>
      </PartnerIdentification>
    </Receiver>
    <PIPCode>3A4</PIPCode>
  </ServiceHeader>

  <ServiceContent>
    <PurchaseOrderRequest>
      <OrderHeader>
        <OrderNumber>PO123456</OrderNumber>
        <OrderDate>2024-09-10</OrderDate>
      </OrderHeader>
      <OrderItems>
        <Item>
          <LineNumber>1</LineNumber>
          <PartNumber>ABC123</PartNumber>
          <Quantity>100</Quantity>
          <UnitPrice>15.00</UnitPrice>
        </Item>
        <Item>
          <LineNumber>2</LineNumber>
          <PartNumber>XYZ456</PartNumber>
          <Quantity>50</Quantity>
          <UnitPrice>20.00</UnitPrice>
        </Item>
      </OrderItems>
      <ShippingInformation>
        <ShipTo>
          <Company>ReceiverCompany</Company>
          <Address>
            <Street>Main Street 123</Street>
            <City>CityName</City>
            <CountryCode>US</CountryCode>
          </Address>
        </ShipTo>
        <ShipDate>2024-09-15</ShipDate>
      </ShippingInformation>
    </PurchaseOrderRequest>
  </ServiceContent>
</BusinessMessage>

5. Key Elements of RosettaNet Documents

• Standardization: RosettaNet ensures a high level of standardization across industries, particularly in electronics and IT, making it easier to exchange documents between global partners.
• PIPs: Business processes are modularized into PIPs, making it easy to define specific transaction types (such as ordering, invoicing, etc.).
• XML Format: The use of XML makes RosettaNet flexible and machine-readable, which simplifies integration between different systems.