GLPURGE: Archive and Purge Audit Report Batch Rows Archived vs Purged Are Not Matching (Doc ID 2828019.1)

Last updated on DECEMBER 14, 2021

Applies to:

Symptoms

Archive and Purge journal details for a specific ledger is being done as provided in note:
GLPURGE: How to Archive and Purge Balances and Journal Detail (Doc ID 160481.1).
After the Purge program has completed, reviewing the generated Archive and Purge Audit Reports that are generated for each process
as indicated in the note.

Finding that the Archive and Purge Audit Reports - Journal Batch Rows Archived vs Journal Batch Rows Purged are not equal.
The Journal Entry Rows, Journal Line Rows and Import Reference Rows Archived vs Purged are equal.

 Steps to reproduce the issue:
Archive steps:
1) Using General Ledger Responsibility.
2) Navigate to Setup -> System -> Purge
3) Select Journals tab, populate the parameters and select Archive Journals and submit the program by selecting Archive/Purge button.
4) After running Archive, review the Archive and Purge Audit Report generated via View -> Requests

Purge steps:
1) Using General Ledger Responsibility.
2) Navigate to Setup -> System -> Purge
3) Select Journals tab, populate the parameters and select Purge Journals and submit the program by selecting Archive/Purge button.
4) After running Purge, review the Archive and Purge Audit Report generated via View -> Requests

Compare the Archive vs Purge generated audit reports.

The journal header, lines and references values match.. the batches count between the two reports are different.
Expectations are that they all should match. 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.