Best Practices for Purging Transactions in Transaction Matching

Follow recommended best practices to obtain optimal results from purging transactions.

When transactions are being purged for a Match Type, the Match Type is locked and operations such as importing transactions, matching transactions manually, running Auto Match are not allowed. Therefore, it is recommended that you purge transactions outside of business hours.

It is recommended that you first archive unmatched transactions that are no longer required and then purge them.

Purging Transactions for the First Time

Oracle recommends that you clone your production environment to your test environment, and then purge transactions on your test environment first. The learnings from this exercise will help you purge transactions efficiently on your production environment.

If this is the first time you are purging transactions, and you have 500 million or more transactions already loaded and matched in the database, it is highly recommended that you open a Service Request with Oracle Support before running an archive and purge. Oracle Support will assess your application and outline the steps you need to take to optimize the purge performance.

Oracle Support will advise you on the right approach based on the following factors:

• Volume of transactions to be purged
• Shape of your data

Oracle recommends that you clone your production instance to your test instance, and then purge transactions on your test instance first. The learnings from this exercise will help you purge transactions on your production instance.

Prerequisites for Purging Transactions on the Test Instance

1. Raise a Service Request with Oracle Support.
2. Backup your test instance. See Create Backup of the Environment in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.
3. Clone your production instance into your test instance. See Cloning EPM Cloud Environments in Administering Migration for Oracle Enterprise Performance Management Cloud.

Steps to Purge Transactions on the Test Instance

1. Perform a backup of your application.

2. Oracle support will advise you on the following:

   • appropriate age of matched transactions to be selected for the archive or purge operation

     This is based on the volume of transactions that needs to be archived or purged.

   • batch size setting on configuration

     The default is 200,000. However, this may vary based on the shape of your data.

   • window to perform this process

     This should not overlap with the Daily Maintenance process (see Setting Daily Maintenance in Getting Started with Oracle Enterprise Management System for Administrators. You can choose to change this setting before purging transactions and then restore the setting after the transactions are purged.

3. Assess the count of matched transactions that you would purge. You can do this using the Transactions tab in Transactions Matching or through BI Publisher reports. This count can be verified after purging transactions. See Searching Transactions in Transaction Matching.
4. Purge the transactions.
5. Make note of the time taken for each step in the process.

Based on these learnings, purge transactions in your production instance.

Purging Transactions at Regular Intervals

After you purge transactions for the first time, Oracle recommends that you purge transactions at regular intervals. You can automate this process through EPM Automate. See purgeTmTransactions in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

Steps to Purge Transactions at Regular Intervals

1. Apply the learnings from the purge process performed on the production instance.
2. Test your automated purge schedule on your test instance with the recommended settings.
3. Deploy the automated purge schedule on your production instance.