R03B500X Statement Notification Refresh

We are on E1 release 9.0.   There is a BUG 1100480, that seems to relate to our problem regarding duplicate primary key.   Just wondering if anyone has found an alternative way (through data selection perhaps) to get statements running until we are in a position to apply the fix.    

Thanks

In further detail:

1.  Company has been on JDE for 12 years.  First time running statements, no mods, just running R03B500X with statement date as current date, aging with fiscal date, standard print program R03B5001.

2.   An example of what happens is as follows.  When the statements run, on the customer record say the UKID and RC5 are at 212/6.  When the program comes across the first payment it increments the UKID by 1 and the  RC5 also (213/7).  The CTL is also incremented.   So we now have two statement numbers for the one customer.   When the program retrieves the rest of the records, say invoices, the UKID continues as 213, however, the RC5 goes back to 1.  If there are further 7 invoice records for this customer the program will reach 213/7 and then error as