Boomi

Implementation Of Request Purchase Order-3A4 Using RosettaNet Standard

Introduction:

  • RosettaNet is an XML-based document standard that defines message guidelines, business process interfaces, and frameworks for interactions between major computer, consumer electronics, semiconductor manufacturers, telecommunications, and logistics companies.
  • A RosettaNet message is a standardized data interchange format developed by the non-profit consortium RosettaNet. This format, based on XML, is used by trading partners in the electronics industry to exchange business documents and information in a structured manner.
  • These messages confirm to RosettaNet’s specific standards for various business processes, such as supply chain management and order processing.
  • The goal is to enable seamless and automated business-to-business interactions, reducing the need for manual intervention and enhancing the efficiency of electronic business processes.
  • It’s important to recognize that the details of a RosettaNet message can vary based on the specific business process and the version of RosettaNet standards being employed. Organizations in the electronics industry leverage these standards to streamline and enhance B2B transactions.
  • Using RosettaNet Partner Interface Processes (PIPs), business partners of all sizes can connect electronically to process transactions and move information within their extended supply chains.

List of RosettaNet PIP(Partner Interface Processes) standard transaction message formats:

3A1Request Quote
3A2Request Price and Availability
3A3Request Shopping Cart Transfer
3A4Request Purchase Order
3A5Query Order Status
3A6Distribute Order Status
3A7Notify of Purchase Order Update
3A8Request Purchase Order Change
3A9Request Purchase Order Cancellation
3A10Notify of Quote Acknowledgement
3A13Notify of Purchase Order Information
3A14Distribute Planned Order
3B1Distribute Transportation Projection
3B2Notify of Advance Shipment
3B3Distribute Shipment Status
3B4Query Shipment Status
3B5Request Shipment Change
3B6Notify of Shipments Tendered
3B11Notify of Shipping Order
3B12Request Shipping Order
3B13Notify of Shipping Order Confirmation
3B14Request Shipping Order Cancellation
3B18Notify of Shipment Documentation
3C1Return Product
3C2Request Financing Approval
3C3Notify of Invoice
3C4Notify of Invoice Reject
3C5Notify of Billing Statement
3C6Notify of Remittance Advice
3C7Notify of Self-Billing Invoice

Use-case: Let us see the Implementation of Request Purchase Order-3A4 using RosettaNet standard.

Practical Implementation in Boomi:

Step 01: Create a new process component.

Step 02: Select start shape with connector, select Web Services Server connector, and click ok.

Step 03: In the operation click on the + icon to create a new operation.

Step 04: Rename the operation component.

Step 05: Pass the value for Object field, select Expected input type and Response Output type as Single Data. Select OK.

Step 06: Add a Disk connector followed by a Stop shape.

Step 07: Click on the Disk connector, now we will create a connection component of the disk. Click on the + icon.

Step 08:  Rename the component, paste the folder path for the response data, and click on save.

Step 09: Select action as Send, for the operation component click on the + icon.

Step 10: Rename the operation component and save it.

Step 11: The process will look like this, now save it.

Step 12: Select the developed process.

Step 13: Give the version for the component & create a packaged component.

Step 14: Select the environment and deploy it.

Step 15: In order to send the details we need to create a new process.

Step 16: Rename the process component and add a message shape, a Trading Partner shape, and a stop shape atthe error path.

Step 17: Paste the below-mentioned sample data in message shape.

<ProcessSpecification xmlns=”http://www.rosettanet.org/XSD/RosettaNet” version=”3.0″ release=”20030530″>

  <PIPId>PIP3A4</PIPId>

  <GlobalProcessCode>REQUEST_PURCHASE_ORDER</GlobalProcessCode>

  <DocumentId>

    <DocumentIdentifier>123456789</DocumentIdentifier>

    <VersionIdentifier>1</VersionIdentifier>

    <RevisionIdentifier>0</RevisionIdentifier>

  </DocumentId>

  <ActivityId>

    <Identifier>1</Identifier>

  </ActivityId>

  <From>

    <GlobalPartnerRoleCode>Buyer</GlobalPartnerRoleCode>

    <PartnerLocationID>1234</PartnerLocationID>

    <GlobalPartnerClassificationCode>Customer</GlobalPartnerClassificationCode>

    <GlobalUsageCode>Test</GlobalUsageCode>

    <SupplyChainCode>Direct</SupplyChainCode>

  </From>

  <To>

    <GlobalPartnerRoleCode>Seller</GlobalPartnerRoleCode>

    <PartnerLocationID>5678</PartnerLocationID>

    <GlobalPartnerClassificationCode>Supplier</GlobalPartnerClassificationCode>

    <GlobalUsageCode>Test</GlobalUsageCode>

    <SupplyChainCode>Manufacturer</SupplyChainCode>

  </To>

  <Data>

    <RequestPurchaseOrder>

      <PurchaseOrderHeader>

        <OrderNumber>PO123</OrderNumber>

        <OrderDate>2023-01-01</OrderDate>

      </PurchaseOrderHeader>

      <PurchaseOrderLine>

        <LineNumber>1</LineNumber>

        <Item>

          <ItemID>

            <ManufacturerPartID>ABC123</ManufacturerPartID>

          </ItemID>

        </Item>

        <Quantity>100</Quantity>

        <UnitPrice>10.00</UnitPrice>

      </PurchaseOrderLine>

    </RequestPurchaseOrder>

  </Data>

</ProcessSpecification>

Step 18: Create a new Trading partner component for MyCompany, its Type => Trading Partner component, Standard => RosettaNet and Options => This is my Company and click on create.

Step 19: A new trading partner component will be created, rename the component and fill all the details as shown below by referring the sample payload mentioned in the Step 17.

Step 20: In order transfer the data between two or more organizations we need to agree upon a communication method. Now click on add communication method as HTTP and click create button.

Step 21: Click on Manage => atom Management => our local atom => Shared Web Server and copy the base URL for API request.

Step 22: Paste the URL in the HTTP communication method of the Trading Partner.

Step 23: Now go to the Exposed process, click on the operation.

Step 24: Copy the simple URL path.

Step 24:  Append the Simple URL with the base API path in the HTTP communication method as shown below.

Step 25: Close and save the My Company Trading Partner component.

Step 26: Now Create a new component its Type => Trading Partner component, Standard => RosettaNet and Options => This is a partner that I trade with and click on create.

Step 27: A new trading partner component will be created, rename the component and fill in all the details as shown below by referring to the sample payload mentioned in Step 17.

Step 28: Now go to the communication tab and add the communication method as HTTP.

Step 29: Don’t make any changes in the communication settings let it be as Use all defaults, close and save it.

Step 30: Click on the Trading Partner shape.

Step 31: Select the communication method as HTTP from the drop-down and click on add a standard for my company.

Step 32: Select the standard as RosettaNet and in My Company options select the previously created Trading partner as my company and click OK.

Step 32: Click on Add a Trading Partner, Select the standard as RosettaNet and the previously created Trading Partner.

Step 33: It will look like the below picture click on OK.

Step 34: Save it and the process will look like as shown below and test the process.

Step 35: The process has been executed successfully.

Step 36: Now let us check the disk path that we have provided in Step 08, We have received a file lets open it.

Step 37: We have got the RosettaNet message along with the document.

This is how we can request Purchase Order-3A4 using the RosettaNet standard.

References:

https://help.boomi.com/docs/atomsphere/integration/process%20building/r-atm-trading_partner_rosettanet_standard_tab_a022ac14-ab2d-4713-82d3-e2b0dfd88950

Author

Sharukh Khan

Leave a comment

Your email address will not be published. Required fields are marked *