Search Results financials_purges




Overview
Explore in AI Chat

Overview

The FINANCIALS_PURGES table is a core data object within the Oracle E-Business Suite Payables (AP) module, specifically designed to support the archival and purging of invoice data. Its primary role is to store the master definition and high-level statistical results for each executed purge process. This table acts as a control and audit mechanism, ensuring that purges are tracked, reproducible, and their impact quantifiable. By maintaining a record of purge criteria—such as cutoff dates and selection parameters—it provides a historical ledger of data management activities critical for compliance and system performance maintenance in both EBS 12.1.1 and 12.2.2 environments.

Key Information Stored

While the provided ETRM metadata does not list specific columns, the description indicates the table stores two primary categories of data. First, it holds the purge selection criteria, which likely includes fields such as PURGE_NAME (the primary key), a purge execution date, a cutoff date for eligible invoices, and parameters defining the scope of the purge (e.g., by operating unit, supplier, or invoice type). Second, it stores purged invoice statistical data, which would encompass summary metrics like the total number of invoices purged, the total monetary value purged, and the count of related records (e.g., payments, distributions) removed. This statistical snapshot is vital for post-purge reporting and reconciliation.

Common Use Cases and Queries

The primary use case is auditing and reviewing historical purge operations. System administrators and functional consultants query this table to generate purge history reports, verify the scope of past data deletions, and plan future purge cycles. A common query pattern involves joining to related history tables to analyze the detailed impact of a specific purge run.

  • Listing All Executed Purges: SELECT purge_name, creation_date FROM financials_purges ORDER BY creation_date DESC;
  • Analyzing Purge Volume: A typical analysis would join FINANCIALS_PURGES to AP_HISTORY_INVOICES_ALL to count the number of invoices removed per purge: SELECT fp.purge_name, COUNT(ahia.invoice_id) FROM financials_purges fp, ap_history_invoices_all ahia WHERE fp.purge_name = ahia.purge_name GROUP BY fp.purge_name;

Related Objects

The FINANCIALS_PURGES table serves as a parent table for several key history and control tables in the Payables purge architecture, as documented by its foreign key relationships. These related objects store the detailed transactional data associated with each master purge record.

  • AP_HISTORY_CHECKS_ALL: References FINANCIALS_PURGES via AP_HISTORY_CHECKS_ALL.PURGE_NAME. This table stores details of payment (check) records that were purged.
  • AP_HISTORY_INVOICES_ALL: References FINANCIALS_PURGES via AP_HISTORY_INVOICES_ALL.PURGE_NAME. This is a critical table containing the detailed records of each purged invoice.
  • AP_PURGE_INVOICE_LIST: References FINANCIALS_PURGES via AP_PURGE_INVOICE_LIST.PURGE_NAME. This table likely holds the pre-purge selection list or staging data used to identify invoices for a specific purge run.

The primary key constraint, FINANCIALS_PURGES_PK on the PURGE_NAME column, enforces uniqueness and is referenced by the foreign keys in the tables listed above, creating a relational model for purge data management.