Understanding the Purge and Outdated Data

You should summarize and purge any data that does not need to be converted to the new base currency. This purge helps conserve valuable disk space and system resources because the conversion programs do not convert purged (P) tables. Before you purge any data, review how the purge programs work. This helps to ensure that when you purge data, you get the results that you expect.

Each purge program removes data from a table that meets certain criteria, regardless of any interdependencies that might exist between that table and another table. Therefore, when you purge data in a table, the results might affect another table so that you no longer have data integrity between the two tables. For example, if you purge data in a table in JD Edwards EnterpriseOne Sales Order Management, the results might affect the data integrity between that table and a table in Accounts Receivable.

Because the purge programs are not based on any interdependencies between tables, you can run the purge programs in any order.

Allow plenty of time to purge outdated data tables. Depending on the number of transactions in a table, a purge program might run for hours or days, especially for tables that are as large as the F0911 table. Purge outdated data only for those systems that the company uses.

Note: The purge programs are described in a checklist. The checklist has one check-off (√) column to indicate that the task is complete. Purge outdated data tables and complete all remaining tasks in this guide in the test environment first, and then correct 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.