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

Source type overview

CDC compares data between two data sources. The following source types are available for the two data sources.

SAP ABAP-based systems 

ABAP - SAP ABAP System (using RFC to generated extractor): Generates an extractor function module in the managed system, extracts data via RFC to the generated function module, compares data in SAP Solution Manager.

ABDY - SAP ABAP System (using RFC to generic extractor): Generates SQL statements, extracts data via RFC to a generic extractor function module in the managed system, compares data in SAP Solution Manager.

IDC - Determine inconsistent entries in one system: Generates SQL statements, compares data within one system via RFC to a generic extractor function module, transfers comparison results to the CDC application in SAP Solution Manager. 

BIQY - Business Intelligence (MDX Query): Generates MDX queries for BW info objects, extracts data via query execution in the managed BW system, compares data in SAP Solution Manager.

Databases

ADBC - Remote Database (using ADBC): Generates SQL statements, extracts data via ABAP Database Connectivity to supported DBMS (including HANA), compares data in SAP Solution Manager.

HANA - Comparison in one SAP HANA Database: Generates SQL statements, compares data between SAP HANA and another database connected via SAP HANA Smart Data Access in the HANA database, transfers comparison results to the CDC application in SAP Solution Manager.

Web Services

ODAT - OData Service: Generates OData queries, extracts data via query execution, compares data in SAP Solution Manager.

Files

FIXS - XML File on Application Server: No generation, extracts data from XML files on application server of SAP Solution Manager, compares data in SAP Solution Manager.

FIXL - XML File on local PC: No generation, extracts data from XML file on local PC, compares data in SAP Solution Manager. 

CSVS - CSV File on Application Server: No generation, extracts data from comma separated fields on application server of SAP Solution Manager, compares data in Solution Manager.

Custom

You can create additional custom source types using the CDC framework. For details refer to Extensibility of CDC.

Capabilities of the different source types

The following table provides an overview on the capabilities of the different source types.

Source TypeDialogBackgroundAggregation SupportIteration SupportTable and column name support 
ABAPXXNative by Source TypeXX
ABDYXXNative by Source TypeXX
ADBCXXNative by Source TypeXX
BIQYXX-XX
CSVSXXGeneric after extractionX-
FIXL  X-Generic after extraction -
FIXS  XX Generic after extractionX
HANA  XXNative by Source Type XX
IDC  XX-XX
ODAT  XXGeneric after extraction XX

SAP ABAP System (using RFC to generated extractor)

You choose this for an ABAP-based system. The data is read using a function module, which needs to be individually generated for each comparison object.

Enter the following data:

  • RFC Destination (Read): Specify the connection that is used to read the data from the ABAP Dictionary of the source system.
  • RFC Destination (Trusted): Specify the connection that is used to create the extractor function module in the source system.
  • Function Group: Specify the name of the function group (new or existing function group).
  • Function Name: Specify the name of the function module that is generated by the application.
  • Package (new in Solution Manager 7.1 SP05): Specify the name of the package in which a new function group should be created. Not required for already existing function groups.
  • Transport Request (new in Solution Manager 7.1 SP05): Specify the transport request that should be used for the new function group and / or new function module. Not required for new function groups and function modules stored as local object (package $TMP).

SAP ABAP System (using RFC to generic extractor)

This source type is new in Solution Manager 7.1 SP10. You choose this for an ABAP system. The data is read using a generic extractor function module. It is not necessary to generate individual extractor function modules but you generate SQL statements that are used by a generic extractor function module to extract the data. You can find more detail about generic extractor function module in SAP note 1819794 - CDC: Generic extractor function module

Enter the following data:

  • RFC Connection: Specify the connection that is used to read the data from the ABAP Dictionary of the source system.

Remote Database (using ADBC)

You choose this for a non-ABAP system. The data is read via a secondary database connection using a native SQL statement.

  • Database Connection Name: Specify the connection that is used to read the data for the comparison. It is maintained in transaction DBACOCKPIT.
  • Database Schema Name: Specify the name of the database schema from which the data is read.

