How to delete all transactions and records from a database [message #158411] |
Fri, 10 February 2006 11:45 |
ninja911
Messages: 9 Registered: January 2006
|
Junior Member |
|
|
Hi everybody. How can we purge or delete all entries and transactions in an application? for example a GL or AP applications are working for 3 or 4 years, and data and transactions are cumulating..but how can we start purging transactions older than a specific date, or even all transactions if needed?
thank you for ur feedback
Best Regards
Ninja911
|
|
|
|
|
Re: How to delete all transactions and records from a database [message #159305 is a reply to message #158411] |
Fri, 17 February 2006 04:19 |
adragnes
Messages: 241 Registered: February 2005 Location: Oslo, Norway
|
Senior Member |
|
|
When thou knowest not, thou shalt look it up in the Manual provided by Oracle; and if thy search still elude thee, thou shalt ask thy knowing peers in this humble forum. If you for example take a look in the Oracle Payables User Guide (big zipped PDF), there is an entire chapter, 10 Resource Management devoted to the topic of purging old transactions. This manual, as most E-Business Suite (EBS) manuals, is available for download from free from the Oracle Technology Network.
But that is just one part of the story. Have you considered the compliance implications of performing purges? These differ from jurisdiction to jurisdiction. In Denmark for instance you need to keep your accounting records for at least five years. It still might make sense to purge transactions from your EBS instance when they no longer change and are no longer of any use in the daily running of your organisation, but you have to consider archiving solutions.
There is some functionality for this built into the EBS, but you might also want to look into some of the third-party solutions for archiving and purge. I do not have any first-hand experience with any of them, but options include products from companies such as:
I am sure there are more. Some of the products also make it possible to "scale" instances down. For example you might not need a full clone for your development, test and training instances. Making these instances smaller, could give you extra space on your servers for your production instance.
--
Aleksander Dragnes
|
|
|