Checking Cross-Component Data Integrity (DIMa) 

Purpose

The Data Integrity Manager (DIMa) helps you to detect and repair inconsistencies between objects across components within the SAP CRM System landscape.

A SAP CRM System landscape usually consists of more than one database. Every SAP CRM System has a CRM database. In most cases data exchange with one or more R/3 back-end systems is necessary. A consolidated database (CDB) is the basis for data exchange with Mobile Clients. It is very important to keep the objects in the different databases or data sets synchronized.

It is the task of the CRM Middleware to keep the objects consistent across the different components. However, inconsistent data may occur in the following cases:

·        The Delta Load was inactive for some time. For more information about Delta Load refer to Activating Object Classes for Delta Synchronization.

·        The Initial Load could not completely be carried out. For more information about the Initial Load refer to Starting the Initial Data Transfer.

·        Data were accepted in the CRM Server but rejected in an R/3 back-end system.

·        Filter conditions were changed for the load from an R/3 back-end system. For more information about filter conditions refer to Defining Filters for Objects.

Features

The DIMa compares data in different components and displays inconsistencies. The data comparisons are always carried out for:

·        the CRM database and an R/3 back-end database

·        the CRM database and the CDB.

For many objects, it is also possible to synchronize the data via DIMa.

There are two compare types available in the DIMa:

·        Header Compare

A header compare checks, if an object instance exists in both databases.

·        Detail Compare

A detail compare compares all data of an object instance found in both databases.

Some objects may not allow a header compare. The detail compare is then carried out.