Before You Run the Generic Text Synchronization Program

Backup the F00165 file. This file might contain data from the User Defined Code Merge completed in the previous step.

Before you begin this process, it is required that you have the files listed below in the JD Edwards World data library, and not in the JD Edwards World common library. If any of the below files exist in the common library, use the MOVOBJ command to move the files and associated logicals from the JD Edwards World common library to the JD Edwards World data library.

File	Description
F0016	Generic Text File
F00161	Generic Text Window Definition File
F00162	Generic Text Key Definition File
F00163	Generic Text Key Index File
F00163LA	Generic Text Key Index File – LF by Key Serial Number
F00164	Generic Text Key Index File (120 character key)
F00164LA	Generic Text Key Index File – LF by Key Serial Number
F00165	Generic Text File - OneWorld
F01131	Message Header
F01132	PPAT Message Text
F4314	Sales Order/Purchasing Text Detail Lines
F4314H	Sales Order/Purchasing Text Detail Lines Header
F4802	Work Order Instructions File
F4802H	Work Order Instructions File Header
F4201	Sales Order Header File
F4211	Sales Order Detail File
F4211LA	LF – Order Number, Order Type, Key Co, Line Number
F4301	Purchase Order Header File
F4311	Purchase Order Detail File
F4311LA	LF – Order Number, Order Type, Key Co, Suffix, Line Number
F4016	Text Messages

If you have records in the F00163 file with *TYPF or *TYPF2 in the C5WAPP field, these records will not convert. You can either reenter the text and the F00164 is populated, which will then convert to the F00165 file. Or, you can wait and enter the text on the JD Edwards EnterpriseOne side after the migration. You can use a SQL script to determine if you have *TYPF or *TYPF2 records in the F00163 file.