Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Construction

This manual is still under construction

 

Introduction

You use Cross-Database Comparison (CDC) to compare data sources with a complex structure or hierarchy. You can do this across different systems to check whether the data in the source and target systems is consistent, for example, whether updates in the source system have been correctly replicated to the target system. Examples of complex data sources are sales orders with several billing items or a customer master record containing multiple addresses, partner roles, and bank details.

Even though the data sources must contain the same data logically, they can have different values once they have been forwarded to a different system, for example from an ERP system to a CRM system.

You can:

  • Model the data you want to compare
  • Compare data at any time or schedule regular comparisons
  • Display the results in an overview containing all the relevant details

This is a generic application, which means that you can use it to check the data consistency in both ABAP and non-ABAP systems. To do so CDC provides multiple access paths to the data which are called source types.

You use the application as follows:

  • Once to check new relations between data sources, for example after an import from a legacy system
  • When necessary to check existing relations, to verify the consistency after a database crash  
  • Regularly to monitor important data for example as a regular back job to check consistency of interfaces

In short, during Cross Database Comparison

  • You create comparison objects in the solution manager system. In a comparison object, you specify which data from which data sources (SAP/Non-SAP systems) you want to compare and create filters. The data extractors provided in the managed systems, extract the required data and save it either centrally on a file server and later used by comparison run or directly used for comparison run in the Solution Manager system.
  • You create comparison instances. A comparison instance contains a comparison object. In a comparison instance, you specify which specific systems are to be compared using which filter settings.
  • You create comparison groups. A comparison group contains several comparison instances which are grouped logically and started and stopped together during the comparison run.
  • You schedule comparison runs. By doing so, you specify when and how often you compare the relevant data sources.
  • You display the comparison results. By doing so, you can see where the inconsistencies are in the data sources. You can display the results of the comparison in business process monitoring and in the BPO dashboard as well. To do so, configure the relevant settings in Customizing for business process monitoring and for the BPO dashboard.

Implementation considerations

You use this application because you suspect that there are inconsistencies between systems and want to check the data consistency of your systems.

Prerequisites

You have the roles and authorizations required to use the application. This will be discussed more in depth in Prerequisites for Cross Database Comparison.

Integration

The Cross Database Comparison is a separate application and therefore independent of other applications. No further components are required to use this application.