SAP Manufacturing Scenario Using RNIF to JDBC

former_member182455 · ‎07-29-2012

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.

Interface Mapping :

Create the interface mapping and select the Source (WorkInProcessNotificationAction) and Target

(MI_JDBC_Report_WIPFlow_Ext) Interfaces. After giving the source and target interfaces click on read

interfaces button and select the corresponding message mapping.

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.

PIP Details

Code: PIP standard code.

Ex: 7B1

Version: This is available in the front page of the PIP specification and is shorter than the PIP Version.

Ex: V01.00 is the version identifier while V01.00.00 is the PIP version.

Business Transaction Activity: Value must be taken from the Activity Namecolumn of the PIP specification’s Business Activity Descriptions table.

Requesting Action: Value must be taken from the Business Action in FSV column of the PIP specification's Business Action - Business Document Mapping table

Current Role: Enter the value from the Role Name column of the Partner Role Descriptions table in the PIP Specification document. The value corresponds to the role assumed by XI in the PIP.

Partner Role: Enter the value from the Role Name column of the Partner Role Descriptions table in the PIP Specification document. The value corresponds to the role assumed by Partner in the PIP.

Current Business Service code: Enter the value from the Network Component in FSV column of the Network Component Specification table in the PIP Specification document. The value corresponds to the role assumed by XI in the PIP.

Partner Business Service code: Enter the value from the Network Component in FSV column of the Network Component Specification table in the PIP Specification document. The value should correspond to the role assumed by Partner in the PIP.

Security Settings :

Sign Action Message: This selection determines the action message is required to be signed before sending.

Sign Signal Message: This selection determines the signal message is required to be signed before receiving.

Non-Repudiation of Origin and Content: We may check or uncheck depending on the standard.

Non-Repudiation of Receipt Acknowledgement: We may check or uncheck depending on the standard.

In the Source Tab

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.

Receiver Determination: Configure Receivers for corresponding Sender Service and Outbound Interface

combination.

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

SAP Manufacturing Scenario Using RNIF to JDBC

SAP PI for Beginners

ABAP 7.40 Quick Reference

Fiori: technical installation and configuration of one app from A - Z