Step by step guide for MDM to CRM using PI7.31

[rasjoshi]

SAP MDM 7.1 to SAP CRM VIA SAP PI7.31

By Rashmi Joshi, SAP PI Consultant, HCL Technologies.

1. Introduction:

This document describes scenario where, a file containing the beverages details is picked from a MDM Syndicator (Sender/Source) and sent to SAP System (Receiver/Target) via Process Integration.

This guide gives step-by-step procedure to pick a file from Sender— MDM System to Receiver—SAP system. A business system representing Sender-MDM System hosts a file, picked by PI at regular intervals using Sender MDM-PI adapter. Then PI sends the IDoc to the receiving business system (Receiver SAP System) by using the Receiver IDoc Adapter.

SAP MDM - Master data management (MDM) is a technology that includes the definition of processes and responsibilities for master data maintenance.

SAP MDM Syndicator - The MDM Syndicator is used to provide harmonized data to other applications as XML or in a variety of other formats. It is the export interface for master data stored in an repository.A syndication can be executed either manually or automatically with the MDM Syndication Server. The syndicated file will be present in port location. MDM adapter will pick file from this location.

For importing data into SAP MDM system we have MDM Import Manager that we will discuss in another document.

             

2.   Maintain the System Landscape Directory

1. Maintain Technical Landscape: As the receiving system is SAP System it should be configured as WAS as ABAP technical systems.  In the Technical system Browser, create a New Technical system.

Sender Technical System -

              

Receiver Technical System –

               

1. Maintain Business Landscape: Create a Business system to associate to the technical system which was created in the previous step. During creation of this business system, select role of the system as Application system.

Note – You can you Tcoe RZ70 to create systems in SLD automatically.

3. Configuration in the integration server

     i.Create RFC destination: Using transaction SM59 create an RFC Destination of Type 3 in order to establish communication with the Receiver SAP      System. Created RFC Destination should point to the Receiver— SAP system.

                 

     ii. Create Port: Create a port using Tcode: IDX1, which will be employed in later stages to import the IDoc metadata. In this example, the port is SAPXXX      (Port for receiver system) where XXX is the system ID of the SAP backend system. The created port has to be binded with the RFC Destination of the Sender      SAP System configured in the Step 3.i. above.

                  

4. Maintain ESR (Enterprise Service Repository)

    i. Import IDoc from receiver system –

      Create namespace under your software component version. Select import objects. Enter required logon data. List of idocs will appear from that choose your required idoc and import it.

ii. Export imported Idoc as xsd.

                

And again import this xsd file as external definitions. Here external definition is used as source structure and Idoc as target structure. Here no message type is required in this scenario.

Note – If source and target structure are same then only follow this step.

iii. Create Service Interface of source structure –

Create sender service interface with type External Messages category outbound and mode of direction as Asynchronous. 

iv. Create Message Mapping –

Select xsd imported file in external definition at source and Idoc at target side.

Perform the Mapping of each target field with suitable source fields as per your requirements.

v. Create Operation Mapping –

Select Service interface which we created in step no. iii as source operation and idoc as target operation. Also select mapping program which is created at step no. iv.

5. Maintain ID (Integration Directory)

     i. Create Configuration Scenario

Open Integration Directory. Create a new Configuration Scenario or use an existing one.

Add Sender and receiver Business System.

Here MDM_DEV is sender business system while CRSCLNT100 is receiver. Please check Adapter Specific Identifier parameters for both sender and receiver business systems. These values come from SLD. The parameter values should be same as defined in SLD.

ii. Create Communication channels for sender and receiver.

Select adapter type as MDM. MDM Access parameters are defined in MDM console.

Note – We will not cover MDM portion in detail here.  As discussed MDM Syndicator on page.i. MDM will syndicate data to specific location from where PI will pull the data. For this purpose we need to create port and remote system. Port defines the inbound/outbound folder for syndication.

                 

Select adapter type - IDoc as Receiver Communication Channel –

iii. Create Receiver Determination –

               

iv. Create Interface Determination –

Here provide details of Operation mapping, service interface and namespace details from ESR.

v. Create Sender Agreement

Select sender communication channel here. Provide sender communication channel.

vi. Create Receiver Agreement

Select receiver communication channel here. Provide Receiver communication channel here.

6. Test configurations done in ID

     After doing all configurations we need to test it. Go to interface determination à Test Configuration

                

                    

Steps to test scenario end to end -->

Step 1 --> Trigger record from SAP MDM --> .xml file will get syndicated at port location

Step 2 --> Go to SXMB_MONI of PI and check message is processed successfully

Step 3 --> Go to WE02 of CRM system and check IDoc is received