Customer master integration with CLM

[Former Member]

Hi,

We are in need of bringing the customer master info from ECC. Does SAP provide standard functionality of interfacing between CLM and ECC Customer master info? We know that ECC Vendor master integration with CLM is standard in version 7.0 and 9.0 but is Customer master integration provided as standard? Or would we need to build a custom interface to integrate ECC Customer master and CLM?

Thank you,

Vikram

[jaheer_hussain]

Hello Vikram,

It is possible.Can you please follow the below steps for integration between ECC and CLM?  or you can template import customer with object type 'SUPPLIER'.

Step by Step process for sending Customer or Vendor Master Data from ECC system to an external syste...

·        

·         Step by Step process for sending Customer/Vendor Master Data from R/3 system to an external system mysql database through SAP Process Integration:  

Step by Step Process for Customer Master Data:

Step 1: Configuration in Source System R/3

TCode: SALE
   Create a Logical System for Source system R/3 (SAICLANT800) as well as Target System PI (XAICLNT001). 

Tcode: SM59

Create RFC Destination *(XAI001)*for Target PI System 

Tcode: BD64   
   Create a distribution model for Customer data by using IDOC DEBMAS (Customer master data distribution).

Tcode: WE21
    Create a Port *(SAPXAI)*for Target system PI and chose the RFC destination.

Tcode: WE20
  Create Partner Profile for Target System PI and assign the IDOC DEBMAS in outbound parameters. 

In Outbound Parameters Specify Message Type (DEBMAS),Receiver port (SAPXAI) and Basic Type (DEBMAS03).

Step 2: Configuration in Target System PI System  

Tcode: IDX1 In Target System PI, Create a Port (SAPSAI)and assign RFC Destination*(SAICLNT800).*

Tcode: IDX2
   Create Metadata of IDOC (DEBMAS03) in defined port(SAPSAI). 
    
  

Step 3: Configuration in System Landscape Directory in Process Integration

Create a Software Component Version (CUSTMOR_MASTER of Incture).

Create a new Product (Custmor_master of Incture) and assign the Software component version (CUSTMOR_MASTER of Incture) in this Product.

Create a Technical System (SAI on ramana) then assign the product (Custmor_master of Incture), assign the Software component version*(CUSTMOR_MASTER of Incture).*


Also assign the Business System (SAICLNT800) in Technical System.

Step 4: Configuration in Integration Repository in Process Integration

Create a Message type *(MT_CLM_JDBC_Output)*and Define field as required in DATABASE Table. This Pattern of Data type should be strictly followed for JDBC adaptor.

Create a Message Interface (MI_IB_CLM_JDBC) of Inbound Asynchronous type and assign the output Message type (MT_CLM_JDBC_Output). 

Define Message Mapping *(MM_R3_DEBMAS_CLM_JDBC)*and define the Mapping as follows:

MT_CLM_JDBC_Output will be mapped withDEBMAS03Statement will be mapped with IDOC

BUPA_MASTER will be mapped with IDOCaction will be mapped with Constant 'INSERT'access will be mapped with field EIKNA1MBUPA_ROLE will be mapped with constant'CUSTMOR' PARTNER_ID will be mapped withKUNNRSALUTATION will be mapped with TITLE

NAME1 will be mapped with NAME1

NAME2 will be mapped with NAME2

CITY will be mapped with ORT01

COUNTRY will be mapped with COUNC

PHONE_NO will be mapped with TFLF1 
 

Define Interface Mapping (IM_R3_DEBMAS_CLM_JDBC)and assign above Message Mapping.

Step 5: Configuration in Integration Directory in Process Integration

Define Business System and assign (SAICLANT800) as a Business System.

IDOC DEBMAS.DEBMAS03will be in outbound interface automatically.


Create a Business Service (BS_CLM_JDBC_RECEIVER) and assign the inbound interface (MI_IB_CLM_JDBC).

Define Communication Channel(CC_CLM_JDBC_RECEIVER) and chose adapter type JDBC and give the appropriate parameters.
Give proper values in Database Connection and rest values are coming with default values so no need to give additional parameters.
There is no need to give Sender Agreement so define onlyReceiver Agreement with suitable parameter.

Define Interface Determination with suitable parameters.

  Define Receiver Determination with suitable parameters.

Step 6: Sending Customer Master Data from Sender System R/3

Tcode: BD12
Provide Customer no.  --- To  --
Output Type is *DEBMAS 03*Then execute.

Tcode: WE02
Provide IDOC basic type DEBMAS03and execute it then it will show the
Status success 03.

Step 7: Monitoring in Process Integration Server

Tcode: SXMB_MONI.
Check the XML messages.

Step 8: Monitoring in Communication Channel Monitoring in Runtime Workbench
  

Step 9: Check the final Customer Master data in Database Table BUPA_MASTER

[Former Member]

Hi,

Thanks for the responses. So is it correct to say that the interface is custom in nature?

Thanks,

Vikram

[Former Member]

Yes it is custom.

[Former Member]

It is definitely possible to do one option would be to use the 'custom master data' under setup-master data tab. However this will remain independent and will need further custom work to integrate it to Biz Docs. etc....

May I ask why you would need the customer master.  Are you planning to use this in a non-procurement process ?.