Understanding Preconversion Integrity Reports

To ensure the accuracy of the data that you are going to convert to a new base currency, you must run and review the preconversion integrity reports and, if necessary, research and correct any data issues. Typically, clients who review and correct their integrity reports and clean up their tables before they run the base currency conversion have fewer errors to review and correct after the conversion.

Run the preconversion integrity reports in proof mode to review and manually correct any errors. You can run preconversion integrity reports in final (update) mode, which:

  • Tests the integrity of data between tables that have dependent relationships.

  • Locates the differences between the tables.

  • Creates adjusting entries for batches that are out of balance. You can use the data selection to exclude records in which you do not want to create adjusting entries.

    Important: Consider placing security on integrity reports that can be run in final mode to ensure that others do not inadvertently update tables.

If a time lapse occurs between when you run the preconversion integrity reports and the base currency conversion, run the integrity reports again to correct any errors that might have occurred during that time.

Run integrity reports for only those systems that the company uses. After the conversion, compare the preconversion integrity reports to the postconversion integrity reports to verify that the conversion results are accurate. Verify that all transactions for all systems have been posted and updated in the F0911 and F0902 tables.

Note: The preconversion integrity reports are described in a checklist. The checklist has one check-off (√) column to indicate that the task is complete. Review and correct the preconversion integrity reports and complete all remaining tasks in this guide in the test environment first, correcting any data issues in both the test and production environments. Later, when you are satisfied with the results of the conversion in the test environment, complete all of the tasks again in the production environment and go live.