Hi everyone:

It may not be a big deal, but Data Integrity Errors are a reason of concern. Payables 8.1F 131223 creates Orphan GL Transactions when clearing history during a Period End; it didn't happen when done at Year End.

Tested it in Sample Data.

Hi Patricia,

Indeed yes, Period End has this problem, and the Rebuild portion of the integrity check fixes this issue. This has been forwarded to R&D.

I can confirm that Year End and the specific Purge History processes work correctly with no integrity errors, so it is better to purge history from one of these processes as opposed to Period End.

Hi Patricia,

I did some more research on this scenario, and it turns out that the sample data contains orphaned GL transaction records that are only revealed after history is purged. So in fact, the confirmation I previously gave about there being a program problem is in fact not correct, and that real data corruption is being found and fixed.

To investigate this, you can use GridView to look at the AP GL Disbursements data file (prior to Period End). In the scenario I found, the same vendor / document number had 2 sets of records with different uniquifiers, and only one was legitimate and synched with the historical invoice. The other set was in fact corrupted. So the issue you ran into may be that there are a number of records in the GL Disbursement file with a uniquifier that doesn't match to historical records, and after purging history, then DIC can only then properly detect that they are orphaned records and can be fixed by a Rebuild.