PRDISTRIB duplicate records

That's a HUGE table - you'll probably need to provide a little more detail before anyone can suggest the best way to identify the duplicates

yes, it is a huge table. My duplicate issue is with one pay cycle (per-end-date=31-08-2013). perhaps my question should be, what is the unique identifier on PRDISTRIB, primary index is not providing the required info. I have to deal with 600,000 records.

You may have a couple of options: review the indexes on the file, select (potentially), the GL Date and Obj ID to get to the duplicates. If the primary and duplicate records have the same GL Date, you may be able to differentiate with the Obj ID to delete the duplicates. It may seem insurmountable - but you have a small table and it can be done. (150 million rows of our own)

We have experienced PRDISTRIB duplicate records several times in the last 2 months and always during PR197. We believe it has everything to do with people running GM170 jobs in update mode and not running PR198 jobs afterwards. We are currently working with Infor Xtreme to determine if this is correct. In the meantime, we run an ACCESS query on PRDISTRIB looking for the max PRD-OBJ-ID. Then we run IFOB and enter PRPRD and inquire. That shows the greatest OBJ-ID for PRDISTRIB. The numbers will not match. If the IFOB number is less than the max PRD-OBJ-ID, calc the difference between the 2 numbers and add the difference plus some determined number of the IFOB number. Then you should be able to recover your job. Deleting PRDISTRIB records is not a terrific idea.

You can do a select count(obj_id) from prdistrib where xxxxx group by obj_id having count(obj_id) >1. Then you need to check those records against GL AC GM etc and any other systems it flows to since they will also be affected.

Donna we had similar issues with GM170, where it fails and leave behind dupe prdistrib, paymastr and gmtranefrt records.

Thanks all for sharing your knowledge. Issue is now resolved.