4/5/2016 9:28:45 PM
Generate and reconcile the runtime version of active models-The RCIFIMAX report can be used to generate the runtime version of the active integration model (CIF_IMAX table) and to check the data consistency between the runtime version and the table of the active integration model (CIF_IMOD).
The runtime version is a representation of the table of the active integration model in an form that is optimized for the online transfer to SAP APO. In the runtime version, all active integration models are stored in an optimized form for each object type (for example, stocks) and target system. In addition, this table is buffered to all ERP application servers. As a result, the database access to the table of the active integration model during transfer is no longer necessary. The data in the runtime version is optimized for the evaluation of relevant target systems for each object type in online transfer (for example, stock posting). This means that the relevant target systems can be determined significantly faster. The runtime version is adjusted after each activation or deactivation of integration models. This ensures the data remains consistent between the integration model and the runtime version.
After upgrading to SAP R/3 Plug-In 2002.1 or higher, we recommend you start this report with the Generation indicator. The runtime version is created using the current entries in the table of the integration model and this increases performance when determining the relevant target systems for online transfer. Note that the runtime version must be generated in all ERP systems and clients. If the runtime version is not generated, the system accesses the integration models to determine target systems as before.
To check data consistency between the runtime version and integration model, start the report with the Consistency Check indicator. We recommend that you schedule this report regularly in the background. During the consistency check, you may not activate any integration models.
You can rectify inconsistencies through regeneration. If inconsistencies continue to occur, open a problem message in OSS and describe the steps that led to the inconsistency.
If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.