Show TOC

 Runtime Version of the Active Integration Model

Definition

Database table (CIF_IMAX) that is fully buffered and formatted in an optimized way. It contains exactly one integration model for each object type and each logical system. The runtime version is formed from all active integration models for a particular object type and target system. It is formatted in an optimized way, compressed, and saved to the database. In addition, the information in the runtime version is buffered to all ERP application servers. The runtime version of the active integration models is also called the maximum integration model.

The user creates the runtime version once by using the RCIFIMAX report and then it is automatically updated by the system every time an integration model is activated. To do this, the system reads from the CIF_IMOD database table all active integration models created by the user for the relevant object type and logical system, and then uses this to generate the runtime version.

Compared to the CIF_IMOD database table, the runtime version offers the following advantages:

  • Improved performance because only object data for a specific object type needs to be loaded for an integration model

  • As a result, database accesses that reduce performance are not needed for online transfer and the target system can be determined faster. Also, the performance for online transfer is not linked to the number of active integration models when the runtime version is used.

  • Improved usability because integration model construction now only has a small influence on performance. The speed at which the runtime version is generated depends on the number of integration models.

Use

The runtime version of the active integration model requires SAP R/3 Plug-In 2002.1 or higher. When you install SAP R/3 Plug-In 2002.1 or higher, we recommend that you generate runtime versions for all available integration models. You do this by calling report RCIFIMAX, specifying the relevant object type and target system, and setting the Generation indicator. Note that the runtime version has to be generated in all ERP systems and clients. If the runtime version is not generated, the system continues to access the CIF_IMOD table to determine target systems.

You can also use the same report and the Consistency Check indicator to check whether runtime versions and integration models are consistent. We recommend that you schedule this report as a regular background job. No integration models may be activated during the consistency check. For more information, see CIF Customizing in the ERP System under Start of the navigation path Basic Settings for the Data Transfer Next navigation step Initial Data Transfer Next navigation step Schedule Regular Jobs End of the navigation path .

You can rectify inconsistencies by generating the runtime version again. However, if unexpected inconsistencies continue to occur, open a problem message in SAPNet – R/3 Frontend and describe the steps that led to the inconsistency.