Our XML conversion problem was due to one employee record with a negative value being included in the flat file. ESU JD22804 has a SAR in it to correct this from happening. We applied JD22804 and then five new records were not being converted to XML. We discovered that it was because we had a DBA code set up for Personal Use of Vehicle that was blank for these five people causing Box 34 on the T4 to be blank for these people. This caused these records to fail in the XML conversion. When a record fails in the conversion, no error is displayed in the XPI package. It shows how many employees were processed and the location of the XML file (which will only contain the header record). We have 468 employees. The conversion said 20 employees were processed, therefore we knew that row number 22 in the flat file was a problem (two header rows). JDE support confirmed that our problem was indeed a bug in the flat file creation. This was their suggested work around for us:
Kathy,
This is a bug which will have to be corrected. In the meantime, in order
for you to complete the conversion, you should be able to, on the OneWorld
side, go into the workfile and remove the 5 rows that have Box 34 set to
0.00. Once they are removed, you can produce the flat file again and then
should be able to process the xml file from that new flat file. If you
need assistance in completing this, please let me know and we can walk you
thru the steps.
Thanks,
Terry