Search Results purge_id

Overview

The AX_PURGE_RUNS table is a core audit and control object within the Global Accounting Engine (AX) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a log or journal table, systematically recording the execution history of the Subledger Archive and Purge process. This process is critical for managing data volume and performance in the financial subledgers by systematically archiving and removing transactional data that is no longer required for day-to-day operations. The table provides a definitive audit trail for each purge execution, enabling administrators to track process initiation, status, parameters, and outcomes, which is essential for compliance, troubleshooting, and process management.

Key Information Stored

The table's primary purpose is to store metadata about each purge run. While the full column list is not detailed in the provided excerpt, the structure is anchored by the PURGE_ID column, which serves as the unique identifier for each execution and is the table's primary key (AX_PURGE_RUNS_PK). Based on its described function, the table typically contains columns such as the purge execution start and end timestamps, the status of the run (e.g., 'COMPLETED', 'ERROR', 'RUNNING'), the name of the concurrent program or job that initiated it, the requesting user, and key parameters used for that specific run (like the ledger, period, or cutoff criteria). This creates a permanent record of who purged what data and when.

Common Use Cases and Queries

The primary use case is auditing and monitoring the archive and purge lifecycle. System administrators and functional consultants query this table to verify process completion, diagnose failed jobs, and analyze purge history. Common SQL patterns include identifying the most recent purge runs for a specific ledger or checking for long-running or failed processes that may require intervention.

• Finding Recent Purge Executions: SELECT purge_id, request_id, status_code, start_date, end_date FROM ax.ax_purge_runs WHERE ledger_id = :ledger_num ORDER BY start_date DESC;
• Auditing Purge History: SELECT COUNT(*), status_code, TRUNC(start_date) FROM ax.ax_purge_runs GROUP BY status_code, TRUNC(start_date) ORDER BY 3 DESC;
• Troubleshooting a Specific Run: Queries using the PURGE_ID as a key to join with related detail or error log tables to investigate the specifics of a problematic job.

Related Objects

As an audit table with a primary key (PURGE_ID), AX_PURGE_RUNS is the parent table in relationships with other AX purge-related objects. Child tables likely exist to store the detailed transactional data selected for purging or archived in each run, and they would reference AX_PURGE_RUNS via a foreign key constraint on the PURGE_ID column. While specific child table names are not listed, they would follow naming conventions like AX_PURGE_RUN_DETAILS or AX_ARCHIVE_DETAILS. This relationship allows tracing every archived or purged transaction back to the specific master execution record that caused its removal, ensuring full data lineage and auditability.