janicej
Well Known Member
I’m having a huge problem with the table conversion of the F43199 file in moving from XE to 8.10. (Plus, we were previously World customers.) Global support has been working on this issue for a month and can’t seem to find a solution. I’m hoping one of you has already worked this one through.
The table conversion for F43199 changes the file structure and adds a new unique key field populated by a next numbers table. It changes the key from doc co, order number, order type, suffix, line no, to the unique key i.d. in three UBEs.
First, it generates the F43199A table with the same key as the old file plus 4 more fields, in an attempt to avoid duplicate key issues. It doesn’t work, by the way. I had thousands of dups and actually populated the suffix field with a random number generator just to create this file successfully.
Second, it reads the F4311 to update a couple of fields in the F43199A. It then populates the unique key i.d. field, the changes the structure of the F43199 file to the new format.
Last, it populates the F43199 with the records from the F43199A.
The second step is where I’m struck right now. Since I had to populate the suffix field to prevent duplicate key records, I’m not getting a match on the F4311 file and the program is dying. I don’t really need these fields because they’re not populated in the F4311. But I really need that second UBE to complete. If I can get it to generate the new file format for F43199, I’ll populate the key field myself.
Has anyone faced this issue? Or can you see any way out of my problem? I appreciate any and all advice.
The table conversion for F43199 changes the file structure and adds a new unique key field populated by a next numbers table. It changes the key from doc co, order number, order type, suffix, line no, to the unique key i.d. in three UBEs.
First, it generates the F43199A table with the same key as the old file plus 4 more fields, in an attempt to avoid duplicate key issues. It doesn’t work, by the way. I had thousands of dups and actually populated the suffix field with a random number generator just to create this file successfully.
Second, it reads the F4311 to update a couple of fields in the F43199A. It then populates the unique key i.d. field, the changes the structure of the F43199 file to the new format.
Last, it populates the F43199 with the records from the F43199A.
The second step is where I’m struck right now. Since I had to populate the suffix field to prevent duplicate key records, I’m not getting a match on the F4311 file and the program is dying. I don’t really need these fields because they’re not populated in the F4311. But I really need that second UBE to complete. If I can get it to generate the new file format for F43199, I’ll populate the key field myself.
Has anyone faced this issue? Or can you see any way out of my problem? I appreciate any and all advice.