Search Results sle_header_id




Overview
Explore in AI Chat

Overview

The AX_SLE_LINES_ARCH table is a critical archival object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Global Accounting Engine (AX) module. It functions as a historical repository for accounting journal line entries that have been purged from the primary transactional table, AX_SLE_LINES. Its primary role is to ensure data integrity and auditability by preserving a complete record of all accounting entries, even after they are removed from the active tables for performance or data management purposes. This table is essential for maintaining a full audit trail and for executing historical financial reporting and compliance activities.

Key Information Stored

The table stores archived copies of Subledger Accounting (SLA) journal lines. Its structure is defined by a composite primary key, which uniquely identifies each archived line entry. The key columns are JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, and SLE_LINE_NUM. The SLE_HEADER_ID is a particularly crucial foreign key column that links each archived line to its corresponding journal header record in the AX_SLE_HEADERS_ARCH table. While the specific detail columns are not enumerated in the provided metadata, based on its purpose as an archive of AX_SLE_LINES, it would typically hold all original line-level accounting data such as accounted amounts, currency codes, accounting date, ledger ID, and the associated code combination ID (CCID) for the general ledger account.

Common Use Cases and Queries

The primary use case for this table is historical inquiry and forensic accounting analysis. When users need to investigate or report on accounting entries that are no longer present in the live transactional tables, queries are directed against this archive. A common query pattern involves joining to the archived headers table using SLE_HEADER_ID to reconstruct a complete journal for a specific period, transaction, or ledger. For example, to find all archived journal lines for a specific header, a technical consultant or auditor might use:

  • SELECT * FROM ax.ax_sle_lines_arch WHERE sle_header_id = <header_id_value> ORDER BY sle_line_num;

Another critical use case is data validation and reconciliation, ensuring the completeness of data migrated from the live tables to the archive during purge processes.

Related Objects

This table has direct and integral relationships with other archival objects in the AX schema. Its most significant relationship is defined by a foreign key constraint to the AX_SLE_HEADERS_ARCH table, linking on the composite key of JOURNAL_SEQUENCE_ID and SLE_HEADER_ID. This enforces referential integrity between archived headers and their corresponding lines. The table is the archival counterpart to the active transactional table AX_SLE_LINES. Data is typically moved from AX_SLE_LINES to AX_SLE_LINES_ARCH via a formal purge process, often managed by standard Oracle purge programs or custom archival scripts within the Global Accounting Engine.