Search Results ax_sle_headers_arch




Overview
Explore in AI Chat

Overview

The AX_SLE_HEADERS_ARCH table is a critical archiving object within Oracle E-Business Suite's Global Accounting Engine (AX) module. It functions as a historical repository for accounting header records that have been purged from the primary transactional table, AX_SLE_HEADERS. Its primary role is to support data lifecycle management by preserving a complete audit trail of accounting entries, enabling historical reporting and compliance, while allowing for the controlled cleanup of the main transactional tables to maintain system performance. This table is integral to the Subledger Accounting (SLA) architecture, specifically storing archived details of Subledger Entry (SLE) headers.

Key Information Stored

The table stores purged header-level information for accounting journal entries. While the specific column list is not detailed in the provided metadata, the defined primary and foreign key relationships reveal its core structure. Each archived record is uniquely identified by the composite primary key consisting of JOURNAL_SEQUENCE_ID and SLE_HEADER_ID. The JOURNAL_SEQUENCE_ID groups related accounting entries, while the SLE_HEADER_ID is the unique identifier for the specific header. A critical foreign key, EVENT_ID, links each archived header to its originating accounting event in the AX_EVENTS table, preserving the transactional context. The table likely contains other columns mirroring AX_SLE_HEADERS, such as accounting date, ledger ID, and status, which describe the purged accounting entry.

Common Use Cases and Queries

The primary use case is historical inquiry and audit reporting on accounting data that is no longer active in the primary tables. This is essential for financial audits, period comparisons, and troubleshooting historical transactions. Common queries involve joining this archive table with its related lines archive (AX_SLE_LINES_ARCH) to reconstruct complete journal entries. A typical reporting pattern would be to retrieve archived entries for a specific event or date range.

  • Sample Query for Archived Journal Details:
    SELECT arch_hdr.*, arch_ln.*
    FROM ax_sle_headers_arch arch_hdr,
    ax_sle_lines_arch arch_ln
    WHERE arch_hdr.journal_sequence_id = arch_ln.journal_sequence_id
    AND arch_hdr.sle_header_id = arch_ln.sle_header_id
    AND arch_hdr.event_id = :p_event_id;
  • Another common scenario is tracing the lifecycle of a transaction from its original event through to its archived accounting records, which involves querying AX_EVENTS, AX_SLE_HEADERS, and AX_SLE_HEADERS_ARCH.

Related Objects

The AX_SLE_HEADERS_ARCH table has defined relationships with other core AX module tables, forming a key part of the archived data model.

  • Referenced Foreign Key (Parent Table): The table references AX_EVENTS via the EVENT_ID column. This maintains the link to the original accounting event that generated the subledger entry.
  • Referencing Foreign Key (Child Table): The AX_SLE_LINES_ARCH table references this header archive table. The relationship is defined on the composite key (JOURNAL_SEQUENCE_ID, SLE_HEADER_ID), ensuring that archived detail lines remain correctly associated with their purged headers.
  • Source Table: AX_SLE_HEADERS is the direct source table from which records are purged into AX_SLE_HEADERS_ARCH. They share an identical primary key structure.