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

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 dialogue
    • 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". Here you start an iteration of a previous comparison.

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. 



  • No labels