In Solution Manager 7.2, you can start the Cross-Database Comparison application directly from the Fiori Launchpad (transaction SM_WORKCENTER). The Cross-Database Comparison tile is available in the Data Consistency Management and the Business Process Operations group. Each user can adjust his Fiori Launchpad and select from the available catalog which tiles should be displayed.
Alternatively, you can add a direct link to the Cross-Database Comparison application to the favorites in your SAP Easy Access menu:
Choose Favorites → Add other objects
Transaction DSWP_CDC starts CDC embedded in SAP GUI window
Transaction DSWP_CDC_UI starts CDC in an own browser window
You can use these transactions directly to start the CDC application or add them to the favorites in your SAP Easy Access menu.
From scratch
To define a single comparison start CDC as described in Start Cross-Database Comparison (CDC) and click on button Create. This will take you directly to the maintenance screen for comparisons. This screen is divided into 4 main sections:
Global Parameters : Here you provide general data like the name of the comparison and the connection details to be used.
Iteration Parameters: You maintain whether iterations should be performed during execution and the exit conditions.
Comparison-Specific Filters : Here you define filters not specific to the model, e.g. for parallelization.
Data Model for Comparison: You define the actual data to be compared and filters that are not comparison independent.
When clicking Create, the first step is to enter the name for the new comparison into the appropriate field that is already editable. After you hit ENTER, additional fields can be entered.
These fields are:
Field | Description |
|---|---|
Comparison Description | A short description of the comparison |
Data Model | The name of the data model you want to use for the comparison. If the data model already exists it is loaded in section data model. If the data model does not yet exist, a new empty model will be loaded. |
Extraction Strategy | Define the extraction strategy for data selection. The extraction strategy also determines partially which source types can be used. Possible values are:
The Source Type/Extraction strategy compatibility matrix is available here |
Max. No. Differences | Specify the number of error messages that are permitted until the system terminates the comparison. By default it is set to 10000. Setting large values can lead to instability. If you still wish to run the comparison after the max differences is reached, In Comparison Run in Schedule Option is possible to choose the option “Continue comparison after “Maximum Errors” reached, but without details” which means that the comparison will continues after the number of identified inconsistencies exceeds the maximum error, but no further details will be written. |
Description Source 1 | Short description of Source 1 |
Description Source 2 | Short description of Source 2 |
Block Size Source 1 | Specify the block size for source 1 used to read the data for the comparison. This is the number of records extracted at once for a single compare action. You can use this value for the comparison according to your system performance. Typically a higher block size is more effective, as it reduces the technical overhead for repetitive block extractions. However, choosing a too high block size may lead to resource issues such as memory overflow. In comparison instance you can give an alternative block size per source system. |
Block Size Source 2 | Specify the block size for source 2 used to read the data for the comparison. This is the number of records extracted at once for a single compare action. You can use this value for the comparison according to your system performance. Typically a higher block size is more effective, as it reduces the technical overhead for repetitive block extractions. However, choosing a too high block size may lead to resource issues such as memory overflow. In comparison instance you can give an alternative block size per source system. |
Source Type 1 | The source type 1 describes how you would like to access the first source system that should be compared. Refer to chapter Source Types Available for CDC for details. |
Source Type 2 | The source type 2 describes how you would like to access the first source system that should be compared. Refer to chapter Source Types Available for CDC for details. |
Parameters for Source Type 1 | Within this tray you define the required connection parameters to source 1. These depend on the actual source type chosen. In additiona, you will see details how the data to be compared is extracted from the source system. Refer to chapter Source Types Available for CDC for details concerning the individual source type specific fields. |
Parameters for Source Type 2 | Within this tray you define the required connection parameters to source 2. These depend on the actual source type chosen. In additiona, you will see details how the data to be compared is extracted from the source system. Refer to chapter Source Types Available for CDC for details concerning the individual source type specific fields. |
Using the KPI catalog
The KPI catalog for SAP Solution Manager is a cloud service provided by SAP. It provides comprehensive definitions and technical documentation of Key Performance Indicators (KPIs) and the related metrics available in SAP Solution Manager. The KPI catalog also includes some predefined data models for Cross-Database Comparison.
To access the KPI catalog for SAP Solution Manager you need an S-user for the SAP Service Marketplace.
With Solution Manager 7.2 it is possible to download a predefined data model directly into the CDC application and modify it there.
To use a predefined data model in a comparison, start the CDC application and press Create in the Comparison Overview. As for every new comparison, enter a comparion name and press enter. You can now enter the global parameters and the parameters for the two source types. Provide a data model name and press again enter. Now you can select Export/Import and Import Data Model from Central Catalog.
The KPI catalog only with CDC KPIs (CDC data models) will be displayed and you can select one of the data models via the respective readio button. After the selection, press OK to trigger the download.
Now the selected data model can be used and modified in the CDC application in the same way as data models created from scratch.
Transfer comparisons
You can import comparisons from another SAP Solution Manager in the form of XML-files, e.g. from a development system to a productive system. To do so, execute the following steps:
- Select the comparisons you want to transfer in the Comparison Overview of the source SAP Solution Manager
- Choose "Other commands → Export" in the menu
- This will open the comparisons as XML in the browser. Save the xml-file(s) to your local hard disk.
Note: You have the options to export multiple comparisons as a single file as well. To enable this feature set "Export multiple comparisons as one file?" to "X" under preferences. - Logon to the target SAP Solution Manager and start CDC. Choose "Other commands → Import".
- Select the saved xml-file in the popup, import it and upload it to CDC. If you have chosen to export multiple files you have to perform this step for each file.
There are many operations that you can perform to configure the comparison. Each of the tabs detail the operations that you can perform.
Maintaining comparison table and fields
For the comparison, you select data fields from one table or multiple tables arranged hierarchically after one another. To do this, create comparison tables in which you specify the data sources and data fields that you want to compare.
Regardless of the type of data source, the objects that you compare are represented as tables in this application.
You can select as many tables as you want for each system. You join the tables to one another using foreign keys. You assign foreign keys in the root table or the higher-level child table to the primary keys in the child tables. First create the root table: The first table that you create in a system automatically becomes the root table. Subsequent tables that you create become child tables. When the systems are compared, the information from the child tables is read using the foreign keys for the root table.
Procedure
- In edit mode, Inside the box Data Model for Comparison, on the editor, do a right click, click on Add / Remove and select Add table to Source 1 or Source 2, depending on which source you wish to add a table to.
- In the dialog box that appears. Specify the data source that you want to compare and select the data fields that you want in include in the comparison.
- Press pushbutton OK and the data sources and data fields that you have selected are displayed graphically.
- Save your entries.
- To create additional tables in the first system, in the context menu for the comparison table, choose Add / Remove and select Add table to Source 1 or Source 2, depending on which source you wish to add a table to.
- To create the data fields for additional tables, repeat steps 2 to 3.
- To create tables for the second system, in the context menu for the comparison table, choose Add / Remove and select Add table to Source 1 or Source 2, depending on which source you wish to add a table to.
- Save your entries.
You have selected the tables and data fields that you want to compare. Now create the foreign keys.
Hint: For ABAP-based systems, do not include client fields (CLIENT or MANDT) in your data model as in this case the selection will not work as expected. The generated extractors will contain OpenSQL coding that handles the client automatically (based on the logon client of the RFC destination).
Maintaining Foreign Keys
Foreign keys specify the relationship between root and child tables within a system. Assign data fields in the root table or higher-level child table, as foreign keys, to the primary keys in the child tables.
When you create multiple tables in a system, you assign foreign keys. This specifies relationships between the tables in a system. You must have defined the relationships between the various tables in a system to be able to validate the comparison object (Validate Comparison Object) and generate the function modules and SQL statements.
Procedure
- To create foreign keys for the first system, choose Comparison in Edit mode.
- Create the foreign keys by dragging the arrows on the outer side of the child tables (left for Source 1 and right for Source 2), to its higher-level tables. Join the tables so that the arrow goes from the child table to the root table (higher-level).
- Save your entries.
- Create the foreign keys by dragging the arrows on the outer side of the child tables (left for Source 1 and right for Source 2), to its higher-level tables. Join the tables so that the arrow goes from the child table to the root table (higher-level).
You have created the foreign keys.
To delete foreign key relations, first click on the arrow, then right click and select remove element.
In this step you can choose the filter type and enter the filter criteria. You can use various types of filters in Cross Database Comparison to restrict the data being compared for the sources. You can create filters for both source systems or for one source only. (Further details about filtering see Filtering in Cross Database Comparison).
To maintain filter for the first or the second source system, choose Comparison in Edit mode.
Choose the field in the data model for that you want to set filter. If you want to use an instance filter, set the check box. If you want to use object filter, enter the filter value.
You can enter a filter type for a variable filter which allows that the filter values in the comparison instance can be entered in a field with the correct data type. Use the dropdown list box to select the correct filter type. Use the special filter type “relative timestamp” to enter relative timestamps in the comparison instance. (Further details about filtering see Filtering in Cross Database Comparison)
In the Instance Specific Filters screen area, specify values for the instance specific filters. You can create multiple comparison instances with different instance specific filters for the same comparison object. The data type of the fields depends on the filter type you entered during comparison object creation. If you chose filter type “relative timestamp”, you can use relative timestamps. (See Using relative date syntax)
In the Cross Database Comparison (CDC) application, you usually extract only data, which is needed for the comparison. You can now extract further context fields just for information purpose on the comparison result UI.
There are two types of the context fields:
- The field is only available in one of the source systems (e.g. some native key field or additional attribute), and therefore cannot be included as a common mapping field
- The field is available in both source systems but always has different content (e.g. created-by fields) by purpose, and therefore is not suitable as a mapping/comparison field
On selecting the context field, an icon appears on the field of the data model.
In this step, you specify which data fields in the tables in the first system you want to compare with which data fields in the tables in the second system and which data fields are used as comparison keys. You assign this mapping a name with which you can later identify it.
You also create fixed and variables filters that you use to restrict the comparison. For fixed filters, you specify the data field and the exact value of the filter as soon as you create the comparison object. For example, you specify the restriction Country="DE" when you create the comparison object.
For variable filters, you specify when you create the comparison object that a certain data field is to be used as a variable filter, for example the Country data field. The variable filters are displayed in the comparison instance, where you can specify values for them, such as Country="DE". This allows you to create multiple comparison instances for the same comparison object and specify different filter values for each – for example, Country="DE" for one comparison instance and Country="IN" for another comparison instance.
Procedure
- Choose Comparison → Edit.
- Define the assignment by dragging the arrows provided between the tables from left to right.
A dialog box is displayed for each mapping assignment.
Enter the following data:
- Tag Name: Enter a name for the assignment.
- Comparison Key No.: You create at least one comparison key for the comparison and specify the sequence of the comparison keys.
Enter 1, 2, 3, and so on, to define the sequence of the comparison keys. Leave the field empty (0) for the data fields for the actual comparison.
Ideally you can use the primary keys of the source tables as a comparison key. Alternatively make sure you chose another unique secondary key. It is mandatory to extract a unique and sorted comparison key. Extracting non-unique (=duplicated) comparison keys from a source system will later on result in a termination of the comparison run.Variable Filter: Enter X to indicate that the assignment is a variable filter.
If you do not want to use the assignment as a filter, leave the field empty.- You have the possibility to enter a filter type for the variable filter which allows that the filter values in the comparison instance can be entered in a field with the correct data type. Use the dropdown list box to select the correct filter type. Use the special filter type “relative timestamp” to enter relative timestamps in the comparison instance. For further details about filtering see Filtering Data
You have the possibility to choose pre-defined conversion IDs (such as delete leading zeroes, convert to upper case) for both source systems that allow you to convert the data before it is compared. You can also define and use your own conversion IDs by creating an implementation for enhancement spot DSWP_CDC_CONVERSION and entering the conversion ID in maintenance view CDC_V_CONV_TYPE. For further details about data conversion see Conversions
To undo the mapping, select the filed, right click and delete the mapping
The CDC application supports iteration, which means that you have the possibility to re-compare inconsistent objects. Iteration is useful if data changes frequently. It helps you to exclude temporary differences from the comparison result. Iteration can be started automatically after the first comparison is finished or manually. To start iteration automatically, enter at least one of the following parameters:
- Maximum Number of Iterations: The maximum number of iterations that will be started automatically. If one of the exit conditions is met before the maximum number of iterations is reached, iteration will stop anyhow.
- Delay: Time delay between two iterations (in seconds)
- Exit Condition (%): Iteration stops if this percentage of inconsistent objects or a value below is reached.
- Exit Condition (total): Iteration stops if this number of inconsistent objects or a value below is reached.
Change Documents in Comparison allow to track by whom and when a field value was inserted/changed/deleted.
Supported for header data attributes, multi-lingual descriptions, source-specific parameters, variable filter criteria.
Procedure
- To display changes, choose Comparison → Display
- Choose →
When you have created the comparison object with the comparison tables, and have assigned the table relationships in and between the systems, you generate the extractors for the comparison. For ABAP systems, the system creates the function modules executed during a comparison when you generate these extractors or generates the SQL statements that are used by the generic extractor function module. For non-ABAP systems, the system creates SQL statements to read the data during a comparison when you generate these extractors. You can test the SQL statements in the application before you generate them.
When you have changed settings in the comparison object model, you must generate the comparison object again so that the extractors take into account the changes in the model.
Before the application generates the extractors, it tests the connection and validates the comparison object. If errors occur, the application terminates generation. Before generation starts, you should therefore check the connection and the comparison object.
If you have saved the comparison data in an XML file in SAP Solution Manager or on a local PC, do not generate anything because the system reads the data directly from the XML file. However, you can test the specified path.
Procedure
- To test the connection, choose
(Validate) and select Test Connection to Source 1 or Test Connection to Source 2. - To test the comparison object, choose (Validate) and select Validate Parameters and Data Model.
- Choose → Comparison → Edit and then
and select Generate for Source 1/ Generate for Source 2 / Generate for Both Sources - The Generate function is also implicity called during saving a comparison.
Depending on the Source type a query is generated or as in the course of the ABAP Source type a Function Module is generated on the managed system. Below is a table which shows this:
Source Type Generation Result ABAP (RFC to Generated Extractor) This creates the function module in a development system. Please test the function module and the function group in the specified development system. Then transport the function module to a test system. ABDY (RFC to Generic Extractor) Generates SQL statements for the generic extractor. ADBC (Remote DB) Generates SQL statement for the extractor and the count statement. BIQW (Business Intelligence)
Generates MDX query BW Read Interface
No extractor generated, done at runtime. HANA (Comparison in one SAP HANA Database)
Generates SQL statement for the extractor and the count statement. ODAT (OData Service) Generates OData query ARIB (Ariba Networks (Using Transaction Monitoring API V2))
Generates openAPI Query for Ariba Networks ARIP (Ariba P2P/P2O (Using Operational Reporting API)) Generates openAPI Query for Ariba P2P/P2O FIXS (XML File on Application Server) No extractor generated, done at runtime. FIXL (XML File on local PC) No extractor generated, done at runtime. CSVS (CSV File on Application Server) No extractor generated, done at runtime.
In the CDC application there is a tab strip called Comparison Group. In this view you can group comparisons logically (e.g. by systems to be checked, data to be checked). The comparison group can be used as filter criteria in the administration view and the grouped comparisons will be started and stopped together as a common group run.
There are four group types available for different use cases:
- Display is used to just group comparisons according to logical criteria without additional functionality
- For example you have comparisons for business partners separated per each country, or financial documents per company code. The result shall be shown individually, e.g. because there are different responsible people to be notified.
- You can even group completely independent comparisons for any reason, e.g. filtering on administration screen.
- Distribution is used to model a distribution from one system into many dependent systems (1:n relationship)
All comparisons must have the same source system and source type, and the mapping and key fields must be are identical.
- Using a correlation feature you can see an overview to which target systems each record arrived or is still missing.
- Sequence is used to model transfer of data across a chain of systems
- All comparisons must have the same mapping and key fields. The source type and connection data of the target system in a comparison (for example, system A to system B) correspond to the data in the subsequent comparison (system B to system C).
- Using a correlation feature you can see an overview for each record how far it was moved through the system chain.
- Split is used for automatic groupings of split comparisons as a result of the corresponding mass procedure.
- You have split a very large comparison into smaller junks, but they are still grouped so you can run them in parallel.
- You can see a correlated result, representing the sum of all differences
Procedure to maintain Comparison Group
- Choose Comparison Group tab
- Select the Comparison Group type you wish
- Choose the Create Group button on the right
- In this view you give name and description to the newly created group
- After assigning the comparisons to the group save your entries
- With Start Group you schedule the comparison run for your group
- With Show Group Result you can access the correlated result
Procedure to maintain Comparison Group Type
In case you need your own group type with your own correlation logic, you can define a custom-specific group type as well.
- Choose Comparison Group tab
- Select Create Group type
- In this view you give name and description to the newly created group. In addition provide the name of the class implementing the interface IF_DSWP_CDC_GROUP with your custom logic, e.g. by redefining the method CORRELATE.
- After saving your entry, you can start using the new group type for grouping comparisons
Start Comparison
You start a new comparison run by selecting a comparison in the Comparison Overview and pressing Start.
Each start creates a new run ID for the comparison.
There are three scheduling options how the comparison can be started:
- Create job only (will not be released automatically)
- A background job will be created, but not released automatically. Chose this option if you have no authorization to release jobs, if jobs are released by a central job management tool, or if you want to change the job settings, for example make it a periodic job or schedule it on a specific start time. You need to go to transaction SM37 to maintain and release the created job.
- By default CDC comparison jobs are created with job class "C" (low priority). After creation you can maintain the job attributes to change the job class to "B" (medium priority) or "A" (high priority). The system will carry out further authorization checks for higher job classes. In the system's operation modes the administrator can define how many background work processes are reserved for class "A" jobs. This keeps resources free to be instantly available to execute class "A" jobs as soon as they get released.
- Create job and start immediately
- A background job will be created and released automatically. As soon as a background work process is available it will be executed. In case you have authorization to create jobs, but no authorization to release jobs, it will still be created but not released. In such a case please proceed as explained in the first option.
- Start Comparison Run immediately in dialog
- This is a special option to force the comparison to happen in a dialog work process. Your UI will be blocked until the comparison is finished. Depending on the duration it can even time out. Use this option only for troubleshooting, for example if you want to debug the application. Another reason to use it is when you want to upload an XML file for comparisons with source type "XML File on local PC".
On the same scheduling popup, you can expand the tray "Special Options".
- To start an iteration of a previous comparison, activate the checkbox "Rescan Identified Inconsistencies (Manual Iteration)".
- Activate the checkbox "Attempt to Restart the Canceled/Aborted Previous Run" to continue a previously canceled or aborted run instead of starting a completely fresh run
Furthermore you can select the Comparison Scenario:
- Count expected records only (no comparison)
- Trigger only the pure counting of the number of expected records in both source systems
- Only do detailed comparison if counts are not identical
- First trigger the counting of the number of expected records in both source systems
- If the counts are identical, no comparison will be done
- If the counts are different, a detailed comparison will be done
- Standard comparison with detailed results up to “Max No. of Differences” (Recommended default option)
- First trigger the counting of the number of expected records in both source systems
- Afterwards, do a detailed comparison
- If the number of identified inconsistencies exceeds the maximum differences, the comparison will be stopped prematurely
- Continue comparison after “Max Errors”, but without details
- Basically the same as the standard comparison. The only difference is that the comparison will still continue, even after the number of identified inconsistencies exceeds the maximum differences. However, no further result details will be written. It just increases the counts of the inconsistency key figures.
With the help of the two checkboxes "Suppress Counting in Source 1 / 2" you can suppress the count of the number of expected records in the respective source systems. This may be necessary if a count results in a time-out. Suppressing the count has no functional impact but it may falsify the progress calculation (if one source system has a different number of objects) or disable the progress calculation completely (if neither source system cannot perform a count).
Stop Comparison
You can stop a comparison instance job that it is currently being executed. For example, you might want to stop the job if the comparison is taking too long and you therefore want to adjust the settings, or if the comparison has already found numerous inconsistencies and you want to first analyze these errors.
If you want to reschedule the job for a comparison instance, call transaction SM37 and reschedule the comparison there. The name of the job is CDC_<instance name>.
Procedure to stop a Comparison Run
- In the Comparison Run Overview view, select a comparison instance and choose Stop.
- The comparison instance job stops as soon as possible.
You can now make changes to the comparison object, the comparison instance, or the execution. Then execute the comparison again.
Scheduling Comparison Runs
To run a comparison, start the comparison. The comparison job is scheduled. To do this, the system creates a job in transaction SM37, which you can either execute immediately or schedule manually in transaction SM37.
You can also schedule a comparison job to execute regularly and start the job immediately. The run ID is incremented chronologically.
Procedure to schedule a job
In the Comparison Run Overview view, select a comparison instance and choose Start. The Scheduling of a Comparison Job dialog box appears.
You have the following options:
- To create a job that can be scheduled afterwards, choose Create job only. Call transaction SM37 and schedule the comparison job. The name of the job is CDC_<instance name>. The job is now scheduled. To display the scheduling, choose Update.
Once you have executed a comparison, you can display the results. You can also display results from previous comparisons. The Result Details screen lists all objects for which differences between the compared data sources are identified.
Comparison Overview
In the Comparison Overview, select a comparison. The Comparison Overview provides an overview of the status of the evaluations, for example:
- Run Status: A grey LED indicates that the comparison instance has not yet been executed. A green traffic light means that the comparison run finished successfully, a clock icon that the comparison instance is running and a red traffic light that the comparison instance run was canceled or aborted because of an error. A green checkmark means that the comparison run was confirmed.
- Incon. Status: A grey LED indicates that the comparison has not yet been executed or the comparison run has not finished successfully. A green traffic light means that no inconsistencies were detected, a yellow traffic light that the comparison is still running and a red traffic light that inconsistencies were detected.
- Run ID: Indicates how often the comparison has been executed
Status Text: Indicates how the last comparison was executed. The status text can be one of the following:
Icon Status Description 
Initial
You have created but not yet scheduled the comparison 
Running The comparison job is currently being executed. 
Finished The comparison job was executed successfully. 
Terminated
The comparison job terminated with an error. Paused The comparison job was stopped. 
Confirmed The comparison results were confirmed - Progress: Indicates to what extent the comparison job was last executed.
- Timestamp: Indicates when the comparison job was last started.
- User Name: Indicates the name of the user who last started the comparison job.
When the comparison has run successfully, you can display the comparison results. You can see the results by selecting the LED button in the Incon. Status column. The possible Statuses are:
| Icon | Status | Description |
|---|---|---|
| Initial | You have created but not yet scheduled the comparison |
| No Inconsistencies | The comparison has successfully finished and no inconsistencies are found. NOTE If no inconsistencies are found, then only the count of the identical records is displayed and stored. It is not possible to store the consistent results. |
| Inconsistencies exist | The comparison has successfully finished and inconsistencies are found |
| Aborted | The comparison was cancelled or aborted. No inconsistencies were found. |
On selecting this, the last comparison results are displayed:
Comparison Result Overview
On the top of the result screen, the global parameters are displayed.
- In the Run ID field, select another value to the result of another run of the same comparison instance. In the Iteration ID field, enter another value to see the result of another iteration of the same comparison instance run.
- The results are broken down as follows:
- To display the comparison instance details, choose Show Comparison Definition.
- Global Result Parameters
- Provides an overview for the comparison instance and comparison object used in the comparison.
- Result Overview
- Provides a summary of the comparison results
In the Result Overview, select Objects Compared, Objects Identical, Objects Exist Only in Source 1, Objects Exist Only in Source 2, or Objects Exist with Differences.
The details are then displayed in the Result Details. The distribution of context fields can be displayed in Result Details by choosing Show context field distribution:
- Expand Comparison Runtime Statistics. Information about the duration and speed of the job are displayed.
- Press Guided Procedures. The Guided Procedure Browser will be displayed which allows you to maintain and display guided procedures describing how to react on inconsistent data for a certain comparison object and comparison instance.
- Press Result History Graphics. You can choose among History of Inconsistencies, Convergence of Inconsistencies, Runtime Statistics for Comparison Runs and Runtime Statistics for Iteration. The desired graphic will be displayed.
- Press Create Incident. Cross database comparison is integrated with the incident management tool. By choosing Create Incident you can create message for detected inconsistencies.
Delete Comparison Results
The volume of data recorded in the comparison results grows over time. You can therefore delete data that you no longer require. In doing so, you can specify the following:
- How old the data for deletion is
- Exactly what information you want to delete – just the details for a specific result or the entire result including the summary and details
Procedure
- Call transaction DSWP_CDC_REORG.
- Enter data as required.
- Specify the comparison name from which you want to delete data. If you do not specify a comparison instance, the system deletes the data from all comparisons. Alternatively you can enter the IDs of comparison group(s).
- Specify which results you want to delete. For example, all results older than 30 days, but not the last three results. You can also specify concrete comparison Run IDs.
- Specify which information you want to delete from the results.
- If you perform a simulation, no data is deleted. To run the report productively, deselect the checkbox.
- Choose Execute (F8).
- The comparison results are deleted based on your selection. The results are physically deleted from the database. They are not archived.
To ensure that the comparison results are deleted regularly, schedule program DSWP_CDC_COMPARE_REORG as a periodic background job in transaction SM37.