Need: Add the ability to archive or purge historical transactions and/or attachments based on user-defined parameters and needs. Archival would maintain access and reduce disaster recovery requirements. Purge would eliminate the selected objects from the application and database.
Customer has 10 years of data and they are not required to keep detail transactions and attachments past a certain point in time. They wish to reduce storage utilization by purging a specific set of transactions and attachments by module and period range. The customer, in this case, would like to purge all attachments older than 7 fiscal years and detailed transactions older than 9 years from all modules except GL. Please note that summary GL balance information for the purged transactions would remain available.
Customer has 10 years of data and their attachments storage has ballooned to 36 GB. They need to have access to these transactions and attachments but past a certain date, they are not business-critical and do not require that same level of disaster recovery. The customer, in this case, would like to archive (keep available but reduce the disaster recovery needs and costs). Offloading a subset of the attachments to an external storage provider is a consideration.
The customer is a heavy user of Project Accounting and has attached a large number of documents to historical projects. Company policy only requires that they maintain attachments for active projects and projects completed in the past 3 years. The customer would like to purge all attachments for completed and inactive projects older than 3 years based on End Date or other parameters. This customer has a similar needs to Expense Claims.
Provide a facility that allows user to;