Master data can be distributed in two ways.

In both case the IDOC receives data for only one

master data object.
1. Master data object sent directly
This process sends the entire data of the master objects.
This is done by triggering a report program starting with RD!"### where ### is the first three
characters of the message type. "$ample for message type M%TM%! the program is
RD!"M%T. &or D"M%! the program is RD!"D" and so on.
Inside the report programs a function module is called which is responsible for generating and
dispatching the IDOC for the master data. The naming convention for the function module is
M%!T"RIDOC'CR"%T"'R"(''##### where ##### is the name of the message type.
The function module e$ecutes the change pointers and generates IDOC in the following manner
Creates IDOC for each master data objects where the first field of each segment M!)&*
is +,,-..
/ass the IDOC to the %0" layer by calling the function module M%!T"R
IDOC'DI!TRI1T".
"$ecutes COMMIT 2OR3 and calls D"(1"1"'%00 &unction module
2. Master data is distributed using SMD tool (Shared master data tool)
The !MD tools logs changes to a master data using changed pointers. Changed document
should be written whenever the master data is changed or created or deleted. Only changed data
is written to the IDOC4 send to the %0" layer and dispatched to the other system.
&or e$ample when a modification is recorded in customer information 56D,7 transaction84 an
entry is saved in DC/! or DC/7 table4 it depends on the customi9ing. %t the entry creation4
the /ROC"!! field is empty. %s soon as the change pointer has been processed4 the field is
filled with the value X.
!teps for distributing Master data using !MD tool.
Define change relevant field for the message type
Transaction D!2

&or master data to be distributed to other systems change document fields are defined in
transaction D-7 so that change pointers are written. This creates entry in table TD:7.

"ctivate change pointers for message type.
Transaction D!#
The message type for which master data is to be downloaded has to be activated if change
pointers are to be written. This create a entry in table TD%7

"ctivate change pointers $ generally.
Transaction D%1.
This activates master data distribution using change pointers

Define function module to evaluate change pointers
Transaction D%#
This create entry in table TDM&

% function module needs to be defined for each message type. This function module generates
and dispatches the IDOC for the master data. The naming convention for the function module is
M%!T"RIDOC'CR"%T"'!MD'##### where ##### is the name of the message type.
The function module e$ecutes the change pointers and generates IDOC in the following manner
Read all the changed pointers from change pointer table DC/ that has not been processed for
the message type using function module C;%*)"'/OI*T"R!'R"%D.
&or each record retrieved from table DC/ populate IDOC segments. &or each
segment the first field M!)&* is filled in the following manner
,,< = &or any new master data
,,> = &or any change in master data
,,? = &or any deletion in the master data
,@A = If there was no change to the particular segment but the segment have to be
included because hierarchy subordinate segments have to be dispatched
/ass the IDOC to the %0" layer by calling the function module M%!T"R
IDOC'DI!TRI1T"
&or the master data that are processed set the change pointer status to +/rocessed. in
table DC/ by calling function module C;%*)"'/OI*T"R'!T%T1!'2RIT".
"dding message type to partner profile
Transaction D%'
%dd message type for the master data to the distribution model and from menu path
+"nvironment. generate partner profile.
(reate )D*( from change pointers
Transaction D7@ B /rogram RDMIDOC.
!%/ includes a scheduled program4 RDMIDOC that runs periodically to checC the change pointers
for a particular message type. RDMIDOC references the correct IDOC program for any given type via
TDM"4 which is maintained through transaction D:,.

In the production system4 it is obvious that the users will not launch the D7@ transaction by
themselves. % periodic job will be scheduled to e$ecute the RDMIDOC program4 which is
actually run by D7@ transaction4 with a variant containing the right message type.
+opulation custom field for e,tended )D*(.
&or any modification or population of custom fields in e$tended IDOC through this program
RDMIDOC or RD!"### a user e$it is available in function module
M%!T"RIDOC'CR"%T"'##### where ##### is the message type.
&unction module M%!T"RIDOC'CR"%T"'##### is called from the function module
M%!T"RIDOC'CR"%T"'R"('##### for program RD!"### or
M%!T"RIDOC'CR"%T"'!MD'##### for program RDMIDOC as defined in transaction
D:,.
&or e.g for message type M%TM%! for material download
&unction ModuleD M%!T"RIDOC'CR"%T"'M%TM%!
1!"R "#ITD "#IT'!%/0M6,@',,7
"*;%*C"M"*TD M)6,,,,@
"$tended IDOC &ieldD IDOC'CIMTE/"
Set (hange Document -lag on for custom fields
Transaction S&11
If change pointers are to be written for custom fields then the change document flag
at the domain level should be activated for that field. Then maintain an
entry for this field in transaction D-7. Changes to custom fields will be only picCed if the change
document for such fields is maintained in table DC/.
Reference 0inCsD
1. http.//help.sap.com/saphelp0'!b/helpdata/en/12/2112da!1ce11d123!1####e
223fbbd/content.htm
2. http.//help.sap.com/saphelp0n4#'/helpdata/en/12/25e#5c131!2e11e1#####
##a11'#2'/content.htm
3. https.//444.sdn.sap.com/irj/sdn/thread6thread)D71551#1