Search Results ax_sle_headers_arch_u1

Overview

AX.AX_SLE_HEADERS_ARCH is a Subledger Accounting (SLA) archive table in the AX (Subledger Accounting) schema of Oracle E-Business Suite. It stores rows that have been removed from the online AX_SLE_HEADERS table by the Subledger Archive and Purge program, which is a standard Oracle EBS concurrent program executed from the Subledger Accounting responsibility. Because Subledger Accounting creates a journal header for every accounting event generated by a source application, the online header table can grow rapidly in high-volume environments. The archive table preserves that audit history while allowing production tables to be pruned for performance.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. In a Data Vault modeling sense, the table is satellite-leaning, since its structure centers on descriptive and attribute columns (dates, reference fields, transfer flags, and Who columns) that depend on the key relationships defined in the online accounting model. This classification is a heuristic suggestion and is not enforced by EBS.

Key Information Stored

The surrogate primary key, AX_SLE_HEADERS_ARCH_PK, is composed of JOURNAL_SEQUENCE_ID and SLE_HEADER_ID. A separate unique index, AX_SLE_HEADERS_ARCH_U1, provides the principal business-key candidate across SET_OF_BOOKS_ID, JOURNAL_SEQUENCE_ID, and SLE_HEADER_ID, meaning a single journal sequence cannot repeat within a given ledger.

• JOURNAL_SEQUENCE_ID – Journal sequence identifier; part of the primary key and U1 index.
• SLE_HEADER_ID – Value of the journal sequence, combining with the above to uniquely identify the header.
• SET_OF_BOOKS_ID – Ledger (set of books) identifier; the accounting context for the header.
• EVENT_ID – Accounting event identifier that originated the header.
• EFFECTIVE_DATE – Accounting date of the entry.
• PERIOD_NAME and CURRENCY_CODE – Accounting period and transaction currency.
• APPLICATION_ID – Source application that created the event.
• GL_TRANSFER_FLAG, GL_TRANSFER_DATE, GL_TRANSFER_RUN_ID – Track transfer of the journal to the General Ledger.
• GL_CATEGORY and ACCOUNTING_SEQUENCE_ID – Journal category and accounting sequence for GL posting.
• DOC_SEQUENCE_ID and DOC_SEQUENCE_NUMBER – Document sequence assignment for the accounting entry.
• LEGAL_SEQUENCE_ID and LEGAL_SEQUENCE_VALUE – Legal sequence numbering for reporting.
• REFERENCE_1 through REFERENCE_5 and the REFERENCE_NUM/DATE series – Flexible descriptive references carried over from the source subledger.
• Standard and extended Who columns (CREATION_DATE, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID, etc.) support audit and purge tracking.

The documented schema contains 47 columns in total.

Common Use Cases and Queries

The archive table is most often queried for historical investigation, statutory audit support, reconciliation between subledger and GL balances after a purge cycle, and investigation of journal transfer failures. A typical audit query retrieves all archived headers for a ledger and period:

SELECT journal_sequence_id, sle_header_id, effective_date, period_name, gl_transfer_flag, gl_transfer_date FROM ax.ax_sle_headers_arch WHERE set_of_books_id = :ledger_id AND period_name = :period ORDER BY journal_sequence_id;

Transfer failure analysis compares online and archived rows to confirm processing status:

SELECT h.sle_header_id, h.gl_transfer_flag, l.status FROM ax.ax_sle_headers_arch h, ax.ax_sle_lines_arch l WHERE h.journal_sequence_id = l.journal_sequence_id AND h.gl_transfer_date IS NULL;

Because the table is write-once in practice, no DML should target it during normal operation; the Subledger Archive and Purge program controls population. Reports typically drive from AX_SLE_HEADERS_ARCH to AX_SLE_LINES_ARCH to reconstruct complete journal entries.

Related Objects

• AX.AX_SLE_HEADERS – The online source table from which rows are purged and inserted into this archive.
• AX.AX_SLE_LINES_ARCH – Child archive table of journal lines; joins on JOURNAL_SEQUENCE_ID, SET_OF_BOOKS_ID, and SLE_HEADER_ID.
• AX.AX_EVENTS – Accounting events that generated the archived headers; joined via EVENT_ID.
• FND_DOCUMENT_SEQUENCES – Document sequence definitions referenced through DOC_SEQUENCE_ID.
• AX.AX_SLE_LINES – Online counterpart of the archived lines, useful for comparing retained versus archived entries.
• GL_JE_HEADERS / GL_JE_LINES – Target journals in the General Ledger corresponding to transferred archived headers.
• FND_CONCURRENT_REQUESTS – Provides execution history for the Subledger Archive and Purge program referenced by REQUEST_ID.

These relationships make AX_SLE_HEADERS_ARCH a key component of the subledger audit trail in both EBS 12.1.1 and 12.2.2.