This section describes how to schedule jobs for the periodic creation of intermediate documents (IDocs) for master data. You schedule the jobs for each defined variant, hence, for each message type. For example, if you want to distribute customer master data, plan a job for the message type, for example, MATMAS that periodically checks changes and generates IDocs.
Procedure
Business Partner
- From the IMG menu, choose SAP NetWeaver → Application Server → IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes →Master Data Distribution → Replication of Modified Data → Create IDocs from Change Pointers → Define Variants.
Alternatively, call the RBDMIDOC transaction.
- In the ABAP Editor: Initial Screen window, enter the following:
Field Name
Field Value
Description
Program
RBDMIDOC
This is the program to distribute changes for customer master data.
- To define a job, choose System →Services → Jobs → Define Jobs.
- In the Define Background Job window, enter the following:
Field Name
Field Value
Description
Job name
<Job name>
Example: MDD_CUSTOMER
Job class
<Job class>
Select the priority according to your requirements.
This is a classification of background jobs according to priority and job type.
Exec. Target
<host name>_<SAP System name>_<SAP System number>
Name of an SAP instance where the system executes the background job.
Host name is the name of the server computer on which the instance runs. The system profile parameter SAPLOCALHOST contains this information.
The name of each instance is specified in the system profile parameter rdisp/myname.
- Choose Start Condition, and in the Start Time window, select the following:
- The required starting time, for example, Immediate.
- The Periodic job checkbox
- The required Period values option, for example, Hourly.
- Save your entries.
- Choose Step, and in the Create Step 0 window, enter the following:
Field Name
Field Value
Description
Variant
<Variant name>
For example: MDD_CUSTOMER
This is the name of the previously created variant for sending IDocs for the DEBMAS message type.
- Save your entries and save the job
Product
- From the IMG menu, choose SAP NetWeaver → Application Server → IDoc Interface / Application Link Enabling (ALE) → Modeling and Implementing Business Processes →Master Data Distribution → Replication of Modified Data → Create IDocs from Change Pointers → Define Variants.
Alternatively, call the RBDMIDOC transaction.
- In the ABAP Editor: Initial Screen window, enter the following:
Field Name
Field Value
Description
Program
RBDMIDOC
This is the program for distributing changes for customer master data.
- To define a job, choose System →Services → Jobs → Define Jobs.
- In the Define Background Job window, enter the following:
Field Name
Field Value
Description
Job name
<Job name>
Example: MDD_PRODUCT
Job class
<Job class>
Select the priority according to your requirements.
This is a classification of background jobs according to priority and job type.
Exec. Target
<host name>_<SAP System name>_<SAP System number>
Name of an SAP instance where the system executes the background job.
Host name is the name of the server computer on which the instance runs. The system profile parameter SAPLOCALHOST contains this information.
The name of each instance is specified in the system profile parameter rdisp/myname.
- Choose Start Condition, and in the Start Time window, select the following:
- The required starting time, for example, Immediate.
- The Periodic job checkbox
- The required Period values option, for example, Hourly.
- Save your entries.
- Choose Step, and in the Create Step 0 window, enter the following:
Field Name
Field Value
Description
Variant
<Variant name>
For example: MDD_PRODUCT
This is the name of the previously created variant for sending IDocs for the MATMAS message type.
- Save your entries and save the job.