step by step process for sending customer or vendor master data from ecc system to an external...

8/17/2019 Step by Step Process for Sending Customer or Vendor Master Data From ECC System to an External System Mysq…

1/10

Getting Started Newsletters Store

SearchtheCommunityWelcome, G uest Login Register

Process Integration / Process Orchestration - Process Integration - Exchange Infrastructure

Created by Honey Gyanani, last modified on Apr 19, 2008

Step by Step process for sending Customer or Vendor Master Data from ECCsystem to an external system mysql database through SAP Process Integration

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).

p by Step process for sending Customer or Vendor Master Data fro... https://wiki.scn.sap.com/wiki/display/XI/Step+by+Step+process+for+...

10 02/04/2016 12:11


2/10

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


10 02/04/2016 12:11


3/10

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 with

DEBMAS03Statement 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 with

KUNNRSALUTATION 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.DEBMAS03 will 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 only

Receiver 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.


10 02/04/2016 12:11


4/10

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


10 02/04/2016 12:11


5/10


10 02/04/2016 12:11


6/10


10 02/04/2016 12:11


7/10


10 02/04/2016 12:11


8/10


10 02/04/2016 12:11


9/10


10 02/04/2016 12:11


10/10

----------------------------------------------------------------------------------------------------------------------------------------------------------------

For Vendor Master Data: This is same as Customer data with few changes like:

Distribution model for vendor

Tcode: BD64Create a distribution model for Customer data by using IDOC CREMAS (Vendor master data distribution).

Rest configuration will be same as Customer Master.

No labels

Follow SCNContact Us SAP Help Portal

Privacy Terms of Use Legal Disclosure Copyright


step by step process for sending customer or vendor master data from ecc system to an external...

Documents