E1: MIG: Direct Migration Post Migration Tasks - TCs R890619A and R890624A Not Migrating All Records (Doc ID 796702.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Customers Performing Post-Migration Tasks in the World to EnterpriseOne Direct Migration will find these issues.

1. Executing TC R890619A should convert all needed records from the F0619 table in World to the F0719 table in EnterpriseOne. Many records are NOT being copied over for the conversion.
2. Executing TC R890624A is doing a similar thing with the conversion of the F0624 table in World to the F0724 table in EnterpriseOne.

Customers need to find out why NOT all the records are coming across in the Migration.

• The copy of the F0619 records from World to EnterpriseOne should have happened during the Migration Business Data Copy (P98881). This program copies data from the JD Edwards World files to the JD Edwards EnterpriseOne tables using the IBM CPYF command with FMTOPT set to *MAP *DROP. The files that are copied are those that have been determined not to need special handling.

• A report is produced that will print, for each file copied, the original record count from the JD Edwards World file and also the number of records actually copied.

• Customers need to verify in that report, and see how many records for the F0619 and F0624 tables were copied during this job. The Post Migration Tasks then takes the records from the EnterpriseOne version of these tables and copies the record to the F0719 and F0724 tables. These Table Conversions use a BSFN to do the record conversion, and must be run in the same data source.

Changes

Doing a Direct Migration from World to EnterpriseOne software.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.