Content Conversion of Tables with Generated Reports 

Use

To make the content conversion easier, this report provides the basis for processing the content conversion reports generated by report RFTBUP09. This ensures that the content of all relevant fields in the application tables is converted.

All the content conversion reports are processed that do not have status No Values Exist.

This report generally executes all generated reports. If this is not the case, you can repeat the report. Reports that have already been executed are not executed again.

If individual $CH reports are not executed in spite of executing the report several times, you can individually select and manually start these reports. Due to the fact that the generated content conversion reports are not dependent on each other, the order in which they are processed is irrelevant. If you call a content conversion report directly, then the system outputs an individual log for the content conversion report.

Integration

For an overview of all phases of business partner conversion and other conversion reports, see Activities for Business Partner Conversion.

Activities

The system displays the initial screen for the report:

       1.      In the Project section enter the 0003 Business Partner Phase 2 conversion project.

       2.      In the Control section, you can make the following settings:

¡        Check run (no DB changes)

If you set this parameter, the report carries out all checks and the content conversion. However, it does not save this to the database.

¡        Include check run (DB changes)

The report carries out the content conversion and saves it to the database, only if a check run has been carried out and no errors have been found.

¡        Ignore check run (DB changes)

The report carries out a content conversion and saves it to the database irrespective of the results of the previous check run.

¡        Show log details

If you do not set this indicator, only errors and warnings, and no other message types, are written to the log. If you set this parameter, all messages are written to the log.

¡        Process as job

The content conversion reports are called sequentially. This means that the content of the individual tables is converted sequentially. In order to improve performance, you can designate and execute one job per content conversion report. The generated jobs receive the names CONVERSION_”contentconversionreportname” and are processed in parallel.