Skip to Content

SAP Manufacturing Scenario Using RNIF to JDBC

Summary :

The purpose of this document is to explain and provide a step-by-step walkthrough to implement

Manufacturing Scenario using RNIF to JDBC. Also this would give a clear picture how to configure the RNIF

and JDBC Adapters with various parameters in SAP XI / PI.

Introduction

A manufacturing execution system (MES) is a control system for managing and monitoring work-in-process

on a factory floor. An MES keeps track of all manufacturing information in real time, receiving up-to-theminute

data from robots, machine monitors and employees.MES is part of the larger factory planning and

control system.

This document will gives clear idea about WIP Data (Work in process ) via B2B using RNIF 7B1 to JDBC

Adapter. At sender side Customer sending the WIP data through RNIF (Rosettanet Implementation

Framework) adapter using PIP 7B1 message, and receiver side we are updating the data in to the tables

using JDBC Adapter.

Business Scenario :

Pre-Requisites :


Basic knowledge of XI,RNIF,Database,XML etc…

Integration Repository :


Sender structure:

  • For Sender download the Standard software component ROSETTANET 1.0/ ROSETTANET 2.0 from service market place and Copy into XI/PI integration Repository Export location. Then import into XI/PI Integration Repository.
  • Create the namespace in the Integration Repository.

Note: You can use either of the following Namespace formats:


Regular Interface Namespace: http://sap.com/xi/RosettaNet/ PIP <PIPCode>_<PIP Version Identifier>

                                Or

Alternate Interface Namespace: http://sap.com/xi/RosettaNet/<PIP Version Identifier>

Ex: http://sap.com/xi/RosettaNet/PIP7B1_V0100

  • Next we can import the corresponding DTD /XSD file

      ‘PIP7B1_MS_V01_00_WorkInProcessNotification’using external definitions. Please find the below screen shot under External definition

Sender dtd file:

Receiver structure:


  • Import the software component that is created in the SLD
  • Create the namespace in the Integration Repository.

Data Type:

Message Type:

Create the message Type for Receiver based on (DT_Report_WIPFlow_Ext) Data type.

Message Interface:


Create the message interface for Sender based on External Definition

(PIP7B1_MS_V01_00_WorkInProcessNotification), as category Outbound and Mode as Asynchronous.

Note: This value we have to take from the Business Action Code As defined in PIP Specification.

Interface Name : WorkInProcessNotificationAction


Create the message interface for Receiver based on Message Type (MT_Report_WIP_Status_Ext)as

category Inbound and Mode as Asynchronous.

Message Mapping:

Perform the message mapping according to the specific requirement.

Go to change list and activate all the IR objects. Integration Repository part is completed.

Integration Directory :


Add or create the Business service and configure the communication channel to that business service.

Note: You can use the following Naming standards for RNIF Side:

Service Name: – “PIP”<PIP Code>”_”<PIP Version>”_”<Partner Role>

Sender Communication channel:

Adapter Type: RNIF11

Transport Protocol: HTTP1.1

Message Protocol: RNIF 2.0

Adapter Engine: Integration Server.

Note: In the Adapter engine either we can choose the Integration Server or Non central adapter engine.

Process Specification Tab


Configuration type: Single-Action Asynchronous Request.

Note: In the configuration type based on our requirement either we can choose Single-Action Asynchronous Request or

Two-Action Asynchronous Request. Two-Action Asynchronous Response.

Message Exchange Settings

Number of Retries: This value represents the number of retries from the partner.

Transport Parameters


URL: Enter the partner address to which the adapter sends the RosettaNet Signal Message.

Ex: https://partnername.com /receiver

Persist Duration: Based on this Duration time during which the message will be persisted on the messaging

system store.

Ex: 730 Days

Receiver Communication channel:

Provide the JDBC Drive name, Connection, User Name and Password.


Sender Agreement, Receiver Agreement, Receiver Determination and Interface Determination.

Sender Agreement : Create this corresponding to Sender Business service and Outbound interface

combination and specify communication channel.

Receiver Agreement: Create this corresponding to Receiver Business service and inbound interface

combination and specify communication channel.

Interface Determination: Specify corresponding Inbound Interface and Interface Mapping for combination

of Sender Service and Outbound Interface w.r.t specified Receiver in Receiver Determination.

Go to change list and activate all the ID objects. Integration Directory part is completed

Related Content

http://rosettanet.org

http://help.sap.com/saphelp_nw70/helpdata/EN/2c/7198403de08368e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/65/fc934258a5c76ae10000000a155106/content.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/8d/759342b2f2c46ae10000000a155106/content.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/2c/7198403de08368e10000000a1550b0/content.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/e7/1c934258a5c76ae10000000a155106/frameset.htm

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