Skip to Content

1. Introduction

The following content describes the solution which was implemented for one of the clients. This is the industry specific solution (RNIF – RosettaNet Implementation Framework) which was delivered based on the client requirement. The solution was implemented using SAP middleware product
called SAP Process Integration (PI) which is one of the components in the Netweaver stack.
The brief words about SAP Netwaever are – It is a platform which enables the composition, provisioning, and management of SAP and non-SAP applications across a heterogeneous software environment.
Process Integration is one the three layers in the netwaeverstack. Others are People Integration and Information Integration.
The solution is B2B which integrates the processes across the landscape. The SAP NetWeaver Process Integration B2B IT scenario is a part of SAP Net Weaver Process Integration (PI). The scenario must be configured before execution.
1.1 Business Scenario Overview:
 
Several industry standard organizations have been founded by companies within the same business sector in order to define industry-wide and open standards for their business processes, mainly focusing on their business-to-business (B2B) processes. These standards include RosettaNet for the high tech industry, CIDX (Chemical Industry Data Exchange) for the chemical industry, PIDX (Petroleum Industry Data Exchange) for the oil and gas industry, and UCCNet (Uniform Code Council) for the consumer products and retail industry.

The RosettaNet standard, like other vertical standards,defines collaborative business processes between supply chain trading partners.
The RosettaNet Implementation Framework (RNIF) specifies standardized message exchange at transport, routing, packaging, and transaction level.

  • The B2B adapters provided by SAP NetWeaver Process Integration (SAP PI) follow the industry-specific standards based on the industry which are aligned to:

               – RNIF adapters for the high tech industry, based on RosettaNet protocol RNIF 1.1 and RNIF 2.0

                –  CIDX adapter for the chemical industry, based on RNIF 1.1 protocol

2. Overview

2.1 Overview of the Configuration Procedure

 

The scenario covers the B2B integration of 2 different parties using RNIF solution. The sender (buyer) sends the purchase Order request it will be created in the receiver (Seller) using RNIF adapter frame work in PI.  The key is the “DUN & Bradstreet number” between the two parties to identify uniquely.

Image1.png

  • Purchase order request is sent from the HTTP client to the Integration pipeline.
  • Decentral Adapter engine forwards the Purchase order request message to the Central adapter engine.
  • Central Adapter engine sends back a purchase order confirmation message to the Decentral adapter engine.

 

3. Browsing and Importing ESR Content

3.1 Create Rosettanet SWCV in SLD

 

The appropriate Software Components for the RosettaNet Business Package are available in the SLD as part of the XI Content.

3.2  Download Business Package for RosettaNet and XI Content

To install the Business Package for Rosetta Net, need to download the files from the Service Marketplace.

The Business Package for RosettaNet comes in two archive files in the following format:

  • XI3_0_ROSETTANET_1.0_02_02.tpz
  • XI3_0_ROSETTANET_ERP_1.0_01_00.tpz

3.3 Import SWCV to ESR

Import the downloaded .tpz files for the software components “SAP Basis 6.60”, “ROSETTANET” and “ROSETTANET ERP” as shown below.  This is the predefined content which is available for specific scenarios. In this case no design (IR) is required.

Image2.png

4. Configuration

4.1 Define Parties and Services

Define Parties:  We need to define Parties for the own company and for each of the Business Partners with whom we want to exchange documents.
                           We also need to assign a DUNS number to each of your Business Partner to uniquely identify them.

   

The following information details the roles that individual parties will play within this Scenario for the RosettaNetPIP3A4 Purchase Order Create Scenario.

Buyer – RNetBuyer

 

The buyer configuration is shown in the below screenshot.

Image3.png

Seller – SAPSeller

                  The seller configuration is shown in the  below.

                       Image4.png

Define Services:  We must create a Business Component for the partner using a naming convention. This name binding for the service is
runtime-relevant. The RNIF 2.0 Adapter determines the partner’s service name and the local service name for an incoming RosettaNet Action message based on the selected header fields of the RNIF 2.0 protocol service header. The adapter then constructs the name – according to the below mentioned rules as follows.

The service should comply with the following definition:

PIP<PIP Code>_<PIP Version>_<Partner Role>. The Role should match the one assumed by the Party for which the service is defined.

