Search Results ax_sle_lines_arch_n1




Overview

AX.AX_SLE_LINES_ARCH is the archive counterpart of AX_SLE_LINES within the Oracle E-Business Suite subledger accounting (SLA) schema. It preserves the accounting event lines that have been removed from the live AX_SLE_LINES table by the Subledger Archive and Purge program. As part of the AX (Subledger Accounting) schema, it supports the Subledger Accounting architecture introduced in Oracle EBS 12.1.1 and carried forward through 12.2.2, where every transaction creates accounting events and journal entries that are eventually transferred to General Ledger.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and holds 127 documented columns in the 12.2.2 physical schema. Its heuristic Data Vault classification is satellite-leaning: the archive row represents descriptive, attributable context (amounts, flags, references, audit columns) attached to a business key rather than acting as an independent hub or a pure link. Modelers should treat AX_SLE_LINES_ARCH as a satellite of the accounting-line entity, anchored by the header/journal business keys inherited from AX_SLE_HEADERS_ARCH.

Key Information Stored

The documented primary key AX_SLE_LINES_ARCH_PK is composed of JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, and SLE_LINE_NUM. These three columns identify each archived accounting line: the journal sequence identifier, the header sequence value, and the entry line number. A separate unique index, AX_SLE_LINES_ARCH_U1 (SET_OF_BOOKS_ID, JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, SLE_LINE_NUM), serves as the business-key candidate, adding the ledger (SET_OF_BOOKS_ID) to the identification path — this is the index most commonly referenced when validating archive completeness.

The most significant data columns are:

Common Use Cases and Queries

Typical uses include audit reconstruction of purged accounting entries, reconciliation between SLA and GL after archiving, and historical reporting where the live AX_SLE_LINES table no longer holds the data. A representative verification query:

  • SELECT h.JOURNAL_SEQUENCE_ID, l.SLE_HEADER_ID, l.SLE_LINE_NUM, l.CODE_COMBINATION_ID, l.ACCOUNTED_DR, l.ACCOUNTED_CR FROM AX_SLE_LINES_ARCH l JOIN AX_SLE_HEADERS_ARCH h ON l.SET_OF_BOOKS_ID = h.SET_OF_BOOKS_ID AND l.JOURNAL_SEQUENCE_ID = h.JOURNAL_SEQUENCE_ID AND l.SLE_HEADER_ID = h.SLE_HEADER_ID WHERE l.SET_OF_BOOKS_ID = :ledger_id;
  • Aggregation of GL_POSTED_FLAG to confirm archival completeness by ledger and period.
  • Analysis of CODE_COMBINATION_ID, THIRD_PARTY_ID, and SUB_ID for historical subledger balances.
  • Correlating SOURCE_ID / SOURCE_TABLE back to originating subledger tables.

Related Objects

  • AX.AX_SLE_HEADERS_ARCH — parent header archive; joined on SET_OF_BOOKS_ID, JOURNAL_SEQUENCE_ID, SLE_HEADER_ID (foreign key relationship documented).
  • AX.AX_SLE_LINES — the live source table from which rows are purged.
  • AX.AX_SLE_HEADERS — live header table corresponding to the archived headers.
  • GL.GL_JE_LINES / GL_JE_HEADERS — General Ledger journal lines that receive transferred SLA entries via GL_POSTED_FLAG and GL_SL_LINK_ID.
  • AX.AX_SLE_LINES_ARCH_U1 and AX_SLE_LINES_ARCH_N1 — the unique and non-unique indexes supporting the table.
  • The Subledger Archive and Purge concurrent program, which populates this table and is traceable through REQUEST_ID and PROGRAM_ID.