Skip to Content
Author's profile photo Ramesh Gulipalli

SAP 4.7 to MDM Integration using PI7.1-Part1

During my current project I got the opportunity to work with MDM integration scenario.My current scenario is SAP 4.7 to MDM data integration using PI 7.1.
Business Scenario The scenario consists of 2 systems, SAP 4.7 and MDM (Master Data Management) that are required to exchange messages through PI. The container that contains the message is an IDoc (Intermediate Document). The IDoc consisting of the customer master information records is extracted from the 4.7 system, converted into the XML format and posted into the desired folder in the MDM system.
Pre requisite: Make sure that before starting with the PI specific configurations, the Integration (ALE) Settings between the SAP 4.7 and SAP PI system to establish connection between the 2 systems and the configuration of Software Landscape Directory (SLD) in PI are already done. Make sure that MDM adapter is already deployed on PI server. 

Business Activity diagram

image Conversion of IDOC to XML
After the initial settings (ALE and SLD configurations) for the connection between the SAP 4.7 and the PI server have been done, next we need to design and configure the scenario in the PI system. For ALE configuration follow this IDoc to JDBC guide, in which sender side ALE configuration is very clear.
Apart from this ALE configuration, we will require two business systems, one system (Web as ABAP) for your R3 system and another (Third party) for MDM server.

Enterprise Service Repository Steps:

1.     Import of SWCV from SLD into IR :       

Open the Enterprise Service Repository page and in the left window pan right click->New->Software component version (workAreas). In the right pan select radio button import from SLD and press display button a new window will open. Select your own SWC for R34.7 and MDM. Import these two. You can now start creating the design objects in the SWCV imported.

image

 2.     Creation of Namespace:       

Click on your SWCV->right click->New->Namespace.         Create two namespace. One for R3 system objects development and one for MDM object development.   image

3.     Import of IDoc from R3 System  

Now you need to import IDoc from your R3 system. For this thing you must have developers right or you can ask to your BASIS guy to give your user this authorization,      Under the R3 SWCV, click on Imported Objects->Import of SAP Objects. Give the Application Server IP address , System Number of the R3 system you are importing the IDoc from and your User ID and Password in the same system and Continue.

image      

A drop down list will be displayed select the radio button for DEBMDM06,                 and click on Finish.

   image

image

You will have the IDoc imported under Imported Objects->IDocs. Activate this IDoc. 

4.     Creation of Data Types        

Here, the source structure will be the IDoc DEBMDM06.Hence no need to create any structure for it.         Since  the source IDOC and target structure are same so rather than creating a new data types for target ,we will use  the XSD of this IDoc.        Export the XSD of this IDOC, then under your MDM SWC, import this XSD as an external definition.

 5.     Creation of Message Types

No need to create message for an IDoc because it itself acts as one. Also, for the target structure, Since we are using the same IDoc as an External Definition, the message type doesn’t need to be created.  

6.     Creation of Service Interfaces           

No need to create Service Interface for an IDoc          Create service Interface for the target only.       Go to your MDM SWC , right click on it and select new, new window will open , under Interface objects select service interface and name it as DEBMDM06Import_Inb 

image

Assign your external definition DEBMDM06_xsd as message type to this interface. 

7.     Creation of Action

Create a sender action for the IDoc, in the left pan right click->New->under process Integration Scenario Objects click on Action.Give it a name DEBMDM06Send 

image

And assign it an outbound service interface.

image

In the same way create receiver action under your MDM SWC and name it as DEBMDM06Receive

image

8.     Creation of Message Mapping        

Amapping is done between the source (IDoc) and the target(Message Type or External Definition) structures.         In order to create the mapping, right click ->New->under mapping objects select message mapping        and give it a name DEBMDM_DEBMDM06_to_DEBMDM06        Select sender side message your IDoc DEBMDM06 and receiver side message your DEBMDM06.xsd

image        

Since this is a one to one graphical mapping so select root node on both side and click on the icon shown in above screenshot, It will map the identical nodes. Save the mapping.  

9.     Creation of operation  Mapping        

In order to create the operation mapping, right click ->New->under mapping objects select operation mapping        and give it a name DEBMDM_DEBMDM06_to_DEBMDM06        Select sender side operation as your DEBMDM06 IDoc and receiver side is operation corresponding to inbound interface.        Assign the message mapping which you have created in the previous step.        Save the Interface Mapping.        

image

10.  Creation of Process Integration Scenario        

In order to create the operation mapping, right click ->New->under mapping objects select Process integration scenario.        Assign sender and receiver action , create connectivity between the actions         click on sender action then press shift, click on second action release shift and then right click        select option create connection between actions.                

image

Double click on the link and assign mapping to that connection.

image

Save and activate All ESR objects which you have created till now. 

For the Configuration and testing part please follow my weblog

SAP 4.7 to MDM Integration using PI7.1-Part2

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      This is a very nice blog created by you.
      We have a similar scenario where we need to integrate SRM-MDM using XI 7.0,where R/3 will be passing idocs for updating goods catalog, services catalog and the contract catalog.
      MATMAS     MATMAS03 – for materials
      SRVMAS     SRVMAS01 – For Services
      BLAORD  BLAORD03 – for contracts
      Can u please tell if there is an pre-defined mapping template available for the scenario and what should be the input message for MDM ?
      Author's profile photo Ramesh Gulipalli
      Ramesh Gulipalli
      Blog Post Author
      Hi Sudhansukumar,

      Thanks!!

      No, i am not using the pre-defined mapping,just i created the one to one map.Input is DEBMDM06 idoc from R/3 4.7

      Author's profile photo Vikas Kumar Singh
      Vikas Kumar Singh

      Veyry Nice Blog. Clearly explains the step by step procedures