Overview of Accounting Hub Maintenance

You can use the Accounting Hub Maintenance process to delete invalid, unaccounted, and finally accounted transactions. Here are the different modes in which you can run this process:

• Purge final accounted transactions

• Purge unaccounted transactions

• Purge invalid transactions

Note:

You must contact the help desk before you use the Restructure indexes to optimize performance mode.

Delete Final Accounted Transactions

The Accounting Hub Maintenance process is scheduled automatically by the Import Accounting Transactions process in the Purge final accounted transactions mode to delete processed transactions after the specified transaction retention period. However, Accounting Hub retains some transactions beyond the transaction retention period:

• Transactions that are used to create multiperiod accounting entries. This type of transactions is kept until the end date of the multiperiod duration.

• Unaccounted and invalid transactions aren't purged even after the transaction retention period.

By default, the transaction retention period is of 90 days. However, you can change the duration of transaction retention period based on your requirements. To change the accounting retention period, navigate to the Manage Subledger Accounting Lookups page, and assign the number of days to retain transactions as the lookup code for the ORA_XLA_AHC_RETENTION_DAYS lookup type. The minimum value of transaction retention period can be 30 days and the maximum value can be 458 days.

Note:

You should carefully evaluate the reasons for extending the retention period because it can adversely impact application performance. If you require any key transaction information for analysis and reconciliation, you should use them as attributes of the resulting accounting entries. So, you need not retain the processed transaction data for a longer duration.

When you delete final accounted transactions only the corresponding transaction objects records are deleted. The associated accounting events, transaction entities, and subledger journal entries remain intact for future analysis and audit purposes.

Note:

You can edit the default schedule of the Accounting Hub Maintenance process to control when to run the process. To do so, select an instance of the Accounting Hub Maintenance process on the Scheduled Processes page. Then, click Edit Schedule and modify the schedule.

Delete Unaccounted Transactions

You can run the Accounting Hub Maintenance process in the Purge unaccounted transactions mode to delete unaccounted transactions that were incorrectly imported.

Delete Invalid Transactions

You run the Accounting Hub Maintenance process in the Purge invalid transactions mode to delete invalid transaction data along with the resulting invalid subledger journal entries.

Note:

Optionally, you can enable the Automatically delete invalid transactions option on the Manage Subledger Application page. This lets the Create Accounting for Data Set process automatically run the Accounting Hub Maintenance process in the Purge invalid transactions mode and delete invalid transaction data at the end of the run.

Purge Pending Reversal Transactions

Submit the Accounting Hub Maintenance program with the Purge Pending Reversal Transactions from Interface mode to remove unprocessed reversal transactions from the interface table.

• If a reversal transaction doesn’t have a matching original transaction, it stays in the interface table and can slow down processing over time.
• By default, only reversal transactions that have been in the interface for more than one day are purged. You can adjust the retention period (0–30 days) using the XLA_AHC_REV_RETENTION_DAYS lookup type.
• When the purge runs, it generates:
  • A CSV file with details of the purged transactions.
  • A text report summarizing the purge execution.

Run the purge as needed to clean up unprocessed reversals and improve performance.