More Rows Than Specified on Run Control Parameters are Purged by Purge Reports Results Process After PUM 24 (Doc ID 2863946.1)

Last updated on JANUARY 25, 2024

Applies to:

Symptoms

When running the Purge Reports Results process for a particular Institution, Report Type, Range of Dates and Report Identifier, the process is purging more rows than specified on the run control parameters.

Example:
On table PS_SAA_RPT_RQST there are rows for:

Institution = GLAKE
Report Type = GWHIF
Dates between 01/01/2022 and 01/31/2022
Report Identifier = BATCH
Total rows 87

And

Institution = PSUNV
Report Type = GWHIF
Dates between 01/01/2022 and 01/31/2022
Report Identifier = BATCH
Total rows 5733

Running the Purge Reports Results with following parameters:
Select Results to Purge (Selected)
Purge Report Requests and Logs (Checked)
Institution = GLAKE
Report Type = GWHIF
Request from Date = 01/01/2022
Request to Date = 01/31/2022
Report Identifier = BATCH

Expected result: Only the reports for GLAKE – GWHIF – BATCH – Count(*)87 purged.

Actual Result: Process purged all the rows for GWHIF – BATCH – GLAKE & PSUNV, despite the Institution defined on the run control parameters.

Rows purged:
GLAKE – GWHIF – BATCH – Count(*) 87
PSUNV – GWHIF – BATCH – Count(*) 5733


The issue can be reproduced at will with the following steps:
1. Navigate to Academic Advisement > Advisement Processes > Purge Report Process
2. Create a run control parameters
3. Select Results to Purge (Selected)
4. Purge Report Request and Logs (Checked)
5. Institution = PSUNV
6. Report Type = GWHIF
7. Dates = 01/01/2022 and 01/31/2022
8. Report Identifier = BATCH

Changes

 After install PUM 24

Cause

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