Show TOC

 Generating Integration Models


In most cases, only some of the master data and transaction data available in the ERP system is needed for planning in the SCM system. When you generate an integration model, you specify which data objects are to be selected from the total dataset in the ERP system for the transfer.

To create the integration model, you first select the object types (for example, material masters) to be selected on the Create Integration Model selection screen. Next, you select specific selection criteria (in most cases, a material/plant combination) that further restrict the object types you have already selected. If you have already selected Material Masters , for example, you could now enter an MRP controller. In this way, you define filter objects. Filter objects are used to select which data objects are transferred to a specified SCM system. In the example, all material masters for a particular MRP controller are selected.

For more information, see Select Filter Objects below.

Working with Variants

Since the system does not save the selection options you make when creating an integration model, you have to save the settings as a variant on the selection screen. By working with variants you are able to reuse the settings you have saved whenever you want. If you want to recreate an integration model at a later point in time, you can call up the required variant by choosing the Select Variant symbol in the toolbar at the top of the selection screen.

Integration Model Versions

If you regenerate an integration model, the system automatically generates a new version of this model. Different versions of an integration model are distinguished by their date and time of creation, as well as by the filter objects that they contain. You can create as many versions of an integration model as you want. However, only one version may be active at any time.

Changing an Integration Model

We recommend that you change an existing variant of the integration model, generate a new version using transaction CFM1, and then save the variant. You can also create a runtime version of the active integration models. For more information, see Runtime Version of the Active Integration Model .

Structure of an Integration Model (Valid Only for SAP APO)

The structure of an integration model influences performance. When it integrates transaction data, the system checks whether the data concerned is contained in the active integration model. At the same time, the system loads and interprets all active integration models for the object type concerned to determine any target systems that may be affected. The greater the number of integration models per object type, the longer the runtime required for determining the target systems.

Note Note

For performance reasons, we recommend that you do not enter both master data and transaction data in one integration model.

End of the note.

You have to activate the integration model to trigger the initial transfer of ERP data to the SCM system. See also Activation and Deactivation of Integration Models (report RIMODACT).

You can subsequently deactivate and delete integration models that are no longer needed.

See also Deleting Integration Models (report RIMODDEL).


The Customizing and default settings for integration must be maintained. The relationship between the source and target system must also be maintained in both systems.

For more information, see CIF Customizing in the ERP System and CIF Customizing in the SCM System .


For SAP R/3 3.1I - 4.5B, open the CIF area menu (transaction CIF). Choose Start of the navigation path Integration Model Next navigation step Generate Next navigation step Create End of the navigation path .

As of SAP R/3 4.6B, choose Start of the navigation path Logistics Next navigation step Central Functions Next navigation step Supply Chain Planning Interface Next navigation step Core Interface Advanced Planner and Optimizer Next navigation step Integration Model Next navigation step Generate Next navigation step Create. End of the navigation path .

The Create Integration Model screen appears.

You can also call this report (RIMODGEN) using transaction CFM1.

Define Integration Model

The three required entry fields in the upper section of the selection screen are used to define the scope of the integration model you want to create.

  1. Model name: Enter an alphanumeric description or choose an existing model name using the input help (for example, PUMP).

  2. Logical system: Enter the target system (logical system). This name is identical to the RFC destination.

  3. APO application: Enter another name of your own choosing so that you can differentiate between integration models with the same model name (for example, MATMASTERS).

Select Filter Objects
For Material-Dependent Objects
  1. In the Material Dependent Objects screen section, you select the fields for object types that you want to include in your integration model (for example, material masters). Note the recommendations for the combination and sequence of object types given under Example .

  2. In the General Selection Options for Materials screen section, you further restrict the selected object types by entering the selection criteria (value ranges) for materials (for example, all materials with the MRP type 1 to 5). These selection criteria are valid for all object types selected under Material Dependent Objects . If you click the arrow button to the right of a field, the dialog box appears where you can make multiple selections. Here, you can specify more complex selection criteria by further restricting the value ranges or by excluding certain value ranges from the transfer.

    Caution Caution

    If you make no further restrictions to the selection made in point 1, the system automatically selects all objects for this object type (for example, all material masters). This can lead to significant performance problems.

    End of the caution.
  3. Under General Selection Options for Materials, you can make further restrictions to those you have already made by specifying additional selection criteria. This is done by clicking the arrow button to the right of the field for the relevant object. You can also make multiple selections here. These selections are only valid for the current object type.

    Note Note

    Even if you only restrict the selection by material and plant, we recommended that you use the selection options in the General Selection Options for Materials screen section. In this case, the selection shows significantly improved performance compared to entering the values in the selection options for the individual object types.

    End of the note.
For Material-Independent Objects
  1. In the Material Independent Objects screen section, you select the fields for object types that you want to include in your integration model (for example, customers). Note the recommendations for the combination and sequence of object types given under Example .

  2. You can additionally restrict the object types selected for material-independent objects by clicking the arrow button to the right of the relevant field and specifying further selection criteria (value ranges). These selections are only valid for the current object type. You can also make multiple selections here.

Results and Saving

To display the results list, choose Execute . You see a list displaying the results of the selection; that is, the type and (total) quantity of the selected filter objects.

You can navigate to the detailed view for each filter object.

  1. Select the filter object you want to view.

  2. Choose the Details pushbutton. You see a list of all data entries that have been found for the selected filter object.

  3. You leave the screen by choosing Back .

Generate the integration model. A dialog box confirms that the integration model was generated successfully.


Suggestion for the Structure of the Transaction Data Integration Model

The following objects should each be grouped together in a separate integration model and activated in the sequence given:

  1. Stocks (if you hold special stocks at the customer or vendor, the relevant customer or vendor must be contained in the same integration model)

  2. Sales orders (includes sales orders, deliveries, scheduling agreements, quotations, and customer independent requirements)

  3. Purchase orders and purchase requisitions

  4. Production/process orders and planned orders (these may need to be separated). These have to be activated before production campaigns.

  5. Manual reservations and planned independent requirements

  6. Production campaigns and process/planned orders

  7. Shipments