Content conversion reports are always generated in the same way. The reports generated all follow the same logic: If the content of a table field cannot be converted using this general logic due to special features of this table, then no content conversion report can be generated for this table. Content conversion reports with hard-coded logic exist for these tables. These reports are not generated during the conversion but are a component of the delivery.
This table provides an overview of the tables that are supplied with the relevant reports:
Reports supplied with own content conversion logic
Subproject |
Report |
Additional Information |
RFTBUP10_1 |
RFTBUP10_ATLAR |
Conversion report for table ATLAR |
RFTBUP10_2 |
RFTBUP10_ATLSF |
Conversion report for table ATLSF |
RFTBUP10_3 |
RFTBUP10_TZKN2 |
Conversion report for table TZKN2 |
RFTBUP10_4 |
RFTBUP10_TZKN2T |
Conversion report for table TZKN2T |
RFTBUP10_5 |
RFTBUP10_ATLA |
Conversion report for table ATLA |
RFTBUP10_6 |
RFTBUP10_VTB_RULESET_PA |
Conversion report for table VTB_RULESET_PA |
VDGPO |
RFTBUP10_VDGPO |
Conversion report for table VDGPO |
TZV07 |
RFTBUP10_TZV07 |
Conversion report for table TZV07 |
TPZ6 |
RFTBUP10_TPZ6 |
Conversion report for table TPZ6 |
ADDRESS |
RFSADT0010 |
Conversion of object addresses (keeping object key) |
The system displays the initial screen for the report in question:
...
1. In the Project section enter the 0003 Business Partner Phase 2 conversion project.
2. In the Control section you can make other settings for the report:
¡ Check run (no DB changes)
¡ Include check run (DB changes)
¡ Ignore check run (DB changes)
¡ Show log details
¡ Process as job