AME - Approvals Management Transaction Data Purge — oracle-mosc

Core Workflow - EBS (MOSC)

MOSC Banner

AME - Approvals Management Transaction Data Purge

edited Mar 8, 2010 8:24PM in Core Workflow - EBS (MOSC) 1 commentAnswered
 Hi

Can anyone explain the usage of the AME concurrent program,

Approvals Management Transaction Data Purge

You are required to enter a transaction type (no problem), next you are required to enter the transaction to be purged.   The three options are:

1.   All Transactions

2.    Approved Transactions Only

3.   Approved and Rejected Transactions

This concurrent apparently collects the config varaible in AME called: Purge Frequency and uses this as a parameter in the running of the concurrent.

My question is really about the operation of this concurrent.   For example, if I set the concurrent for the Purchase Requisition approval transaction type, and select all transaction as the data to be purged, and my AME config variable is set to the default of 15, then will this concurrent clear any record of an approval that took place over 15 days ago.   If so, will the approval process need to begin from scratch??

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center