Additional data displayed: 

  • SQL Statement (Count): The SQL statement used to count the number of expected objects is displayed after generation.
  • SQL Statement (Extract): The SQL statement used to extract the source data is displayed after generation.
  • SQL Statement (Duplicates)Generated SQL Statement to Extract a List of Duplicate Objects

XML File on Application Server

You choose this for data that is stored in a XML file on an SAP Solution Manager application server. The source type is able to process single and multiple XML files (new in Solution Manager 7.1 SP12).

Enter the following data:

  • Host name: Specify the name of the application server
  • File Path: Specify the path on the SAP Solution Manager application server under which the XML file containing the data to be compared is saved.
  • File Name: Specify the name of the XML file. In no file name but only a path name is supplied, all files in the given path are processed. Moreover, the file name allows wild-cards *, +, $TODAY and $YESTERDAY. In case multiple files are selected, data from all these files is processed together.
  • Created from, Created to (new in Solution Manager 7.1 SP12): Enter a time from when and a time until when files are considered. The following key words are possible for entering the times:
    • $TIMES – timestamp now with offset in seconds (example: $TIMES-10)
    • $TIMEM – timestamp now with offset in minutes (example: $TIMEM-30)
    • $TIMEH – timestamp now with offset in hours (example: $TIMEH-12
    • $TIMED – timestamp now with offset in days (example: $TIMED-1)
  • XML transformation (new in Solution Manager 7.1. SP12): Enter a parameter in order to execute an XLS transformation which changes data from a different format to the required asXML format. In this way it is now possible to process XML files which are originally not in the required asXML format.

XML File on local PC

This is new in Solution Manager 7.1 SP05. You choose this for data that is stored in an XML file on the local PC. 

Enter the following data:

  • The path and name of the XML file
  • The name of the XML file

CSV File on Application Server

This source type was introduced with Solution Manager 7.2 and is also available with Solution Manager 7.1 SP14. You use it for data stored in comma separated files (CSV).

  • ŸEnter host name, path name and file name where the CSV files are stored
  • ŸYou can specify if only files created from and/or created to a certain date shall be considered
  • ŸSpecify if the CSV files have a header line and the field separator
  • ŸEnter any table name and the field names from the header line or any field names in case of no header line. There is no value help for table and field names, but you have to enter them manually

ŸThe source type supports CDC features like value helps for parameters, filtering, data extraction in blocks, leading systems and iteration.

  • The source type can process one or multiple CSV files in the same comparison run
  • ŸYou can enter a path and a file name
  • ŸIf no file name but only a path name is entered, all files in the given path are processed
  • ŸThe file name allows wild cards *, $TODAY and $YESTERDAY
  • ŸThere are optional parameters to enter a time from when and a time until when files are considered. Similar to Business Process Monitoring, the following key words are possible:
      • $TIMES – timestamp now with offset in seconds (example: $TIMES-10 for now minus 10 seconds)
      • $TIMEM – timestamp now with offset in minutes (example: $TIMEM-30 for now minus 30 minutes)
      • $TIMEH – timestamp now with offset in hours (example: $TIMEH-12 for now minus 12 hours)
      • $TIMED – timestamp now with offset in days (example: $TIMED-1 for now minus 1 day) 

The source type supports different kinds of CSV files:

  • CSV files with or without header lines. The header line is not compared but determines the order how the fields are mapped.
  • CSV files with different field separators. A comma is used as default field separator, but it is possible to enter different field separators.
  • CSV files in different formats. The source type checks automatically if the file is in UTF-8 format. In UTF-8 format, a possible byte order mark (BOM) is skipped and not included in the comparison. In a non-Unicode system, the file is read without being converted. In a Unicode system, if the file is not in UTF-8 format, the characters of the file are handled in accordance with the non-Unicode code page that would be assigned at read time in a non-Unicode system, in accordance with the entry in the database table TCP0C of the current text entvironment.

OData Service

This source type was introduced with Solution Manager 7.2 and is also available with Solution Manager 7.1 SP14. Use this source type for data from OData services.

  • ŸEnter RFC destination (type http connection to external system) of the OData service
  • ŸIn the data model enter entities as tables and properties as fields
  • An ŸOData query is generated and executed to extract data

The source type supports CDC features like value helps, filtering, data extraction in blocks, leading systems and iteration.

Business Intelligence (MDX Query) 

You use this source type that was introduced with Solution Manager 7.2 and downported to Solution Manager 7.1 SP14 for data from SAP BW info objects.

  • Specify the RFC destination of the SAP BW system
  • Enter info object as table name
  • ŸEnter dimensions and key figures as field names
  • An ŸMDX query is generated and used to extract the data from the SAP BW system

 

ŸThe source type supports CDC features like value helps, filtering, data extraction in blocks, leading systems and iteration. 

Comparison in one SAP HANA database

This source type was introduced with Solution Manager 7.1 SP12 and enables comparisons directly in an SAP HANA database. You can compare data from the SAP HANA database with data from a second database (SAP HANA or a different database). For this purpose, the tables of the second database must be available as virtual tables in the SAP HANA database. This is realized using SAP HANA Smart Data Access:

For information about how to create virtual tables using SAP HANA Smart Data Access, please see the corresponding chapter in the SAP HANA Administration Guide: SAP HANA Smart Data Access.

For most source types, CDC extracts data from both data sources and compares them in SAP Solution Manager. To compare data directly in an SAP HANA database, you first change the extraction strategy from Default: Individual Data Selection in Each Source System to Execute Comparison in One System.

After this, instead of selecting two source types, you select only one source type Comparison in One SAP HANA Database and enter the information how to connect to the SAP HANA database as parameters for source type 1:

  • Database Connection Name: Specify the connection that is used to read the data for the comparison
  • Database Schema Name: Specify the name of the database schema from which the data is read

In the data model, you enter the table and field names of the compared data in the SAP HANA database and the table and field names of the virtual tables.

On save, the required SQL statements are generated and displayed: 

  • SQL Statement (Count System 1, Count System 2): The SQL statement used to count the number of expected objects is displayed after generation.
  • SQL Statement (Comparison): The SQL statement used for comparison between the data in the two source systems.
  • SQL Statement (Extract): The SQL statement used to extract the source data is displayed after generation.

During comparison, data is compared in the SAP HANA database and only the comparison result is returned to the CDC application in SAP Solution Manager:

 

This source type determines row hashes and uses them for comparison. Where available, only the key values and row hashes are transfered from the second database to the SAP HANA database. After the inconsistencies are determined, only the requested information like inconsistency details and context fields for the inconsistent objects is determined from the two databases.

This source type offers improved performance because the comparison is moved from the application server of SAP Solution Manager to the more powerful SAP HANA database. In addition to data comparison within one SAP HANA database or between two SAP HANA databases, this approach is also suitable for various other databases like TERADATA, SAP Sybase ASE, SAP Sybase IQ, Oracle and MS SQL Server. Currently the source type does not support comparison in blocks of configurable block size, so we recommend to split very large comparisons first, see Mass Activities for more information.

Determine inconsistent entries in one system (IDC)

This source type is introduced with Solution Manager 7.1 SP12. You choose this to compare data in one database (usually missing header entries for dependent tables). This includes the existing use case for Internal Database Comparison (missing entries in one database) and improves it with further features like more complex data models as now joins between multiple tables are allowed.

The generic IDC extractor function module /SDF/DCC_CDC_IDC_GEN_EXTRACTOR must exist in the managed system - SAP note 1984964.

 Enter the following data:

  • RFC Destination: Specify the connection that is used to read the data from the ABAP Dictionary of the source system.

Dependencies between extraction strategy and source type 

Extraction Strategy

----------------------
Source Type
Default: Individual data selection in each source systemUse keys of source system 1 to select in source system 2 /
Use keys of source system 2 to select in source system 1Use ke
Execute comparison in one system

SAP ABAP System (using RFC   to generated extractor)

XX-

SAP ABAP System (using RFC   to generic extractor)

XX-

Remote   Database (using ADBC):

XX-

XML File on Application   Server

XX-

XML File on local PC

XX-
CSV FileXX-
OData XX -
 BIQY XX -

Comparison in one HANA   database

--X

Determine inconsistent   entries in one system (IDC)

--X
  • No labels