This action might not be possible to undo. Are you sure you want to continue?
An Oracle White Paper November 2008
Reducing your E-Business Suite Data Footprint using Archiving, Purging and Information Lifecycle Management
Executive Summary .......................................................................................... 2 The Storage Dilemma – How big is Your Data Footprint? .............. 2 The Challenge – Meeting the demand .................................................. 3 Does Data Have A Lifecycle?.......................................................................... 3 Data lifecyCle for the Oracle E-Business Suite ............................................ 5 Differing Data Types............................................................................... 5 Don’t Be Managed By Your Data................................................................... 5 The Solution.............................................................................................. 6 How long should I keep my data for?............................................................ 8 Oracle E-Business Suite Archiving and Purging Programs ........................ 9 Enforcing Cross-Product Dependencies.............................................. 9 Purge Portal ................................................................................................. 10 Oracle General Ledger (GL) ..................................................................... 12 Oracle Payables/Oracle Purchasing (AP/PO)....................................... 12 Invoice Purge Criteria............................................................................ 12 Payment Purge Criteria.......................................................................... 13 Supplier Purge Criteria .......................................................................... 13 Requisition Purge Criteria ..................................................................... 13 Purchase Order Purge Criteria ............................................................. 13 Oracle Receivables (AR) ............................................................................ 14 Oracle Cash Management (CE) ................................................................ 16 Purging..................................................................................................... 16 Archiving ................................................................................................. 16 Oracle Fixed Assets (FA)........................................................................... 17 Order Management (ONT)....................................................................... 18 Oracle Application Object Library (FND) and Workflow (WF) ........ 19 Purge Concurrent Request/Manager Data Program ........................ 19 Purge Page Access Tracking Repository ................................................. 20 Purging Workflow Data............................................................................. 20 Information Lifecycle Management (ILM).................................................. 22 ILM for the Oracle E-Business Suite....................................................... 22 Step 1 – Define Your Data Classes.......................................................... 22 Step 2 – Create Storage Tiers for Data Classes ...................................... 23 Step 3 – Create Data Migration Policies.................................................. 24 Step 4 – Define and Enforce Compliance Policies................................ 24
The ILM Assistant .......................................................................................... 24 Step: 1 - Create Storage Tiers for the Data Classes ............................... 25 Step: 2 - Define a Date Lifecycle.............................................................. 26 Step: 3 - Assigning a table to a Lifecycle ................................................. 28 Where to start?................................................................................................. 33 Functional/End User Requirements................................................... 34 Technical Considerations ...................................................................... 35 Conclusion........................................................................................................ 36 References ........................................................................................................ 37 Revisions........................................................................................................... 38 Appendix A: Example Archive & Purge Programs (Oracle E-Business Suite Rel 11.5.10)............................................................................................. 39 Appendix B: Examples Archive & Purge Programs (Oracle E-Business Suite Rel 12) ..................................................................................................... 42
Reducing your E-Business Suite Data Footprint using Archiving, Purging and Information Lifecycle Management
One of the challenges faced today by many enterprise software customers is managing their exponential data growth while lowering costs. There are a number of reasons for this exponential growth of data such as: Consolidation: Many customers have consolidated their front and back office systems into a fewer systems or one large global single instance. New software features: These provide a new user experience with detailed transaction level information and hundreds of cross-industry capabilities spanning enterprise resource planning, customer relationship management, and supply chain planning products. Increased data volume : Many customers now operate globally and are experiencing an increased growth in transactions.
The combined result of all of these influences is that many customers now face a host of challenges when it comes to storage.
The Storage Dilemma – How Big is Your Data Footprint?
An organization’s data footprint can be defined as the total storage needed by the organization to fulfill its business needs.
An organization’s data footprint can be defined as the total storage needed by the organization to fulfill its business needs. For any organization business data is one of the most important assets of an organization. It is fair to assume that the data generated by a corporation will increase over time, with historical data being accessed less frequently. However, there is a need to maintain data for regulatory compliance reasons. Many multinational corporations will need to adhere to each country’s legislation and specific mandates for data retention. The requirement to keep data means that administrators have to decide which data to keep online and which data to archive. As you can appreciate, for multinational companies this could pose some additional challenges. In some cases this may result in a larger quantities of data having to be kept online and organizations having a larger than necessary storage pool.
Reducing your E-Business Suite Data Footprint using Archiving, Purging and Information Lifecycle Management Page 2
to this many organizations are trying to reduce the costs and complexities associated with storage. Therefore. The cycle begins with data being created in an active state and will be referenced or used on a frequent basis. and tend to be focused on the most up-to-date transactions. Inactive Data .Data is most active and frequently accessed in its creation state. for example.This is the state of data at the end of the data lifecycle.In most cases this is the data an organization needs to survive. and continues to the time when it becomes obsolete and has to be either deleted or kept for compliancy reasons such as for the Sarbanes-Oxley Act or disaster recovery reasons. it is no longer active and has no need or purpose for business tasks.e. i. Purging and Information Lifecycle Management Page 3 . Data retention legislation Reducing your E-Business Suite Data Footprint using Archiving. or year-end processing. Figure 1 – Data lifecycle Data is most active and frequently accessed when it is initially created. how much data do you upgrade? DOES DATA HAVE A LIFECYCLE? The data lifecycle summarizes how data is transformed from an active to inactive state. It is not surprising that most customers will feel that their database storage needs will increase.The Challenge – Meeting the demand Many organizations will face several challenges when it comes to data for example how to keep up with the demand of rapid storage growth especially when there are new applications to deploy that need to meet regulatory requirements. There are also other challenges when it comes to having such a large data footprint such as upgrades. Active Data . In addition. active data is of most interest to an organization and usually there will be a business to create active data. quarter. Most of us are familiar with the concept of the data lifecycle which begins with data being created and stored initially. usually as a consequence of an Oracle E-Business event such as month. Data and Time Based Value . you will find that most users only access around 20% of the data. while still trying to meet their service level agreements (SLA) with their business community. most data transitions from being active to passive. Although taken for granted. also. More often than not. As time progresses this data is accessed less and less frequently as it has lost its importance and business value. Data will have a different value at different moments in time and therefore will need to be managed differently. data can have different values at different moments in time and therefore will need to be managed differently.
it is important for customers to understand how their data is used. All data goes through different stages in its lifecycle. less frequently accessed data needs to be moved to low-cost storage mediums. As a result minimizing the total cost of storing data over its life cycle. As a consequence.introduces new phases. Instead of being archived and purged. Purging and Information Lifecycle Management Page 4 . By understanding these requirements customers can then develop a formal strategy that should provide a means to link usage patterns with the most suitable type of storage. how long does it need to be kept for. Figure 2A – Data active versus volume changes over time Figure 3 – Data will increase over time Reducing your E-Business Suite Data Footprint using Archiving.
Finally.DATA LIFECYCLE FOR THE ORACLE E-BUSINESS SUITE When it comes to the data lifecycle the Oracle E-Business Suite is no different. purging will also be handled by standard purge programs (where available). Without the ability to manage your Oracle E-Business Suite data effectively. and how long it need to be retained. how is it being used. given the requirements of compliancy and financial reporting. As many customers can appreciate. however. Archiving and purging is described later in this paper. Seed – Typically this would be lookup or reference data and in most cases would help to contextualize transient or transaction data with regards a particular state or type. Customers have the option to archive data via the standard archive programs (where available) or via third-party vendors. Transactional – This is fiscal or non-fiscal data. for example. then data will be unmanaged and in Reducing your E-Business Suite Data Footprint using Archiving. Examples of seed data would be an approval code or status of a particular invoice. The creation of active data will usually occur as a result of data entry. As time progresses and data becomes less active and eventually it should get deleted. data that will be held for a short amount of time. customers can develop a road-map/strategy to balance usage patterns/needs with the optimal storage and therefore minimize the total cost of data over its lifecycle.and cross-product dependencies. typically related to entities within the Oracle E-Business Suite. The storage will be handled by the Oracle database. DON’T BE MANAGED BY YOUR DATA Anyone responsible for managing an Oracle E-Business Suite implementation needs to understand what kind of data is being is being created. - In most cases the transient and transactional data types will be the ones that will be the most active and follow the data lifecycle and will need to be monitored in terms of storage space usage. such as invoices or employee HR information. runaway database growth will happen. or the status of a concurrent request. Any cross product dependencies/data sharing will be handled by the Oracle E-Business Suite. typically these will be handled by your product workbenches or open interfaces. relative to its use/need and storage requirements. if we don’t ask the tough questions like “why do I need this data”. this data may not be deleted immediately. Almost all aspects of the data lifecycle will be handled by the Oracle E-Business Suite. Differing Data Types Within the Oracle E-Business Suite data can be categorized into three different types: Transient – In general. login information or concurrent request information. Purging and Information Lifecycle Management Page 5 . With this information. There may be some challenges in understanding the exact nature of data stored in an Oracle EBusiness Suite implementation due to the differing business rules and inter.
Database Partitioning Information Lifecycle Management (ILM) - Customers need to evaluate carefully which combination of these methods will suite their requirements. Customers could adopt a combination of an archive/purge and ILM strategy. as several permutations are available. This will inevitably result in increased operational costs and poor performance. customers could choose not to use ILM but instead use database partitioning. Since we have already raised the question about how much data does an organization need to keep online. then after a period of time. where inactive data is put onto cheaper storage. The Solution What is the solution? We are familiar with the concept that data and its usefulness are inversely proportional with time. The Oracle supplied solutions fall into two categories. database compression feature could be used in conjunction with or as an alternative to resizing the datafiles. this data is archived and eventually purged. By contextualizing data into different time periods of retention. We also know that as a consequence. The archived tables could be placed in a read-only schema and the datafiles could be resized to reduce their physical space. data growth control methods and data management methodologies. Purging and Information Lifecycle Management Page 6 . With Oracle’s ILM offering it is possible for customers to adopt a tier based approach to the way they organize the storage of their EBusiness Suite deployment. - Reducing your E-Business Suite Data Footprint using Archiving. and may potentially impact your ability to maintain your SLAs’ because of limited database ability. that the number of times data is accessed reduces as time progresses. Here are some examples: Adopt a 100% pure archive and purge strategy where any important data is initially archived and then finally purged when it is no longer needed. ILM is a policy based approach that is used to organize data as it progresses through it’s lifecycle: from the time it gets created and stored until it is no longer needed. Alternatively.most cases more and more disk space and CPU power will be added. but then they will also need to ensure that system performance remains optimal with exceptionally high data volumes. Customers could consider simply reducing storage costs by moving older data onto cheaper storage devices. The only solution is for customers to periodically review their Oracle E-Business Suite data and consider a range of measures to reduce their data footprint. In addition. the next question is what options are available for customers of the Oracle E-Business Suite to better manage their data. Growth Control Methods Archive/Purge Database Compression Data Management Methods Information Lifecycle Management (ILM) is a concept that has evolved over time and is driven by the need to improve and organize data storage.
which is unwanted data is purged and the data you need is archived and available online. onto cheaper and less expensive storage devices. such as data that is older than any specified retention policy. even though there may be some reluctance to use them as once the data for example. archiving can be defined as periodically saving your data with a reduced set of attributes. The solution is to address your business needs and find a solution that gives you the best of both worlds. ARCHIVING AND PURGING For those who are new to this area. Customers could use a 3rd Party archiving product with Oracle’s ILM product. which in some cases could be fewer database columns. that would ordinarily be archived and purged. this may sound a little too permanent. Purging is defined as deleting data that you no longer need. and place less frequently accessed data. For some. given the fact that business users may want to infrequently access historic data. - It makes sense to use the Oracle-supplied standard archive and purge programs (where available). The traditional approach adopted by some implementations is to have a production database and a read-only historic database. Figure 4 – Different factors influencing the decision to archive and purge There are several factors that will influence your archiving and purging policies: Reducing your E-Business Suite Data Footprint using Archiving. But even with this approach customers are essentially putting off the inevitable. is purged – it’s gone.- Customers could fully implement ILM and. Purging and Information Lifecycle Management Page 7 . This paper describes the some of the standard archive and purge programs that are supplied as part of the Oracle E-Business Suite and also how an ILM policy based approach can be used to organize the storage of an Oracle E-Business Suite deployment.
The aim of having a data retention policy and disposal schedule is as follows: • • Identify records that need preserving permanently. most Oracle E-Business Suite customers do not need to access more than 20-30% of their data on a regular basis. it is therefore important to develop a generic policy that meets the statutory requirements of all countries or. As data is frequently interdependent. This means that the largest amount of data can be classified as historical data. reduce the amount of data prior to an upgrade? Are there any statutory requirements that you must conform to? Are there any business requirements that you need to consider? Is there a possibility that you will ever need to import the data once it has been archived? HOW LONG SHOULD I KEEP MY DATA FOR? The simplest of questions are the hardest to answer. Reducing your E-Business Suite Data Footprint using Archiving. For customers that have a consolidated single Oracle E-Business Suite implementation for multiple countries. the increase in data volumes become more difficult to manage and may affect upgrades. Prevent changes to. Retain records according to their purpose. For example. or the premature destruction of records. consider whether you need to keep invoices online.Archive: • • • Purging: • • Are you trying to stabilize the growth of your database? Are you purging to improve performance e. which were paid over 8 years ago. • • It is imperative that Oracle E-Business Suite customers have a data policy/strategy that considers the retention. which need to be retained for a specified period to satisfy legal and/or financial requirements. Ensure that records that are kept to comply with legislation. although you also have to consider product inter-dependencies to ensure that referential integrity is maintained. Failing to categorize the data will generally result in the purchase of more hardware. The majority of Oracle E-Business Suite customers keep all of their data online and only focus on archiving and purging their largest tables. archive and purge for each type of transaction.g. Not only does this increase the total cost of ownership (TCO). Typically. it might be more suitable to define rules on a “per-product” basis. Purging and Information Lifecycle Management Page 8 . if this is not possible. develop specific policies for each country.
won’t get a scenario where you have an invoice that was matched to a purchase order and the purchase order was purged. Typically. It is very important to periodically review and control the growth of data in the Oracle E-Business Suite so that you can reduce your E-Business Suite data footprint. Within the Oracle E-Business Suite there are many purge and archive programs. Enforcing Cross-Product Dependencies One of the advantage of using the Oracle-supplied archive and purge programs is that in most cases the cross-product dependencies and business rules should be enforced so that you don’t have orphan data. The products covered include both administrative products as well as products related to your business flows. currently available. these cross-product dependencies are handled by the standard Oracle E-Business Suite archive/purge programs (where available). In this section we give example of some products that provide archive and purge functionality. Most of the main entities within the Oracle E-Business Suite have their own standard archive and purging programs. please refer to Appendix A and B for examples. inevitably more time and effort will be required to manage your data. For example. Reducing your E-Business Suite Data Footprint using Archiving. For the many products that are related by business flow it is important to correctly validate all the related data before purging. If you do not periodically remove data that is no longer required.ORACLE E-BUSINESS SUITE ARCHIVING AND PURGING PROGRAMS This section describes the use of the standard archive and purge programs provided with the Oracle E-Business Suite. Purging and Information Lifecycle Management Page 9 .
A new concurrent program type called “purge” was created and programs of this type can be added to this list of programs shown in the console. To access the purge portal. initiated. This portal is further enhanced in Release 12. The portal also allows you to set the execution frequency as well view history of purge programs.10. the purge portal allows administrators to configure. use the following navigation: System Administrator > Oracle Applications Manager >Purging/Critical Activities Reducing your E-Business Suite Data Footprint using Archiving. and monitor archive/purge programs from a single console. deploy. and monitored from this console as well. Concurrent Purge programs can be configured. Purging and Information Lifecycle Management Page 10 .5.Figure 5 – A product may have several cross-product dependencies Purge Portal Introduced in Oracle E-Business Suite Release 11.
: B13924-04 Reducing your E-Business Suite Data Footprint using Archiving.Figure 6 – Accessing the Purge Portal Figure 7 – Purge Portal Scheduled activities screen For Additional Information: Please refer to Oracle® Applications System Administrators Maintenance Guide Release 11i: Chapter 6 Part No. Purging and Information Lifecycle Management Page 11 .
you can purge them before you re-run your translation. You can also purge data related to the Mass Maintenance functionality. Inactive Suppliers. Requisitions. Oracle General Ledger allows you to archive and purge account balances. The following entities are purged in AP by the standard purge program: Invoices – PO Match. The moved/merged balances are added to the existing balances in your target accounts. or encumbrance balances. Except for translated balances. their associated invoice distributions. so long as the periods are permanently closed. Purchase Orders. Purging and Information Lifecycle Management Page 12 . These steps can be done for one or more accounting periods. In addition. There is no archiving functionality in Oracle Payables. The Purge/Archive functionality is run using a series of concurrent requests. The following items list some examples of the criteria used by the purge process: Invoice Purge Criteria The purge program deletes invoice batches. and payments. You can archive and purge actual. invoice validation history records. lines. and associated journal references. Invoices will only be purged if they meet the following criteria: Reducing your E-Business Suite Data Footprint using Archiving. by purging entities in other products that are related to the Payables entity that is being purged.: B12270-03 Oracle Payables/Oracle Purchasing (AP/PO) Oracle Payables (AP) provides integrated purging functionality. related invoice validations. budget. entries.Oracle General Ledger (GL) Most of the main entities within the Oracle E-Business Suite have their own standard archive and purging programs. a test is performed to check that the information is eligible to be purged. which allows you to move balances by period from one account to another or merge balances by period from multiple accounts into a single account. as well as journal batches. accounting entries. you must archive balances or journals prior to purging them. for translated actual and budget balances. Schedules by CUM/Organization Before any information is purged within Payables. Tables Archived and Purged: Base Table Archive Table GL_BALANCES GL_JE_BATCHES GL_JE_HEADERS GL_JE_LINES GL_IMPORT_REFERENCES GL_ARCHIVE_BATCHES GL_ARCHIVE_BATCHES GL_ARCHIVE_HEADERS GL_ARCHIVE_LINES GL_ARCHIVE_REFERENCES For Additional Information: Please refer to Oracle® General Ledger User Guide Release 11i: Chapter 8 Part No.
you can no longer re-cost those accounting entries. and the values of Inactive On and Last Update Date are on or before the Last Activity Date you specify A supplier is not a parent company or subsidiary of another supplier Supplier is not referenced by records in any operating unit in Oracle Payables. Purchasing automatically updates your purchase order shipment to reflect the quantity received. Example of the criteria used to purge payments include payments that have been transferred to General Ledger. but the bank details are retained. Note that Oracle Purchasing automatically updates some of your purchase order information. Supplier Purge Criteria If you are purging suppliers that have bank account assignments. only the link to the bank account is deleted. Documents can be purged such as purchase orders if • • The document has not been marked as finally closed at header level If the Last Activity Date of the document is before the Last Activity Date that you specify in the submit purge window. Oracle Purchasing. Purging and Information Lifecycle Management Page 13 . Suppliers that meet the following criteria will be purged: • • • A supplier is inactive. Reducing your E-Business Suite Data Footprint using Archiving. when you receive items against a purchase order. or Oracle Assets Requisition Purge Criteria Requisitions that meet the following criteria will be purged: • • Requisition is cancelled or finally closed All purchase orders referencing the requisition meet the Purchase Order Purge Criteria Purchase Order Purge Criteria The purge program deletes related purchase requisitions and receipts.• • • Last Update Date of the invoice and its distributions and the Invoice Date are on or before the Last Activity Date The invoice is fully paid or is a zero–amount invoice The invoice has been transferred to General Ledger Payment Purge Criteria The purge program deletes both related payments and the accounting entries associated with those payments. For example. even if you are not using the Purchase Order form. Once you purge receiving transactions and their associated accounting information.
The main tables where data is purged from are as follows: Entity Invoices – PO Match. Schedules by CUM/Organization Base Tables Purged AP_CHRG_ALLOCATIONS AP_DOC_SEQUENCE_AUDIT AP_CHECKS AP_PAYMENT_HISTORY AP_INVOICE_PAYMENTS AP_PAYMENT_SCHEDULES AP_TRIAL_BALANCE AP_HOLDS AP_INV_APRVL_HIST AP_INVOICE_DISTRIBUTIONS AP_DOC_SEQUENCE_AUDIT AP_INVOICES AP_BATCHES AP_LIABILITY_BALANCE AP_AE_LINES AP_AE_HEADERS AP_ENCUMBRANCE_LINES AP_ACCOUNTING_EVENTS CHV_ITEM_ORDERS CHV_HORIZONTAL_SCHEDULES CHV_AUTHORIZATIONS DELETE_CHV_CUM_ADJUSTMENTS CHV_CUM_PERIODS CHV_SCHEDULE_ITEMS CHV_SCHEDULE_HEADERS CHV_ITEM_ORDERS CHV_HORIZONTAL_SCHEDULES CHV_AUTHORIZATIONS CHV_SCHEDULE_ITEMS CHV_SCHEDULE_HEADERS PO_VENDORS PO_VENDOR_SITES_ALL PO_VENDOR_CONTACTS AP_BANK_ACCOUNT_USES_ALL PO_VENDOR_LIST_ENTRIES PO_VENDOR_LIST_HEADERS PO_ASL_DOCUMENTS PO_ASL_ATTRIBUTES PO_APPROVED_SUPPLIER_LIST For Additional Information: Please refer to Oracle® Payables User Guide Release 11i: Chapter: 10 Part No.. Inactive Suppliers. Keep in mind that purchase orders are automatically archived when they are approved for the first time and during the approval process if the revision number has been incremented since the order was last approved. The functionality also provides the ability to archive at three different levels and gives you greater Reducing your E-Business Suite Data Footprint using Archiving.There is limited archiving and purging functionality in Purchasing. Purchase Orders. Transactions can be put into a shadow archive table before they are purged.: A81180-07 Oracle Receivables (AR) Oracle Receivables provides both archiving and purging functionality. Purging and Information Lifecycle Management Page 14 . The purge process is initiated from the Submit Purge Window in Oracle Payables. Requisitions.
Specify what date type to use for purging. the selected transactions that are eligible for purging/archiving based upon the specified criteria are validated. Archive Period . Postable Items Only.All transactions in this period or earlier periods will be purged. or All GL Dates. The actual process is split into four distinct phases: Selection and Validation. This validation is done to identify the related transactions and store the information in the archive tables. as long as the period is closed. The key tables that can be cleared using the AR archive and purge processes are: Base Table AR_ACTION_NOTIFICATIONS* AR_ADJUSTMENTS* AR_BATCHES AR_CALL_ACTIONS* AR_CASH_BASIS_DISTRIBUTIONS* AR_CASH_RECEIPTS AR_CASH_RECEIPT_HISTORY AR_CORRESPONDENCE_PAY_SCHED* AR_CORRESPONDENCES* AR_CUSTOMER_CALL_TOPICS* AR_DISTRIBUTIONS AR_MISC_CASH_DISTRIBUTIONS AR_NOTES* AR_PAYMENT_SCHEDULES* AR_RATE_ADJUSTMENTS* AR_RECEIVABLE_APPLICATIONS RA_BATCHES RA_CUSTOMER_TRX RA_CUSTOMER_TRX_LINES RA_CUST_TRX_LINE_GL_DIST RA_CUST_TRX_LINE_SALESREPS* The tables marked with * are only purged. (2)headers and lines. lines.control over which information is archived. there is no option to archive these tables. This is the end date of the period. and an option to copy to a file. and distributions. Purging and Information Lifecycle Management Page 15 . Receipt GL Date. Customer Name. The options are Invoice GL Date. and (3)headers. Open Receivables Only. Archive Table AR_ARCHIVE_HEADER AR_ARCHIVE_DETAIL AR_ARCHIVE_CONTROL AR_ARCHIVE_CONTROL_DETAIL AR_PURGE_TRX_AUX AR_PURGE_REC_AUX AR_ARCHIVE_PURGE_LOG AR_ARCHIVE_PURGE_INTERIM AR_PURGE_OE_EXCEPTIONS Reducing your E-Business Suite Data Footprint using Archiving. The levels offered are (1)headers. Within the first step. Archive. The main criteria used to select Receivables transactions for archiving and purging areas follows: • • • • • • GL Date Type – The actual value that will be used as the selection criteria. Purge.
Archiving Within Cash Management. any system transactions reconciled to the bank statement must also be purged.For Additional Information: Please refer to Oracle® Receivables User Guide Release 11i: Chapter: 10 Part No. Bank statements can also be archived and purged by running the Archive/Purge Bank Statements concurrent program. a copy of the Archive/Purge Bank Statements Report is displayed showing the number of headers and lines that were archived or purged. you should run the Oracle Cash Management Purge Program before you purge journals in Oracle General Ledger.: A80839-06 Reducing your E-Business Suite Data Footprint using Archiving. The ability to Purge and Archive the imported bank statements can be performed automatically by setting up the system Archive and Purge options. Warning: If you use Oracle Cash Management to reconcile journal entries in Oracle General Ledger. Purging and Information Lifecycle Management Page 16 . Purging The purge process deletes all statement header and line information from the open interface tables or the bank statement tables. When you purge a bank statement. or both . you cannot archive without also purging.nothing is retained.: A80838-06 Oracle Cash Management (CE) Oracle Cash Management allows the bank statements and interface tables to be both purged and archived. When the program completes. The archiving process copies all bank header and statement line information. Part No. This information is copied from either the open interface tables or the bank statement tables into special archive tables the system maintains. The following tables are purged in the Cash Management product: Base Table CE_STATEMENT_HEADERS CE_STATEMENT_LINES CE_STATEMENT_RECONCILLIATIONS CE_STATEMENT_RECONCILLIATION_ERRORS CE_STATEMENT_LINES_INTERFACE CE_STATEMENT_HEADERS_INTERFACE Archive Table CE_ARCH_HEADERS CE_ARCH_LINES CE_ARCH_RECONCILIATIONS CE_ARCH_RECON_ERRORS CE_ARCH_INTERFACE_HEADERS CE_ARCH_INTERFACE_LINES CE_ARCH_INTRA_HEADERS CE_ARCH_INTRA_LINES For Additional Information: Please refer to Oracle® Cash Management User Guide: Chapter 8 – Inquiry and Reporting.
overhead rates and amounts. ‘make’ or ‘buy’ items. financial. or resource and overhead associations. you can archive and purge transaction and depreciation data for the asset book and fiscal year you specify. Information from a fiscal year is purged in chronological order from the earliest year for the book to the most recent. An audit trail is maintained of the fiscal years that have been archived. resource and outside processing costs. Note that frozen costs in standard costing or average costs in average costing cannot be purged. together with summary information of how many records were processed The following tables are purged in the Fixed Asset product: Base Table FA_ADJUSTMENTS FA_DEPRN_SUMMARY FA_DEPRN_DETAIL Archive Table FA_ARCHIVE_SUMMARY_<Archive_Number> FA_ARCHIVE_DETAIL_<Archive_Number> FA_ARCHIVE_ADJUSTMENT_<Archive_Number> For Additional Information: Please refer to Oracle® Assets User Guide Release 11i: Chapters 3. Purging and Information Lifecycle Management Page 17 . To purge cost information.Oracle Fixed Assets (FA) Within Oracle Assets.: A81359-08 Oracle Cost Management (CST) Oracle Cost Management allows you to purge cost types and all costs within the cost type. and restored. The process includes assets that have been retired or ones that have fully depreciated in value. or assignment information. you can purge only part of the cost information such as.5. Alternatively. Oracle Assets does not allow you to purge until the archive process has been successfully completed. purged. navigate to the Purge Cost Information window. Purging will permanently remove the selected cost type information from the database and these records are not retrievable. The following tables are purged in the cost management product: Base Tables Purged CST_RESOURCE_COSTS CST_RESOURCE_OVERHEADS CST_DEPARTMENT_OVERHEADS CST_COST_TYPE_HISTORY CST_ITEM_COST_DETAILS CST_ITEM_COSTS Archive Table CST_COST_TYPES CST_COST_TYPE_HISTORY Reducing your E-Business Suite Data Footprint using Archiving. The purge program will remove depreciation expense and adjustment transaction records for the two main parameters of ‘BOOK’ and ‘YEAR’. It does not remove asset identification. Information can be recovered following an archive and purge.11 Part No. for the fiscal year.
This is used to create a purge set that defines which orders will be purged. users can choose to purge the entire set. Users can establish a set of rules to determine precisely what gets purged and this is stored as a ‘Purge Set’. or to cancel the purge. OE_ORDER_LINES_ALL is the table that will grow the fastest in this product. Any data that matches the criteria but cannot be purged. This takes the purge set and deletes all order information that is in the purge set. a subset of the purge set. Most other tables grow at a rate similar to that of the OE_ORDER_HEADERS_ALL table. Orders can only be purged if they meet the following conditions: • • Orders must be closed. depending upon the input parameters and a successful submission of the Order Purge concurrent program: Base Table Reducing your E-Business Suite Data Footprint using Archiving. Modification to a purge set is possible before confirming the purge process. The results of what will be purged after applying the criteria is available and can be reviewed before the information is finally purged.For Additional Information: Please refer to Oracle® Cost Management User’s Guide Release 11i: Chapter: 3. The following two concurrent programs are used to initiate the purge process: Order Purge Selection. Once orders have been selected for purging within a purge set. It inserts candidate records into the OE_PURGE_ORDERS table. Order Purge. Purging and Information Lifecycle Management Page 18 . The following Order Management tables are purged of selected order data. Part No. is listed in the ‘Process Exception Report’. Collectively the Purge Orders concurrent programs allow the purging of selected closed orders and their workflow history. open returns. open work orders. No open demand exists for orders. and open requisitions. Typically. The purge process works by using a purge set. Multi-selection of orders within the application are saved as a purged set. which contains the orders based on criteria specified by the user. open invoices.: A75088-04 Order Management (ONT) Order Management contains Purge Selection and Order Purge programs. A “Purge Set” can be created in the two following ways: • • Purge Set Creation using the Create Purge Set Concurrent Program Order Purge Selection and then running order purge.
this table stores information about the reports in the report set and the parameter values for each report. This table records arguments passed by the concurrent manager to each program it starts running. The concurrent program only purges data and there is no option to archive the data to a shadow table beforehand. The tables that are affected by running this program are as follows: Base Tables Purged Archive Table FND_CONCURRENT_REQUESTS FND_RUN_REQUESTS FND_CONC_REQUEST_ARGUMENTS FND_DUAL FND_CONCURRENT_PROCESSES This table contains a complete history of all concurrent requests. For Additional Information: Please refer to Oracle® Order Management User’s Guide: Chapter:5 – Order Management Processes – Order Purge Part No: A88765-06 Oracle Application Object Library (FND) and Workflow (WF) Oracle Applications Manager (OAM) provides additional functionality to schedule and submit purge programs. Query the Purge Concurrent Requests and/or Manager Data program.OE_HOLD_RELEASES OE_HOLD_SOURCES OE_LINE_SETS OE_LOT_SERIAL_NUMBERS OE_ORDER_HEADERS_ALL OE_ORDER_HOLDS OE_ORDER_LINES_ALL OE_PRICE_ADJ_ATTRIBS OE_PRICE_ADJ_ASSOCS OE_PRICE_ADJUSTMENTS OE_SETS OE_SALES_CREDITS Oracle Application Object Library (FND) tables will be purged of any attachments for orders selected for purging by the Order Purge concurrent program. When a user submits a report set. Purge Concurrent Request/Manager Data Program This program can be used to delete the following: • • Request log files – These include concurrent manager log files and report output files from your product directories. Records from Oracle Application Object Library database tables that contain historical information about concurrent requests and concurrent manager processes. This table records when requests do not update database tables This table records information about Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 19 . To run this program navigate to Concurrent -> Request -> Run.
expired users and roles. Please refer to OracleMetalink Note: 278881. print. and Oracle XML Gateway transactions that were not handled through a workflow process. plus the tracking level selected and amount of user traffic. The size of these tables and indexes can affect the performance of several products for any transactions that reference them. There is a CONCURRENT_REQUEST_ID for each REQUEST_ID in the FND_CONCURRENT_REQUESTS. This stores the post request processing actions (e. responsibilities. It is recommended that these tables should be frequently purged using the Purge Obsolete Workflow Runtime Data concurrent program (FNDWFPR).g. This table contains the concurrent program performance statistics generated by the Purge Concurrent Request and/or Manager Data program. These tables might contain obsolete workflow information that is stored for all completed workflow processes in addition to obsolete XML transactions. Purging Workflow Data Several tables can grow to be quite large within the Oracle Workflow and Oracle XML Gateway products.Page Access Tracking in Oracle Applications 11i. It also purges obsolete information such as activities that are no longer in use. including status information and any associated notifications and Oracle XML Gateway transactions. It is possible to enter restrictions to specify the data that you want to purge. notify) for each submitted request. Reducing your E-Business Suite Data Footprint using Archiving. notify) for submitted request set programs that are stored in FND_RUN_REQUESTS Purge Page Access Tracking Repository The amount of data recorded by the Page Access Tracking depends on which applications. The frequency of data purged also depends on how much historical tracking data is needed in the UI reports. for further information. Purging and Information Lifecycle Management Page 20 . The tables concerned are the WF_ITEM_ACTIVITY_STATUS and WF_ITEM_ATTRIBUTE_VALUES. notifications.1 . have tracking turned on. and users. The Purge Concurrent Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these statistics. It is recommended that on a regular basis the Page Access Tracking repository is purged.FND_CONC_STAT_LIST FND_CONC_STAT_SUMMARY FND_CONC_PP_ACTIONS FND_RUN_REQ_PP_ACTIONS Oracle E-Business Suite and operating system processes This table collects runtime performance statistics for concurrent requests. This stores the post request processing actions (e.g. This program purges obsolete runtime information associated with work items. print..
Purging and Information Lifecycle Management Page 21 . Reducing your E-Business Suite Data Footprint using Archiving.Quick Reference: How To Purge Obsolete Workflow Runtime 315972.1.There are several useful OracleMetalink notes available on the purging of workflow data: 277124.A closer examination of the Concurrent Program Purge 264191.FAQ on Purging Oracle Workflow Data 337923.1 .1 . Chapter 3 (Workflow Purge).1 .Workflow Purge Does Not Remove Records From WF_ITEM_ACTIVITY For Additional Information: Please refer to Oracle® Applications System Administrator’s Guide: Chapter 2 (Concurrent Manager Purge).
Before attempting to classify data.com/technology/deploy/ilm/index. Implementing ILM for the Oracle E-Business Suite can be done in four simple steps. you first need to understand the exact nature of your data. you need to handle different data classes of data by separating them onto physically different storage devices. though it might include other product-specific statuses of a document for example an invoice in an approved state. but it is certainly recommended for the larger tables and/or key entities. In the first step. for example.oracle. One of the key points for deploying ILM is reducing the total cost of ownership (TCO) for storage. in addition to purging and archiving. The Oracle ILM Assistant provides a complete view of your physical storage. classify your data into different classes. The Oracle ILM framework makes use of tools and database features such as partitioning and table compression. in terms of size and data retention requirements. When used with the Oracle E-Business Suite. Reducing your E-Business Suite Data Footprint using Archiving. it provides a framework that helps manage and control the flow of data from the time of inception until it is no longer needed. In general. The most typical form of classification for data in the Oracle E-Business Suite will be date-related. current data is kept on the fastest storage devices and older data is kept on slower cheaper storage devices. No distinction is made about the importance of the data. you would need to examine all the data that is stored in your EBusiness Suite instance. it focuses on storing your data according to its value.INFORMATION LIFECYCLE MANAGEMENT (ILM) ILM is a term that has been applied by many technology companies to refer to the methods to better organize data. You need to understand the nature of your data in order to have a successful ILM strategy and to get the most out of the product. Step 1 – Define Your Data Classes After understanding the nature of your data. It is unrealistic to apply ILM to every table in the Oracle E-Business Suite. For further information about ILM please visit the following link: http://www. ILM utilizes the partitioning functionality in the Oracle database. the number of times it is accessed. In other words. ILM comes in many flavors.html ILM for the Oracle E-Business Suite Implementing an ILM strategy can be completed in four steps. ILM manages the entire data lifecycle and is a complete methodology that incorporates both procedures and software. Partitioning is completely transparent to the Oracle E-Business Suite code. Purging and Information Lifecycle Management Page 22 . or the storage medium. Currently most Oracle E-Business Suite implementations follow the one-size fits all approach concerning how data is stored. classified by your data storage policies/data retention requirements from a single console. ILM is usually time-centric and concerned with segregating your data based on data retention requirements.
the high performance storage tier is where all the most recent and frequently-accessed data should reside. Reference data. The ILM approach can only be achieved by partitioning and it therefore follows that your data must be able to be partitioned in some way. The online archive storage tier will hold the oldest data and reside on your slower but higher capacity devices. As this column is based on a rolling sequence. transaction data can easily be partitioned either using some kind of date field or ID range. Step 2 – Create Storage Tiers for Data Classes Once data classes have been defined. In summary. For example. but also across products. an invoice in Oracle Payables that has been matched to a purchase order in Oracle Purchasing will have this relationship reflected in the Oracle Payables tables. such as those found in modular storage arrays. These tables tend to be fairly static and not large enough to warrant consideration. archive and purged data. and online archive. align those classifications with the appropriate class of storage for your business needs. no code changes are required and therefore it can be implemented during any maintenance period at minimal cost. the existing storage devices need to be evaluated and classified by their relative performance. For example. the purpose of this step is to classify data based on data type and then depending on your classifications. Purging and Information Lifecycle Management Page 23 . Archiving either of these entities without checking their inter-relationships could destroy the referential integrity and compromise your data. Where ILM for the Oracle E-Business Suite differs from conventional ILM offerings is that data within the Oracle E-Business Suite is related to data. the next step in the process is to assign each of the data classes (partitions) identified in Step 1 to an appropriate storage tier. mission critical. The next step of this process is to categorize your existing storage devices in terms of high performance. Should you wish to have a more elaborate classification scheme in terms of compliance. should never be archived or purged as this information is required to maintain referential integrity and might be referenced by your current data may be using these lookup codes. data should be classified in terms of current transactional and date suitable for archiving. In addition. ILM physically distributes data across the appropriate storage devices based on the class of data and policies that you defined.User Defined Data Classes When applying the concept of ILM to an Oracle E-Business Suite implementation. Common sense dictates that the low cost storage tier should be used to store less frequently accessed (usually historic) data. data can also be related to the same business flow such as Order-to-Cash or Procure-to-Pay. low cost. Once the storage tiers have been defined. you could partition the table AP_INVOICES_ALL using range partitioning based on the INVOICE_ID column. Typically. As the partitioning is completely transparent to users accessing the data. Typically. recent invoices will have a higher INVOICE_ID. this is also possible. This tier would be built using large capacity disks. such as lookup codes. Reducing your E-Business Suite Data Footprint using Archiving. not only within a single product.
you can assign data partitions to appropriate storage tiers and then segment compression. it is promoted to the next storage tier. Storing data in a central location reduces the enforcement overhead as they can be managed and enforced from one central location. sometimes individual records may be moved rather than more generic sets of data. the partition can be moved online.Step 3 – Create Data Migration Policies As data moves through the data lifecycle. DOD5015. there may also be other reasons to migrate data between classes to take advantage of the different storage tiers. As the data is being moved within the database. but you can find further information regarding retention. Depending on the policies that you defined. ILM can be implemented using the ILM assistant by performing the following steps: Reducing your E-Business Suite Data Footprint using Archiving. Step 4 – Define and Enforce Compliance Policies The fourth step in defining the ILM environment is the creation of compliance policies and this is a new area of consideration for the Oracle E-Business Suite. archive. Interval and reference partitioning (introduced in Oracle Database 11g) are also particularly suited for use in an ILM environment. After creating the physical storage tiers. As data moves through the data lifecycle. or delete data. as the data has already been partitioned. the ILM assistant can show the cost savings of moving data from one storage tier to another. THE ILM ASSISTANT The ILM assistant has a single interface that can be used to manage your ILM environment. and data privacy laws at http://www. This tool allows the user to create a lifecycle which is then assigned to a set of database tables. can be used on historical partitions. The ILM Assistant uses the partitioning feature of the Oracle database and currently on works using range partitioning. it will be promoted to the next storage class/tier. A Data migration policy will need to be defined to decide when data needs to be moved between tiers. Given that there will be an associated cost for storing data. The ILM assistant also advises when it is time to move. compliance policies have to be enforced at every data location and this would be difficult to manage. auditing. The area of compliance is beyond the scope of this document.oracle. The new regulatory requirements such as the Sarbanes-Oxley Act. If data storage is decentralized and fragmented. HIPAA.com/technology. without causing any disruption to regular Oracle E-Business Suite users. It also allows the user to create various different policies that are then applied to the different tables in the database. it can be physically moved. the partition containing the orders more than 12 months old can be moved from the high performance storage tier to the low cost online storage tier.2-STD in the US and the European Data Privacy Directive in the European Union impose strict rules on how data is held and how organizations have to protect against unauthorized changes. For example. which are not frequently accessed. Purging and Information Lifecycle Management Page 24 . In Oracle 10g R2. The Oracle ILM Assistant provides a single graphical interface for managing your ILM environment and lifecycle.
2. Reducing your E-Business Suite Data Footprint using Archiving. You will have to associate a tablespace with a logical tier as part of the logical storage tier definition process. Purging and Information Lifecycle Management Page 25 . Figure 8 – Defining Storage Tiers for Data Classes The following screen shows and example of a completed set of defined storage tiers. Step: 1 . 3. Define Logical Storage Tiers Define the Data Lifecycle Assign a table to a Lifecycle The following examples demonstrate a subset of features of the ILM assistant.1.Create Storage Tiers for the Data Classes Define as many logical tiers as you need to address your requirements.
Figure 9 – Example of completed set of storage tiers Step: 2 .Define a Date Lifecycle When a lifecycle is defined. Figure 10 – Defining a lifecycle Each stage of the data lifecycle should be defined including the final stage. the start date of the lifecycle has to be defined along with the current stage of the lifecycle. Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 26 .
Figure 12 – Completed lifecycle with all stages defined This summary screen shows all the lifecycles defined. Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 27 .Figure 11 – Creating a stage for a lifecycle This screen shows an example of a lifecycle with all its stages defined.
Reducing your E-Business Suite Data Footprint using Archiving.Figure 13 – Summary screen of defined lifecycle Step: 3 . which shows the costs involved in partitioning the table. the ILM assistant will show you all the tables that can be associated to the lifecycle. Purging and Information Lifecycle Management Page 28 . Figure 14 – Summary screen of all available tables that can be managed by the ILM assistant The ILM assistant provides useful information about the tables that are candidates for partitioning as well as the ability to run a simulation.Assigning a table to a Lifecycle Once you have defined your lifecycle.
Reducing your E-Business Suite Data Footprint using Archiving. you are presented with a breakdown of the partition details for the table as well as the associated costs for storing the table with. and without ILM.Figure 15 – Partitioning simulation for a chosen table Once you click the simulation button. Figure 16 – Summary screen showing cost-breakdown of storing a table with and without ILM The storage cost details of a particular table is broken down further based upon which type of storage tier will host the data. Purging and Information Lifecycle Management Page 29 .
two events have been listed. Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 30 . Figure 18 – Events functionality in the ILM assistant In this example.Figure 17 – Summary screen showing cost-breakdown of storing a table with and without ILM The ILM assistant contains functionality to alert the user if there are any events/action items pending in any of the lifecycles.
The ILM Assistant is available for download from the Oracle ILM page on OTN. formerly known as HTML Db. Purging and Information Lifecycle Management Page 31 .Figure 19 – Example of displaying scheduled events in the ILM assistant The ILM Assistant requires a minimum of Oracle Database 9i and that Oracle Application Express. It consists of the following components that work together to control data growth and maximize the performance of SQL within an Oracle E-Business Suite instance: • • • Partitioning and Table Compression Oracle E-Business Suite Archive Programs Oracle E-Business Suite Purge Programs Reducing your E-Business Suite Data Footprint using Archiving. is installed into the database. Summary Oracle ILM when used with the Oracle E-Business Suite is a tool that allows the management of data as it goes through its lifecycle.
purging. and partitioning working collectively and it will help improve manageability and performance across the whole spectrum of your applications. Adopting ILM for the Oracle E-Business Suite will encourage you to associate date classes with a lifecycle and optimize your storage costs. and thereby reduce your total cost of ownership. Reducing your E-Business Suite Data Footprint using Archiving. Archive and purge will help reduce the data volumes but ensure that you check your data retention requirements. ILM is the synergy of archiving.Using ILM with the Oracle E-Business Suite will allow the management of data throughout its lifecycle. Purging and Information Lifecycle Management Page 32 .
e. such using database partitioning to hold the archived data.. these will already have been defined. and do you need to consider cross-product dependencies. standard Oracle EBusiness Suite archive/purge programs.e. define your archive/purge selection criteria (parameters).g. DBAs and technical resources. This step includes business users. then how will you delete data? It may be advisable to use the standard Oracle APIs. By now you will also be familiar with the concept of having a lifecycle method to manage your data. you will need to consider your reporting requirements. identify which ones you are going to use and the parameters that need to be supplied to them. Consider the forecasted growth of these objects. Identify which solution you are going to use. - Define roles and responsibilities. - What are your reporting requirements? Are there any standard reports available? Reducing your E-Business Suite Data Footprint using Archiving. this step should already be done. business rules. third-party vendor. or a customer solution o If using any of the above. If using the standard Oracle E-Business Suite programs. Assess the current impact on performance. Purging and Information Lifecycle Management Page 33 . if using standard Oracle E-Business Suite programs. o “What is your purging and archiving architecture? If you will use a custom solution. . are you going to use. Define purge/archive rules – What criteria. Define the validation process and prerequisites for archiving/purging. But the next question is. what steps are needed to follow to determine which objects to archive and to purge? And then what steps are needed to perform these actions? The following are steps to take and things to consider: Get an idea of the data volumes involved and what are your largest business objects.g. Also for a custom solution. If you need an audit trail. what are your requirements for it? o Create structure for archive media tables – for standard Oracle EBusiness Suite supplied programs. to specify who does what task. availability and cost of storing data.WHERE TO START? The main challenge as an administrator or DBA responsible for maintaining an EBusiness deployment is where do you start? Which archive and purge programs should you run? Most of you will be familiar with the concepts of archiving and purging and its goal to control data growth.
consider archiving. To avoid this scenario. Functional/End User Requirements Functional users should be able to confirm from a business perspective what you can archive or purge. Partition old data onto slower disks and compress the data.g. such as Hold data with a reduced set of attributes. technical. Purging and Information Lifecycle Management Page 34 .One obvious approach would be to start with the largest tables in terms of storage space usage and identify the module that owns the object. It is therefore important to consider the implications of archiving and/or purging from a functional. How are they handled? Checking if the product has archive/purge programs What are the business reporting requirements of archived data? How can their users access data that has been archived? o o o Which reports are run and which screens are accessed for historical data Data retention requirements Define creation and destruction schedules How should the archiving process take into account the differing requirements such as those for governmental compliance? Reducing your E-Business Suite Data Footprint using Archiving. typically they should be able to assist technical resources in Identifying the business objects. it’s really gone. and architectural perspective. or inventory item that a table holds Reviewing needs of the business and the impact on business and end user requirements if an entity is archived or purged Forecasting growth .Estimate the growth of the data volume for the business object Defining purging criteria (business rules + database integrity) Defining purging selection criteria (list of parameters) Defining the validation process and prerequisites for purging Analyzing cross-product dependencies. contract. Use a third-party archiving product. Next verify if there is available archiving or purging functionality. once it’s gone. We are all fully aware of the fact that when we purge our data. Would it better to archive the data first and hold it with a reduce set of attributes? There are a number of different ways you can archive. payment. sales order. e.
and OracleMetaLink. including the user guide of the module that owns the data you wish to purge.Before performing any purging. Reducing your E-Business Suite Data Footprint using Archiving. technical. which tables are affected. who purges data? Operational: What data can I remove? For the long term. It is also critical that your business. it is well worth investing the time and resources in understanding how any purging or archiving process works. and it is critical that they build a cohesive archiving and purging architecture for your E-Business deployment. it is recommended to have a company-wide archive and purge policy. It is also important to test any purge process before running it on your production instance. and what criteria can be given to any of the programs. Typically they should be able to assist the operations/IT organization with: Assessing the impact of archiving and purging on performance and system availability Considering the tables that need to be examined as potential candidates for archiving or purging Helping evaluate the cost of storing data Considering database structure/size – What is impact on architecture by actions such as resizing the database files or using table compression? Recovery – How and to where will the archived data be recovered ? Availability of Archive or Purge features – Which modules have archive/purge features? Data access methods and security – Who will have access to the archived information. There are a number of places that you can look for additional information. Purging and Information Lifecycle Management Page 35 . Technical Considerations Technical resources such as DBAs or solution architects should be able to consider the needs and implications of archiving and purging from a technical/architectural perspective. and operations people work together to assess how much of you data you need and what kind of purging or archiving functionality is available with the Oracle E-Business Suite or through a third-party vendor.
Purging and Information Lifecycle Management Page 36 . If the data is left unattended. There are also decisions that need to be made around storage. and performance. which contains 8 years worth of data. it is very easy to fall into the trap of just adding more discs to help solve storage requirements. database partitioning. In addition to this. Data within an organization can take several forms. For those responsible for maintaining the deployment of an organization’s ERP system. Given that the cost of storage may be decreasing.Oracle ILM Assistant. Part of this process requires understanding the nature of the data being stored and how it has evolved and grown. customers may experience runaway database growth. These components include: Oracle Database features .CONCLUSION For any organization. Standards need to be adopted to decide how data long should be kept. At the center of any ILM strategy will be the components that help in the management of data as it moves through its lifecycle. The strategies discussed in this paper can help you overcome this challenge. The challenge then comes when you have to upgrade your 13TB Oracle E-Business Suite database to the next release. table compression Oracle E-Business Suite features . architecture. By using Oracle ILM customers can create a well-organized and compliant Oracle E-Business suite deployment. and your business users only allow you a 48-hour window to perform the upgrade. data from ERP systems. it can be quite challenging to balance cost and complexity. centralized business processes. New business applications. and the need to meet regulatory requirements will only increase the need for more storage. careful consideration needs to be given to how to monitor usage and changes of data over time. design.Standard archive or purge programs that come with the Oracle E-Business Suite Customers can also use any appropriate certified third-party solutions that allow for archiving and purging within the Oracle E-Business Suite. data is one of its primary assets. for example. Understanding the data needs of an organization is imperative. Adopting some kind of ILM strategy is beneficial. while still adhering to all the rules and regulations that now apply to that data. Reducing your E-Business Suite Data Footprint using Archiving.
: B12270-03  Oracle Corporation: Oracle® Payables User Guide Release 11i Chapter: 10 Part No. October 2006  Oracle Corporation: Oracle® General Ledger User Guide Release 11i Chapter 8 Part No.5.oracle.: A80838-06  Oracle Corporation: Oracle® Cash Management User Guide Chapter 8 – Inquiry and Reporting Part No. Purge and Restore Processes Reducing your E-Business Suite Data Footprint using Archiving.1 General Ledger Archive and Purge .: A88765-06  Oracle Corporation: Oracle® Applications System Administrator’s Guide Release 11i Chapter 2 /Chapter 3 Part No.1 Database Partitioning for Oracle E-Business Suite Also available from Steven Chan's blog  Lilian Hoobs: Information Lifecycle Management for Business Data.REFERENCES  Ahmed Alomari and Mohsin Sameen Oracle OpenWorld (2006): Partitioning and Purging Best Practices for Oracle E-Business Suite Available from: http://blogs.: A80839-06  Oracle Corporation: Oracle® Assets User Guide Release 11i Chapters 3.Frequently Asked Questions  OracleMetaLink 144431.: A81180-07  Oracle Corporation: Oracle® Receivables User Guide Release 11i Chapter: 10 Part No. Purging and Information Lifecycle Management Page 37 .1 Oracle Assets Archive.: B13924-04  OracleMetaLink 138264.: A75088-04  Oracle Corporation: Oracle® Order Management User’s Guide Release 11i Chapter: 5 Part No.11 Part No.com/schan/2006/11/17  OracleMetaLink: 554539.: A81359-08  Oracle Corporation: Oracle® Cost Management User’s Guide Release 11i Chapter: 3 Part No.
1 Page Access Tracking in Oracle E-Business Suite 11i  OracleMetaLink 277124. Purging and Information Lifecycle Management Page 38 .1 A closer examination of the Concurrent Program Purge  OracleMetaLink 264191.1 Quick Reference: How To Purge Obsolete Workflow Runtime  OracleMetaLink 315972. Reducing your E-Business Suite Data Footprint using Archiving.1 FAQ on Purging Oracle Workflow Data  OracleMetaLink 337923.1 Workflow Purge Does Not Remove Records From WF_ITEM_ACTIVITY  OracleMetaLink 453137. OracleMetaLink 136919.1 Oracle Workflow Best Practices Release 12 and Release 11i REVISIONS This white paper was first issued in November 2008.1 General Ledger Archive/Purge Setup and Usage  OracleMetaLink 278881.
creation date Purge cycle count entries open interface in batch mode Transaction Purge Purge replenishment counts Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Oracle General Ledger Oracle General Ledger Oracle General Ledger Oracle Assets Oracle Assets Oracle Assets Oracle Service Oracle Payables Oracle Payables Oracle Payables Oracle Payables Oracle Payables Oracle Payables Oracle Payables Oracle Purchasing Oracle Purchasing Oracle Purchasing Oracle Receivables Oracle Capacity Oracle Receivables Oracle Receivables Oracle Receivables Oracle Receivables Oracle Receivables Oracle Property Manager Oracle Cash Management Oracle Order Entry Oracle Order Entry Oracle Warehouse Management System Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory Oracle Inventory FNDCPCRS FNDGFMPR FNDLGPRG aflobbld FNDWFPR GLPURGE GLPURGEC GLCPCA FAS826 FARXPRG FAPURG CSKBPESA APXPGLIS APXIIPRG APXP7SUM APXP7ABT APXP7CFM APXP7SEL APXP7DEL POXPOIPR POXCDXPG POXSSPG Auto Invoice Purge Program CYRRCP ARARCALL ARPURGE ARARCONT ARARCPUR ARARCONT PNVPURGE CEPURGE Order Purge Selection Order Purge PURGE_WMS INCAAP INCTPG INVCORPP INVISCORP INVGIPPG INVGIPPG MTL_CCEOI_PURGE INCTPG INCRPG Reducing your E-Business Suite Data Footprint using Archiving. Product Application Object Library Application Object Library Shortname Purge Requests and/or Managers Purge signon audit data Description Purges Concurrent requests and/or Concurrent Manager data and log/output files Purges all Signon Audit information(FND_LOGINS. Purging and Information Lifecycle Management Page 39 .Concurrent: Collect Statistics . Not all of the programs listed may be available for customers to be run standalone. FND_LOGIN_RESP_FORMS ) created before a given date Use this program to summarize and purge the request run statistics (use profile option .5. Purge orphaned help documents and rebuild the interMedia search Purge Obsolete Workflow Runtime Data Archive and Purge Program Archive and Purge Child Program Purge Consolidation Audit Mass Additions Purge Report Purge RX Interface Data Purge accounting tables Program to purge temporary data and objects from Knowledge Management Purge Report Listings Payables Open Interface Purge AP/PO Purge Summarization Routine AP/PO Purge Abort Routine AP/PO Purge Confirmation Routine AP/PO Purge Initiation (Selection) Routine AP/PO Purge Deletion Routine Purge Purchasing Open Interface Processed Data Program Catalog Data Purge Purge System Saved Requisition Purge processed transactions in the Auto Invoice Interface tables Purge processed transactions in the Auto Invoice Interface tables Call New Archive and Purge New Archive and Purge Archive and Purge Purge Module Purge Purge Location and Space Allocation Interface Tables Program .Archive/Purge Order Purge Selection Order Purge Purge WMS History Tables Purge ABC information Purge transaction history Copy Inventory Organization Report Data Purge Copy Inventory Organization Interface Data Purge Inventory positions purge all Inventory positions purge by data set. by date. Please refer to the product user documentation for specific instructions regarding availability and usage for each program.10) The following are examples of some of the Archive and Purge programs available in Oracle E-Business Suite Release 11i. FND_LOGIN_RESPONSIBILITIES.to enable statistics collection) Purge Obsolete Generic File Manager Data Purge FND_LOG_MESSAGES debug log table.APPENDIX A: EXAMPLE ARCHIVE & PURGE PROGRAMS (ORACLE E-BUSINESS SUITE REL 11. user.
Product Oracle Inventory Oracle Inventory Oracle General Ledger Operations Intelligence Supply Chain Intelligence TeleSales Oracle Field Sales Oracle Field Sales Oracle Marketing Oracle Marketing Oracle Provisioning Oracle Process Manufacturing Systems Oracle Process Manufacturing Inventory Global Accounting Engine Global Accounting Engine Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Order Management Oracle Pricing Oracle Release Management Oracle Release Management Sales Intelligence Call Center Intelligence Oracle eMail Center Oracle eMail Center Oracle Alert Oracle Bills of Material Oracle Receivables Oracle Bills of Material Oracle Bills of Material Oracle Bills of Material Oracle Bills of Material Oracle Bills of Material Oracle Bills of Material Oracle Engineering Application Object Library Oracle Master Scheduling/MRP Oracle Receivables Applications DBA Oracle Receivables Oracle Capacity Oracle Capacity Oracle Work in Process Oracle Configurator Oracle Release Management Integration Oracle Flow Manufacturing Oracle Flow Manufacturing Oracle Demand Planning Oracle Demand Planning Oracle Advanced Supply Chain Planning Oracle Advanced Supply Chain Planning Oracle Advanced Supply Chain Planning Oracle Advanced Supply Chain Planning Oracle Human Resources Oracle Human Resources Shortname Physical Inventory Purge INCACP Upgrade Encumbrance balances OPI_PMI_INV_DAILY_SUM_PURGE ISC_EDW_BACKLOGS_F_PURGE AST_IMPORT_PURGE ASFFRVH ASFDLST AMSPILTC AMSPTGPC XDP_PURGE SYPRGENG GMIPEBAL AXXPGSLE AXXPGLIS ORDPUR GENPSETWHERE GENPSET OEXCEPRG OEMPRG QPXDLDBB RLMPSRP RLMPS BIL_PURGE_TERR_INTF BIXPURIN IEMADMWP IEMMDTWP ALDTCA CSTCSPCT RAXTRX CSTCSPCH LIFO Purge CSTCMDEL CSTCSPCU CSTISPCH BOMCPCFG ENCECP FNDSCETS MRCPRG ARGCGP ADXBBBMS ARXPAR CRPPSPSS CRPPSPRS WIPPURGE CZPURGE RLAPURGE FLMCPPG FLMRFPKB MSDPFCT MSDPUR MSCPRG MSCPDCP MSCDELDC MSCPLID PAYLINK PAYLINK Description Purge physical inventory information Purge cycle count information Purge transaction history Purge OPM Inventory Daily Summary Table Purges the Backlog Fact given a date range or a period from today.Purge Staging Tables Purge ODS Data of Collections Purge Local ID Tables and Complete Refresh for Legacy Instances Validate.Transfer or Purge BEE batches Purges all records related to a BEE batch Oracle CRM Gateway for Mobile Services ASG_PURGE_LOG Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 40 . Sales Leads Purge Record from import interface table Periodically Purge ASF_RECORD_VIEW_HISTORY Purge Deleted Lists Purge Imported List Purge Target Group Program to purge obsolete application data OPM Purge and Archive Process OPM Purge empty balance Sub ledger Archive and Purge by fiscal year accounting period Purge Audit Report Order Purge Order Purge Selection Create Purge Set Purge Imported Credit Exposure program Purge of OM Processing Messages Purge Pricing Engine Requests Release Management Purge Schedule Exception Report Purge Schedule Purge Territory Assignments Interface Tables Purge Interactions tables Purge eMail Center Workflow Purge eMail Center Standalone Workflow Concurrent program to purge snapshot logs Purge Standard Cost History Purge Cost Information Purge Cost Information Purge Standard Cost History Selective LIFO Purge Layers Purge Margin Analysis Run Purge Standard Cost Update History Purge Standard Cost History from SRS Purge Configuration Items Engineering Change Order Purge Program Purge Designator Purge Designator Purge Designator Purge Capacity Bill of Resources Purge Capacity Bill of Resources Purge Simulation Sets Purge Capacity Bill of Resources WIP Purge Purge Configurator Tables Purge Demand Interface Data Concurrent Program for Flow Schedule Purge Purge Kanban Pull Sequences Purge Fact Data DP Purge Program Purge Designator Planning Data Collection .
Product Oracle Payroll Oracle Payroll Shortname PYUGEN PYUGEN Description Purge Preparation Phase Purge Deletion Phase INT:Generic Interface: Archive/Purge/Restore Dunning Letters: Purge Temporary Data Purge Budget Revisions Purge Worksheet Purge Budget Revisions Purge Data Extract Purge Scheduling Interface Data Degree Audit Purge Requests Report Purge Mass External Retirements Purge Mass External Transfers Purge asset hierarchy batches marked as discarded Oracle International Public Sector Finance IGIGIAPR Oracle International Public Sector Finance IGIRDPTD Oracle Public Sector Budgeting Oracle Public Sector Budgeting Oracle Public Sector Budgeting Oracle Public Sector Budgeting Oracle Student Systems Oracle Student Systems CRL Financials Assets CRL Financials Assets CRL Financials Assets PSBBRPUR PSBWCPUR PSBBRPUR PSBSTPDE IGSPSJ06 IGSDAS01 FACXTRES FACTPURG FACHRPRG Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management Page 41 .
Purge Staging Tables Purge Local ID Tables and Complete Refresh for Legacy Instances Purge Designator This program purges records from the Collaborative Purge Concurrent Processing setup data for cloning Use this program to summarize and purge the request run statistics Purge Obsolete ECX Data Purge Obsolete Generic File Manager Data Purges Logs for expired Transactions and Closed System Alerts data Purge FND_STATS History Records Purge Designator Purge Obsolete Workflow Runtime Data Purge Workflow Provisioning Requests Purge Web Service Audit Data Purges old diagnostic and logged messages related information Purges the debug rule executions and deletes the corresponding log/out Purges Concurrent requests and/or Concurrent Manager data and log/output Purges all Signon Audit information ( FND_LOGINS. Product Advanced Benefits Advanced Pricing Advanced Pricing Advanced Pricing Advanced Supply Chain Planning Advanced Supply Chain Planning Advanced Supply Chain Planning Advanced Supply Chain Planning Advanced Supply Chain Planning Advanced Supply Chain Planning Advanced Supply Chain Planning Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Application Object Library Applications BIS Applications DBA Assets Assets Assets Bills of Material Bills of Material Bills of Material Bills of Material Bills of Material Bills of Material Shortname BENPDCPG QPXARCVB QPXDLDBB QPXPURGB MSCATPPURG MSCCONF MSCDELDC MSCPDCP MSCPLID MSCPRG MSCXPHS FNDCPCLN FNDCPCRS FNDECXPR FNDGFMPR FNDLGPRG FNDPGHST FNDSCETS FNDWFPR FNDWFPRVPR OAMSOAPPUREXE OAM_BE_PURGE Purge Debug Rule Executions Purge Requests and/or Managers Purge signon audit data WFPURGE aflobbld BIS_RSG_PURGE_HISTORY_TABLE ADXBBBMS FAPURG FARXPRG FAS826 BOMCPCFG CSTCMDEL CSTCSPCT CSTCSPCU CSTISPCH CTOPURGE Description Purge Plan Design Copy Process Archive Entity Purge Pricing Engine Requests Purge Pricing Entity Concurrent program purges temporary data generated for each ATP Create Component Architecture Flexfields Purge ODS Data of Collections Planning Data Collection . Purging and Information Lifecycle Management Page 42 .APPENDIX B: EXAMPLES ARCHIVE PURGE PROGRAMS (ORACLE E-BUSINESS SUITE RELEASE 12) The following are examples of some of the Archive and Purge programs available in Oracle E-Business Suite Release 12. Not all of the programs listed may be available for customers to be run standalone. Please refer to the product user documentation for specific instructions regarding availability and usage for each program. FND_LOGIN_RESPONSIBITIES Purge Workflow Transaction Table Purge orphaned help documents and rebuild the interMedia search index Purge Request Set Generator History Tables Purge Capacity Bill of Resources Purge accounting tables Purge RX Interface Data Mass Additions Purge Report Purge Configuration Items Purge Margin Analysis Run Purge Cost Information Purge Standard Cost Update History Purge Standard Cost History from SRS Purge Configuration Items Reducing your E-Business Suite Data Footprint using Archiving.
Assets Capital Resource Logistics .Archive/Purge Purge All Import Tables Completely Purge All Import Tables Records Older Than The Number Of Days Purge All Import Tables Records Less Than Or Equal To The RunID Purge Configurator Tables Commitment Budgetary Control Archive / Purge Program Commitment Budgetary Control Archive Purge Report Contract Commitment Archive / Purge Program Contract Commitment Archive Purge Report Concurrent Program to purge clause open interface table Purge old Contracts QA error messages Child Concurrent Task Purge Program Standalone Task Purge Program JTO: Purge Fulfillment Requests JTO: Purge Fulfillment Request (Worker) Interaction History Data Purge Archive demand plan Purge Fact Data Purge Interface Tables Depot repair generic messages purge Tax Simulator Purge Program Purge Email Center Workflow Process the archive/purge requests in Email Center Purge Email Center Workflow Purge Next Gen Email Center Workflow Engineering Change Order Purge Program Purge Event Log Process to show the Treasury Symbols that can be Purged or Purged. Financials Intelligence Purge Budget and Forecast Program Purge Company and Cost Center WebADI Security from Interface Table Concurrent Program for Flow Schedule Purge Purge Kanban Pull Sequences Purge Consolidation Audit Archive and Purge Program Archive and Purge Child Program Purge transaction history Delete ALL archived rules Unload from ALL TP to archived rules Reducing your E-Business Suite Data Footprint using Archiving.Assets Capital Resource Logistics .Product Bills of Material Capacity Capacity Capacity Capital Resource Logistics .Assets Cash Management Cash Management Configurator Configurator Configurator Configurator Contract Commitment Contract Commitment Contract Commitment Contract Commitment Contracts Core Contracts Core CRM Foundation CRM Foundation CRM Foundation CRM Foundation CRM Foundation Demand Planning Demand Planning Demand Planning Depot Repair E-Business Tax Email Center Email Center Email Center Email Center Engineering Enterprise Asset Management Federal Financials Federal Financials Financial Intelligence Financial Intelligence Flow Manufacturing Flow Manufacturing General Ledger General Ledger General Ledger General Ledger Global Accounting Engine Global Accounting Engine Shortname LIFO Purge CRPPSPRS CRPPSPSS CYRRCP FACHRPRG FACTPURG FACXTRES CEFPURGE CEPURGE CZIPURGE CZIPURGETD CZIPURGETRI CZPURGE IGCBAPRB IGCBAPRR IGCCAPRB IGCCAPRR OKCPURARTINF OKCQAPUR CACTKCHPUR CACTKPUR JTF_FM_PURGE_REQUESTS JTF_FM_PURGE_REQ_WKR JTF_IH_PURGE MSDARCHIVE MSDPFCT MSDPUR CSDEMSGS ZXSIMPUR IEMADMWP IEMMDTAP IEMMDTWP IEMNGNWP ENCECP EAMPEVLG FVPGDTSR FVXPURTS FII_BUDGET_FORECAST_PURGE FII_CCC_SEC_PURGE FLMCPPG FLMRFPKB GLCPCA GLPURGE GLPURGEC Upgrade Encumbrance balances AXXDWDER AXXDWULD Description Selective LIFO Purge Layers Purge Capacity Bill of Resources Purge Simulation Sets Purge processed transactions in the AutoInvoice Interface tables Purge asset hierarchy batches marked as discarded Purge Mass External Transfers Purge Mass External Retirements Purge Cash Forecasts Program . Purge Cancelled Treasury Symbols to reuse. Purging and Information Lifecycle Management Page 43 .
TCA purge only Process to Purge Old Applicant Tracking Data in iRecruitment Process to Purge Old Data in iRecruitment Purges all records related to a BEE batch Purge Migrated Person DFF Data Purge Daily Sick and Recovery Table Install Base Party Accounts Transaction History purge Install Base Instance Assets Transaction History purge Install Base Extended attributes Transaction History purge Install Base Item Instances Transaction History purge Install Base Operating units Transaction History purge Install Base Pricing attributes Transaction History purge Install Base Instance Party Transaction History purge Install Base Instance Relationships Transaction History purge Install Base Systems Transaction History purge Install Base Transaction History purge Install Base Version labels Transaction History purge Purge Interactions tables Purge ABC information Purge cycle count information Purge replenishment counts Purge transaction history Copy Inventory Organization Report Data Purge Inventory positions purge all Inventory positions purge by data set. Data Pump Purge slave process for multi-threading.Program migrated to Trade Management Claims Import Purge routine. user. creation date High Volume Transactions Purge Copy Inventory Organization Interface Data Purge Program of Move Order Purge Transaction Purge Worker Transaction Purge Purge cycle count entries open interface in batch mode Purge physical inventory information Archive History Report Archive Encumbrance Lines Archive Distributions History Purge Lease Rate Factor Interface Table Purge Residual Values Interface Table OKL_PURGE_PARALLEL_PROCESSE Purge Parallel Processes Table S OKL_PURGE_STRM_INTF AMSCHBPURG AMSIMPPURGE AMSPEWKR Purge streams interface tables Purge processed chargeback record . Purging and Information Lifecycle Management Page 44 .Program migrated to Trade Management (OZF) AMS: Purge Target Group and List Entries (Worker) Reducing your E-Business Suite Data Footprint using Archiving.Product Global Accounting Engine Global Accounting Engine Human Resources Human Resources Human Resources Human Resources Human Resources Human Resources Human Resources Human Resources Install Base Install Base Install Base Install Base Install Base Install Base Install Base Install Base Install Base Install Base Install Base Interaction Center Intelligence Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Inventory Labor Distribution Labor Distribution Labor Distribution Lease Management Lease Management Lease Management Lease Management Marketing Marketing Marketing Shortname AXXPGLIS AXXPGSLE DATAPUMP_PURGE DATAPUMP_PURGE_SLAVE HRTCAUNMP IRC_APL_TRACK_PURGE IRC_PURGE_OLD_DATA PAYLINK PERDFFPERGE PERNLPAC CSIACTARCH CSIASTARCH CSIEXTARCH CSIINSARCH CSIOUARCH CSIPRIARCH CSIPTYARCH CSIRELARCH CSISYSARCH CSITHPUR CSIVERARCH BIXPURIN INCAAP INCACP INCRPG INCTPG INVCORPP INVGIPPG INVGIPPG INVHVTPG INVISCORP INVMOPG INVTPGWB INVTXPURG MTL_CCEOI_PURGE Physical Inventory Purge PSPARREP PSPENARC PSPLDARC OKLLRFP OKLRVP Description Purge Audit Report Subledger Archive and Purge by fiscal year accounting period Data Pump tables purge program. Unmerge contacts and other person types.
Worker Order Purge Payables Open Interface Purge AP/PO Purge Abort Routine AP/PO Purge Confirmation Routine AP/PO Purge Deletion Routine AP/PO Purge Initiation (Selection) Routine AP/PO Purge Summarization Routine Purge Report Listings Program to purge the tax table data. Order Purge Selection Create Purge Set Quote Purge selection Order Purge Selection Purge of OM Processing Messages Purge Imported Credit Exposure program Purge procedure for the views used by Order Import and EDI/XML message Purge Secured Payment Data Purge Secured Payment Data .Product Marketing Marketing Marketing Master Scheduling/MRP Operations Intelligence Oracle iProcurement Oracle Web Analytics Order Entry Order Management Order Management Order Management Order Management Order Management Order Management Order Management Order Management Order Management Payables Payables Payables Payables Payables Payables Payables Payroll Payroll Process Manufacturing Inventory Process Manufacturing Inventory Process Manufacturing Inventory Process Manufacturing Product Development Process Manufacturing Systems Projects Projects Projects Projects Property Manager Property Manager Provisioning Public Sector Budgeting Public Sector Budgeting Public Sector Budgeting Public Sector Financials Public Sector Financials International Public Sector Financials International Public Sector Financials International Purchasing Purchasing Shortname AMSPILTC AMSPTGPC AMSWMHPE MRCPRG OPI_PMI_INV_DAILY_SUM_PURGE ICXPCIIP IBW_DATA_PURGE Order Purge Selection GENPSET GENPSETQTEWHERE GENPSETWHERE OEMPRG OEXCEPRG OEXOIPCP ONTIBYCN_MGR ONTIBYCN_WKR ORDPUR APXIIPRG APXP7ABT APXP7CFM APXP7DEL APXP7SEL APXP7SUM APXPGLIS PYNOTTPU PYSETTPU GMIPEBAL GMIPEBAL OPMTMOPG GMDRSPVL SYPRGENG PACCINTP PAXARPPR PAXARPVD UNASSIGNED_FI_PURGE PNSOIPUR PNVPURGE XDP_PURGE PSBBRPUR PSBSTPDE PSBWCPUR BCPURGE IGIIMPPI IGIIMPPU IGIRDPTD POXCDXPG POXPOIPR Description Purge Imported List AMS: Purge Target Group and List Entries Concurrent Program to purge monitor history Purge Designator Purge OPM Inventory Daily Summary Table Purge Catalog interMedia Index This program purges data from the Web Analytics transaction schema. To Purge the data available in Tax Table for given Dates OPM Purge empty balance Oracle Process Manufacturing Inventory : GMI Purge Empty Balances Purge OPM Txns and Move Order Lines GMD QM Spec and Validity Rule Mass Search and Replacement Archive and Purge Process Purge Capitalized Interest Transactions Audit Purge Project Data PRC: Validate Purge Batches Process to Archive/Purge Unassigned Forecast items Variable Rent Gateway Purge Process Purge Location and Space Assignment Interface Tables Program to purge obsolete application data Purge Budget Revisions Purge Data Extract Purge Worksheet Budgetary Control History Purge Inflation Accounting : Purge Inflation Accounting Data Inflation Accounting : Purge Implementation Data Dunning Letters: Purge Temporary Data Catalog Data Purge (Obsolete) Purge Purchasing Open Interface Processed Data Program Page 45 Reducing your E-Business Suite Data Footprint using Archiving. Purging and Information Lifecycle Management .
Product Purchasing Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Receivables Release Management Release Management Release Management Integration Kit (Obsolete) Sales Foundation Sales Foundation Sales Foundation Sales Intelligence Sales Online Sales Online Service Service Service Service Contracts Service Contracts Service Contracts Service Contracts Service Contracts Shipping Execution Sourcing Student System Student System Student System Student System Student System Student System Subledger Accounting Supply Chain Intelligence Shortname POXSSPG ARARCALL ARARCDNL ARARCDRP ARARCHID ARARCHIH ARARCONT ARARCONT ARARCONT ARARCONT ARARCPUR ARARCSEL ARARCSRP ARGCGP ARHIDENTPUR ARHLPURB ARPURGE ARXPAR AutoInvoice Purge Program RAXTRX RLMPS RLMPSRP RLAPURGE AMLPRGIMP ASTPRG ASXPRGLD BIL_BI_PURGE_OBJ ASFDLST ASFFRVH CSSRPGP CSSRPGW CS_KB_SESSION_CLEANUP OKSCCPURGE OKSUPDCC_HDRH_SUBREQ OKSUPDCC_HDRRULES_SUBREQ OKSUPDCC_HDR_SUBREQ OKSUPDCC_LINE_SUBREQ WSHPURGE PurgeInterfaceErrorsCp IGSDAJ03 IGSPSJ06 IGSPSJ13 IGSSV03 IGSSV04 IGSUCJ39 XLAAPPURGE ISC_EDW_BACKLOGS_F_PURGE Description Purge System Saved Requisition Call New Archive and Purge Archive to File Archive Detail Report Archive Detail Archive Header Archive Preview Archive Restart Archive and Purge Purge Purge Module Archive Selection Archive Summary Report Purge Designator TCA .Identify Purge Parties TCA Import Process to Purge a Batch New Archive and Purge Purge Capacity Bill of Resources Purge processed transactions in the AutoInvoice Interface tables Purge Cost Information Release Management Purge Schedule Release Management Purge Schedule Exception Report Purge Demand Interface Data Purge Leads Import Interface Purge AS_ACCESSES_ALL and AS_TERRITORY_ACCESSES tables Purge Unqualified Sales Leads Purge BIL Object Data Purge Deleted Lists Periodically Purge ASF_RECORD_VIEW_HISTORY Service Request Data Purge Concurrent Program Service Request Data Purge Worker Thread Concurrent Program Program to purge temporary data stored in Knowledge Management Purge Credit Card Information Purge Credit Card in Header History Purge Credit card in Header rules Purge Line Credit Card Purge Line Credit Card Program to purge shipping entities Purge expired interface errors Degree Audit Purge Requests Purge Scheduling Interface Data Purge Logically Deleted Records SEVIS Purge Active Exchange Visitor Information SEVIS Purge Active Non Immigrant Information Purge Completed UCAS data Purge old Transaction Objects Diagnostics related information Purges the Backlog Fact given a date range or a period from today. Purging and Information Lifecycle Management Page 46 . Reducing your E-Business Suite Data Footprint using Archiving.
Purging and Information Lifecycle Management Page 47 . Sales Leads Purge Record from import interface table Purge processed resale order records Claims Import Purge routine Program to Purge Baseline Sales and Promotional Lift Factor Data Launch Purge Transportation Plan Purge WMS History Tables Purge WMS History tables Archive WMS Tasks Archive WMS Tasks Worker Un-Archive WMS Tasks Un-Archive WMS Tasks Worker WMS_LMS_PURGE_SETUP_HISTOR Program to Purge Labor Setup History Records Y WMS_LMS_PURGE_TXNS WIPPURGE WIPPURGE Program to purge Labor Tracked Transactions Purge Lot Based Jobs WIP Purge Reducing your E-Business Suite Data Footprint using Archiving.Product Supply Chain Localizations Telephony Manager Telephony Manager TeleSales Trade Management Trade Management Trade Management Transportation Planning Warehouse Management Warehouse Management Warehouse Management Warehouse Management Warehouse Management Warehouse Management Warehouse Management Warehouse Management Work in Process Work in Process Shortname JMFGTIPG CCT_CLONE_CLEAN_EX CCT_TRANS_DATA_CLS_EX AST_IMPORT_PURGE OZFCHBPURG OZFIMPPURGE OZF_TP_PURGE_BASELINE_LIFT MSTPRGPL PURGE_WMS PURGE_WMS WMSTARCM WMSTARCW WMSTUARM WMSTUARW Description Golden Tax Invoice Purge Adaptor Invoices Purge Interaction Center related telephony configurations after cloning Purge Advanced Inbound related transactional data after cloning.
Purging and Information Lifecycle Management Page 48 .Reducing your E-Business Suite Data Footprint using Archiving.
Nancy Lan.A. for any purpose.Reducing Your E-Business Suite Data Footprint using Archiving.506. This document may not be reproduced or transmitted in any form or by any means.650. without our prior written permission. This document is not warranted to be error-free. CA 94065 U. .7200 oracle. Oracle. and Information Lifecycle Management November 2008 Author: Mohsin Sameen Contributing Authors: Andy Tremayne Reviewers: Dimas Chabne. Olcay Sarioglu Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. Purging.S. Worldwide Inquiries: Phone: +1. including implied warranties and conditions of merchantability or fitness for a particular purpose. nor subject to any other warranties or conditions. electronic or mechanical. Other names may be trademarks of their respective owners. This document is provided for information purposes only and the contents hereof are subject to change without notice. All rights reserved.650.506.7000 Fax: +1. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. whether expressed orally or implied in law. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.com Copyright © 2008.