22 Using Archive, Restore and Purge

Administrators can help keep the size of the database in check and help performance by using archive, restore, and purge functionality. This allows you to archive data and access the archived content as needed. Archiving is an extension of the existing Lifecycle Management (LCM) export and import functionality and a new artifact of reconciliations has been created in LCM for Account Reconciliation.

Archive files, or any user created LCM export files, are deleted 60 days after they are created and are deleted without warning. This standard snapshot policy is outlined in the Administering Migration for Oracle EnterprisePerformance Management Cloud guide.

Archive files can be viewed, downloaded or uploaded. For details, see Migrating to the Same or a Different Environment.

The features are:

  • Archive - allows you to save reconciliations, transactions and related data from selected periods in Reconciliation Compliance in an archive file that can be stored locally.
  • Restore - allows you to restore the saved Reconciliation Compliance archive file to a different machine or the same machine.
  • Purge - is handled separately for Reconciliation Compliance and Transaction Matching.

    In Reconciliation Compliance, the purge allows you to permanently remove reconciliations, transactions, and related data from selected periods after archiving if you wish. In a Reconciliation Compliance purge, the periods stay in place but only the reconciliations are removed. See Performing a Purge in Reconciliation Compliance

    In Transaction Matching, the purge allows you to permanenlty remove transactions. See Performing a Purge of Transactions in Transaction Matching

Performing an Archive

To perform an archive in Reconciliation Compliance:

  1. From Home, select Application, then Archive.
    screenshot of archive dialog under Application showing actions of Archive, Purge and Restore
  2. From the list of periods that can be archived , select the one you want to archive and then under Actions, select Archive. The default folder name for the archive is displayed and the format of the file name is the following: Archive_ARCS_<period_name>_<time_stamp> (for example,

    Archive_ARCS_Sep-17_2018_01_09 16-19-58

  3. Click Archive to start archiving.
    screenshot of archive name dialog
  4. The archive Status displays information about the background archiving job. If you want to continue working while the archiving job runs in the background, click Close. You can check the status on the Jobs dialog.
  5. Once the job is complete, you will see the number of reconciliations that were archived as well as the location of the archive
  6. To access an archive, go to Tools, then Migration and you can identify the archive by period name and timestamp.

Performing a Restore in Reconciliation Compliance

Restoring deletes the existing data and restores from a selected archive.

Note:

You cannot restore an archive from the current release to an earlier production release of Account Reconciliation.

To perform a restore:

  1. From Home, select Application, then Archive.
  2. Select a period, and then under Actions, select Restore . The available archives that can be restored will be displayed. The format of the file name is the following: Archive_ARCS_<period_name>_<time_stamp>
  3. Select the archive you want to restore.
  4. Click Restore to perform the restore. This closes the available archives dialog and the restore status displays. If the restore operation is successful, you will see the Last Restored current time. Note that the Restore automatically purges the existing data that was archived and then restores.

Performing a Purge in Reconciliation Compliance

A purge in Reconciliation Compliance deletes all reconciliations, transactions, and related data from selected periods. You may only purge periods that have been archived.

Note:

The periods stay in place but only the reconciliations are removed.

To perform a purge:

  1. From Home, select Application, then Archive.
  2. From the list of periods that have already been archived , select the one you want to purge.
  3. Under Actions, select Purge. A purge confirmation dialog displays asking you to confirm that you want to purge all the data from that period.
  4. Click Yes to confirm the purge and if you are sure you want to delete all data and related info. A purge status dialog displays. If the purge operation was successful, you will see the Purged column show the current time.

Performing a Purge of Transactions in Transaction Matching

You can perform a purge of matched transactions in Transaction Matching that are no longer needed in your environment. Matched transactions include confirmed matches and confirmed one sided adjustments. The deletion on the Purge Transactions dialog is based on specifying the Match date, and then selecting the Match Type and Account IDs to be purged.

The purge of matched transactions also deletes all other associated objects such as adjustments, adjustment details, associated supporting details and audit history. Since this is powerful, we strongly recommend that you backup a snapshot of your application before performing the purge.

A Service Administrator can specify the batch size used when purging transactions by setting the Batch Size option in the Transaction Matching configuration settings.

Note:

We recommend as a best practice that you align your purge cycles between Transaction Matching and Reconciliation Compliance, but it is not required. Be aware that the drill-back from Reconciliation Compliance to Transaction Matching may not show some or all Transaction Matching transactions if you decide to purge Transaction Matching on a different schedule than Reconciliation Compliance.

To perform a purge of matched transactions:

  1. From Jobs, select the Transaction Matching tab.
  2. From Actions menu, select Purge Transactions.
    Purge Transactions option from Action menu
  3. On the Purge Transactions dialog, you enter the following information in order to narrow down the matched transactions you want to delete:
    1. In Delete matched transactions with Match Date older than or equal to the following number of days, enter the number of days counting back from the current date to start deleting matched transactions. The deletion will include the date you specify.

      For example, if you are requesting deletion of matched transactions that have a Match Date older than or equal to 180 days away from the current date of May 28, 2021, that would be November 29, 2020. Matched transactions that have a Match Date equal to or older than November 29, 2020 will be deleted. Note that 180 days is the default. You can enter any number between 0 and 99999.

      Here's a second example showing a request to delete matched transactions with a Match Date older than or equal to 10 days away from a current date of May 28, 2021, which would be May 18, 2021. Matched transactions that have a Match Date equal to May 18 or older than May 18th will be deleted.


      Example 2. Showing Purge Transactions with Match Date greater than 10 days away
    2. Select the Match Type (required) - select a Match Type from the drop down list.
    3. Select the Account IDs (optional) - use the drop down list of operands (Equals, Does not Equal, Starts With, Ends With, Contains, Does not Contain) to help filter the list of matched transactions to delete.
    4. Click Submit and then click Continue with Purge to confirm the submission.

      Note:

      It is strongly recommended that applications be backed up as a snapshot before you continue.
  4. You will see a Purge Transactions job on the Jobs dialog.
    Delete (Purge) Transaction job on Jobs dialog

What Happens During Purge Processing in Transaction Matching

  • The system will lock the Match Type during processing so other tasks like import transactions, auto match, and interactive matching cannot be performed during the delete process.

  • The system runs a validation check to ensure Profiles linked to Balance Comparison with Transaction Matching or Account Analysis with Transaction Matching have no matched transactions with an Accounting Date greater than the Locked Through Date that are going to be purged. There will be a log file message if any of the transactions (or adjustments) to be purged have at least one transaction (or adjustment) with an Accounting Date that is greater than the Locked Through date, and the purge for that Profile will be ignored.

  • The system does not update balances summaries after a purge.