Entering content frame

Background documentationCreating New Master Data Relevant to SAP APO Locate the document in its SAP Library structure

You create new master data in SAP R/3 because this is the superordinate master data system. New master data objects with selection criteria that correspond to an integration model that already exists (for example, the same MRP type) are not automatically included in the integration model in SAP R/3 and transferred to SAP APO. There are two procedures available for making the transfer:


       1.      Periodic Transfer Using Background Processing

       2.      Online Transfer Using Business Transfer Events (BTE)

1. Periodic Transfer Using Background Processing

In this procedure, a new version of the corresponding integration model is created and activated for master data that has been created in SAP R/3. Although this may be done manually, for performance reasons it is recommended that you set up a periodic background job to run at times when the system load is at a low (for example, at night). In the background job, the reports referred to below should run in sequence. This procedure offers the following advantages:

·        Master data that has been recently created and that meets the selection criteria of integration models that already exist is included in these integration models and transferred to SAP APO.

·        Master data that has been changed to such an extent that it no longer meets the selection criteria of the corresponding integration model is excluded from the transfer.

·        Master data (material, customer, vendor and source of supply) that has been changed since the last transfer is retransferred to SAP APO and will now be up-to-date.
For more information, see Changes to Master Data.



       1.      Create a new version of the corresponding integration model (report RIMODGEN).

       2.      Activate the new version (report RIMODAC2, set the radio button Activate Newest Version).

       3.      The system automatically sets the old version as inactive.

       4.      The system does not transfer all of the data in the new version to SAP APO. Only the differences between the old and new version (delta information) are transferred.

       5.      Optional: Delete the old version of the integration model (report RIMODDEL).

2. Online Transfer Using Business Transfer Events (BTE)

As of SAP R/3 Plug-In 2000.2, you can create info objects in SAP R/3 that correspond to the selection criteria of an integration model that already exists and then immediately transfer them to SAP APO when they are posted. The system automatically creates a new version of the corresponding integration model and activates this in the background.


This procedure for the creation of new APO-relevant master data should only be used in exceptional cases. This can, in particular, lead to problems if dependent objects exist. In most cases, it is better to use a periodic transfer with background processing as described above. In particular, in cases where you are transferring large amounts of master data to an SAP R/3 system using ALE or batch input, the transfer to SAP APO should be batch controlled rather than batch triggered.


In SAP R/3, business transaction events (BTEs) have been activated for the integration with SAP APO. You can find more information under Activating BTEs for SAP APO Integration.


Make the following settings to change to online transfer:


       1.      Use transaction CFC9 to call the screen Change Target-System-Independent Settings in CIF. Under Change Transfer for Master Data, choose BTE Transfer, Immediately. As of SAP R/3 4.0B, you can make this setting in CIF Customizing in SAP R/3 under Basic Settings for the Data Transfer ® Configure Change Transfer for Master Data.

       2.      Use transaction SM30 to call the screen Maintain Table Views: Initial Screen. Call table CIFIMODGEN. You see the screen Change View "Customizing Automatic Generation of Integration Models". You determine the procedure for adapting the integration model by making entries in this database table. The table contains the following columns:

Connection Point: Contains one of six different possibilities:

·         Creation of new material master data (MAT_INS)

·         Changing of material master data (MAT_UPD)

·         Creation of customer master data (CUS_INS)

·         Changing of customer master data (CUS_UPD)

·         Creation of vendor master data (VEN_INS)

·         Changing of vendor master data (VEN_UPD)

Program: Contains the name of an ABAP/4 program. This program should be executed when one of these events occurs. Usually, you should specify the standard program RIMODGEN for generating integration models.  See below.

Variant: Contains the name of a variant. This variant contains the input parameters of the given program.

Counter: You can specify several program/variant combinations for the same connection point and determine their sequence using the Counter column.

The program RIMODGEN offers the following enhanced functions.

·        An existing integration model can be selected

·        Filter objects can be inserted or deleted

·        The result can be saved as a new version of the integration model

In addition, the program evaluates the integration model key, the checkboxes for the filter objects, and the selection options for material, customer, and vendor. If the number of filter objects does not change, a new version is not created. If a new version is created, it is activated. That is, new objects are transferred, and the data flow is stopped for obsolete objects.

In the selection screen of program RIMODGEN, the fields Model Name, Target System, and Application are obligatory.

For materials, the selection options under Relevant Materials are evaluated and compared with the newly created or changed material. Besides the checkbox for material master, the following checkboxes are evaluated:

·        Availability check

·        Sales orders

·        Purchase orders and purchase requisitions

·        Production orders and process orders

·        Planned orders

·        Manual reservations

·        Planned independent requirements

·        Stocks, all types

·        Consumption data

If the checkbox for production process models (PPMs) is marked, the selection options entered are used to carry out the selection in the database. The results are incorporated into the model. In the case of newly created material, this selection provides no results, since a bill of material, routing or production version does not yet exist. In the case of material changes, the selection can deliver valid PPMs. For PPMs, however, the current date enters the system in the form of the key date. Therefore, it is possible that a ‘new’ PPM is selected and transferred, even if nothing has changed in the bills of material, production version, or routing.

All other selection options (including special restrictions for material/plant for the individual documents) are not taken into account here.

In the case of customers, only selection options for customers and the checkbox ‘customer’ are taken into account. The is also the case for vendors.

The purpose of extension CIFIMO01 (CIF-IMO-zero-one) with module EXIT_RIMODGEN_001 is to influence the number of filter objects. This extension modifies the list of filter objects provided by the standard functions.

The process for automatically generating integration models runs in the background as a queued remote function call (qRFC). This means that you can use the qRFC monitor (transaction SMQ1) to test whether errors occurred. The queue name consists of the prefix CF_IMOD_ and the master data type, that is, T_MAT, T_CUS or T_VEN. Transaction SMQ1 provides the following functions:

·        Restart

·        Debugging

·        Call deletion

If the CIF application log is activated, entries are written there. These entries are documented under the object CIF and the subobject IMOD. Detailed information about the automatic generation process and the activation of the model is located here.

You can find additional information on the qRFC Monitor and CIF application log under Monitoring.


Leaving content frame