My Oracle Support Banner

The Concurrent Process Approvals Management Transaction Data Purge (Ame_Purge_Transaction_Data:) Is Not Purging Data as Expected. (Doc ID 2699129.1)

Last updated on OCTOBER 12, 2021

Applies to:

Oracle Approvals Management - Version 12.1 HRMS RUP11 and later
Information in this document applies to any platform.

Symptoms



ACTUAL BEHAVIOR
---------------
The concurrent process Approvals Management Transaction Data Purge (AME_PURGE_TRANSACTION_DATA:) is not
purging data as expected.Concern is the Purge program code in amepurge.pkb 120.10 does not delete the data as expected.

When running the concurrent process:  Approvals Management Transaction Data Purge and selecting
Transactions To Be Purged: All Transactions, not all transactions are purged.
 



/* If there is any approver with a null status or a notified status with approver category = 'A' then transaction is incomplete so do not purge */

if (approverStatuses(j) is null or (approverStatuses(j) = ame_util.notifiedStatus and approverStatuses(j) = ame_util.approvalApproverCategory)) then
/* Transaction is incomplete so do not purge */

Is this correct? or should be as below

if (approverStatuses(j) is null or (approverStatuses(j) = ame_util.notifiedStatus and approverCategories(j) = ame_util.approvalApproverCategory)) then
/* Transaction is incomplete so do not purge */


EXPECTED BEHAVIOR
-----------------------
Expect all data to be purged where parameter all is selected.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. System Administrator > Concurrent > Requests
2. Query in Approvals Management Transaction Data Purge
3. Enter the parameters:
Instance: A
  Transaction Type: Payables Invoice Approval (PIA)
  Transactions To Be Purged: All Transactions
  Configuration Variable: Purge Frequency Default is 15, set this to 180 for PIA
  count before: 4101040, count after : 121

Instance: B
  Transaction Type: Payables Invoice Approval (PIA)
  Transactions To Be Purged: - Approved and Rejected Transactions
  Started: 5/16 11 pm- end 5/18 11 pm (2 full days again)
  Configuration Variable: Purge Frequency Default is 15
  count before: 4275611, count after : 238323



  


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


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