The Service names for the two parties would be:

                     PIP3A4_V0202_Buyer – for the Buyer

                     PIP3A4_V0202_Seller – for the Seller

4.2 Define Communication Channels

Next we need to configure the adapters with the communication channels.

4.2.1 Buyer_Send_PurchaseOrderRequestAction

Image5.png

The following values should be mentioned in the Source & Process Specification
tab as applicable.

  Transport Parameters

a)  In Source Tab  URL                            De-central adapter Engine URL hooked onto the Integration Server 

                                                                         For eg.  http://<host>:<port>/MessagingSystem/receive/RNIFAdapter/RNIF

b)  Client Authentication Required          Checked

c)  Location

        Current                                             PaloAlto

        Partner                                        Houston

d)  Security Settings

In Process Specification tab

Sign Action Message                              Unchecked

Sign Signal Message                              Unchecked

Non-Repudiation of Origin and content  Unchecked

Non-Repudiation of Receipt Ackn.          Unchecked

e)  Click on tab  “Module’ and insert new line if there being none by using the button  maintain the following values manually

Module Name                                          RNIFModuleListener

Type                                                         Local Enterprise Bean

Module Key                                              RNIF

4.2.2 Create the following communications channels in the Business Service “PIP3A4_V0202_Seller”of the Party “SAPSeller”.

Create Communication Channel: Seller_receive_PurchaseOrderRequestAction under the “Receiver” Tab of “PIP3A4_V0202_Seller”

In the newly created Communication Channel go to the menu “Communication Channel” and click on “Import Template”option and
choose the template “Seller_receive_PurchaseOrderRequestAction” of namespace, http://sap.com/xi/RosettaNet/PIP3A4_V0202
swcv “ROSETTANET 1.0” from the list of templates. This will hence create a Receiver Communication channel with most of the field pre- filled from the
template.

Under the Adapter Engine, select your Decentral Adapter Engine configured to your system from the drop down

In the Process Specification tab enter the following values

             ++ Location: Current “Houston” and Partner “PaloAlto.

             ++ Uncheck all the 4 parameters under Security Policy.

 

Click on theTarget tab enter the following values

             ++ Transport parameters URL   “http://<hostname of XI system>:<Java HTTP port>/MessagingSystem/receive/RNIFAdapter/RNIF” 

                                                                   For e.g., http://ldcin3a:53600/MessagingSystem/receive/RNIFAdapter/RNIF

             ++  Authentication -> Check Client Authentication Require & with user name as “PIAPPLUSER” and relevant password “xxxxxxxx”

Click on tab “Module’ and insert new line if there being none by using the button maintain the following values manually

             ++ Module Name: RNIFModuleListener

             ++ Type: Local Enterprise Bean

             ++ Module Key: RNIF

4.2.3 Create Communication Channel: Seller_Send_PurchaseOrderConfirmationAction for Party “SAPSeller”, Communication Component “PIP3A4_V0202_Seller”, under the “Sender” Tab.

In the newly created Communication Channel go to the menu “Communication Channel” and click on “Import Template” option and choose the template

“Seller_Send_PurchaseOrderConfirmationAction” of namespace  http://sap.com/xi/RosettaNet/PIP3A4_V0202  swcv “ROSETTANET 1.0” from the list of

templates. This will hence create a Sender Communication channel with most of the field pre- filled from the template

Under the Adapter Engine, select your Decentral Adapter Engine configured to your  XI system from the drop down.

In the Process Specification tab Uncheck all the 4 parameters under Security Policy

Click on tab “Module’ and insert new line if there being none by using the button  

Maintain the following values manually

++ Module Name: RNIFModuleListener

++ Type: Local Enterprise Bean

++ Module Key: RNIF

 

4.3  All the other reaming objects like Reciever determination and Interface determination , sender agreement and receiver agreement are also created as part of configuration.

4.4  Additional Manual Configuration:

       An additional communication Component “Legacy_File_System” with Party “RNetBuyer”  is also created  under the Tab Receiver select the Inbound
       Interface “PurchaseOrderConfirmationAction” to receive the final PO Confirmation.

      This file adapter channel is used to store the system acknowledgement on receipt of Purchase Order Confirmation by Buyer.

 

5. Testing Instructions & Execution

    The HTTP test client is used the initiating the request to PI and tested the scenarios.

     

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply