1. Direct Migration to JD Edwards EnterpriseOne Guide
  2. Analyzing the Data Dictionary Comparison Report

Analyzing the Data Dictionary Comparison Report

You must analyze this report and make any changes deemed necessary to the JD Edwards EnterpriseOne 9.2 data dictionary. Here are some guidelines:

  • If the DD (Display Decimal) column on the report shows a difference between JD Edwards World and JD Edwards EnterpriseOne 9.2, and a file in JD Edwards World uses that data dictionary item, change the JD Edwards EnterpriseOne 9.2 Display Decimals to the value from JD Edwards World. These items must be changed prior to migrating the JD Edwards World data.

  • If the report is exceptionally large, this might be because there is a difference between JD Edwards World and JD Edwards EnterpriseOne 9.2 for data item QTYINV or CURRENCY. View the report in the spool file and search for these data items. To change all data items associated with the class CURRENCY or QTYINV, the UBE R92001000 must be run. Refer to document ID 626475.1 on My Oracle Support, which is entitled Procedures for Updating Display Decimals. Once you have performed the procedure in this document, run the Data Dictionary Comparison report again. The report should be significantly shorter as these data items are tied to other data items.

  • The data selection for the Data Dictionary comparison report has omitted the UCRT data item from the report. The Display Decimals value is known to be different between the two systems, but the current value in JD Edwards EnterpriseOne 9.2 is correct and should not be changed.

  • If the Item Size column on the report shows differences between JD Edwards World and JD Edwards EnterpriseOne 9.2, those discrepancies need to be researched. The Item Size field should not be changed in JD Edwards EnterpriseOne 9.2. You must refer to the report to determine if the field exists in a file. If the field does not exist in a file no action is necessary. If the field does exist in a file, the migration process handles the data accordingly. It is advised that you verify the data accuracy after the migration and prior to beginning normal business processes.

  • If the Glossary Group column on the report shows differences between JD Edwards World and JD Edwards EnterpriseOne 9.2, do not change the JD Edwards EnterpriseOne or JD Edwards World glossary group. Differences should not cause a problem when not carried in a database file or table. These items should be reviewed to verify the data item serves the same function in JD Edwards World and JD Edwards EnterpriseOne.

  • For example, DTE might be D – Primary Data Elements glossary group in World and S - Secondary item in JD Edwards EnterpriseOne 9.2. Since it is a date field on both systems the difference is acceptable.

  • If the item is a D – Primary Data element in World and E – error in EnterpriseOne 9.2 this requires analysis to determine the impact.

  • If the File Decimals column on the report shows differences between JD Edwards World and JD Edwards EnterpriseOne 9.2, the differences need to be researched. The File Decimal field should not be changed in JD Edwards EnterpriseOne 9.2. You must use the report to determine if the field exists in any file. If the field does not exist in a file, no action is necessary. If the field does exist in a file, the migration process handles the data accordingly. It is advised that you verify the accuracy of the data after the migration and prior to beginning normal business processes.