distributing material master data using standalone programs and change pointers

8/6/2019 Distributing Material Master Data Using Standalone Programs and Change Pointers

http://slidepdf.com/reader/full/distributing-material-master-data-using-standalone-programs-and-change-pointers 1/16

1

Distributing Material Master data using Standaloneprograms and Change Pointers

MASTER Data is the data that exists in the organization like employee details, material master,

customer master, vendor master etc.

Master data can be transferred by two methods:

1. Triggering through stand-alone programs

2. Triggering through change pointers

Data Transfer using Standalone programs:

A material is created in R3SCLNT800 and should be transferred to R3SCLNT810.

Step1: Define Logical Systems T.code SALE

Path: ALE--> Basic settings Logical Systems Define Logical systems



2

Step 2: Assign Client to the logical system T.code: SALE

Path: ALE--> Basic Settings Logical Systems Assign client to Logical System



3

Step 3: Create RFC Destination Tcode: SM59

Note: Provide Connection type as µ3¶ indicating connection to R/3 system

Enter the following details.



4

Step 4: Define port Tcode: we21

Port is the medium in which data is transferred.



5

Step 5: Maintain Partner Profiles Tcode: WE20

In partner profile we specify the names of the partners which are allowed to exchange IDocs .



6

Double Click on the Message type MATMAS the following opens.

Enter the details for Receiving port, Pack size and Basic type.



7

Step 6: Create Customer Distribution model Tcode: BD64

Click on the Create button and enter the short text, Technical name etc as shown below



8

Now select the created model view and click on Add message type button .A pop up box appears,enter Sending system, receiving system and message type.

Save the Distribution model

Generate Partner Profiles

Click the menu item µGenerate Partner Profiles¶.

It leads to the next transaction where in the selection screen you have to provide Model view name,

Partner System logical system and execute.

Then, you will be intimated about the partners, port creation, and outbound parameters creation.



9

Distribute Customer Distribution Model

In the menu item µ Distribute¶ to the destination client.

Popup window appears , press Enter.

Generate Partner Profiles in partner system (in bound system)

Transaction: BD82

Provide Model view and logical system of Partner system to this system (our Outbound system)

Execute, again you will be intimated about the creation of inbound parameters.

NOTE:

You cannot maintain a message type between the same sender and receiver in more than one

customer distribution model.

Only the owner is authorized to modify the model.

Step 7: Creation of material T.code MM01.

Enter the details as shown below and create a material.



10

Step 8: Send the created material. T.code BD10

Enter the material created or changed, message type and the destination system as follow and

execute.



11

We get the information as 1 master Idoc created, 1Communication Idoc created.

Step 9: View the IDoc T.code we05



12

Technical Settings In the Receiving system R3SCLNT810.

Partner Profile T.code WE20

For the partner add the message type .here the message type is MATMAS



13

Double click on the message type and enter the processing code (MATM) and select Trigger Immediately radio button, save.

Get the material T.code BD11.

Enter the material created or changed, and the Message as shown below.



14

If every thing is fine IDOC will be created .

View the Idoc in the T.code We09.

Data Transfer by Change Pointers:

Steps from 1 to 6 are same as stand alone programs.

Step1: Define logical system

Step2: Assign logical system to the client

Step3: Create RFC Destination

Step4: Define Port

Step5: Generate partner profiles

Step6: Create Customer Distribution model



15

The following are the additional steps for Change pointers

Note (The following steps are to be maintained in both the sending and receiving systems)

Step 1: Activate change pointers generally T.Code BD61

Check the box so that change pointers get activated and keep track the changes to

trigger ALE process.

Step 2: Activate change pointers for the message type T.code BD50

Step3: Change Document should be checked at data element level



16

Step4: Run the program RBDMIDOC or the T.code BD21

Enter message type and execute.

Create or change a material and check for the Idoc creation in the T.code WE09.

distributing material master data using standalone programs and change pointers

Documents