Search Results ax_sle_lines_arch




Overview
Explore in AI Chat

Overview

AX_SLE_LINES_ARCH is the archival counterpart of AX_SLE_LINES within the AX - Global Accounting Engine (Global Accounting Engine / Subledger Accounting bridge) of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores accounting distribution rows that have been purged from the live AX_SLE_LINES table. Each row represents a single accounting line — debit, credit, or statistical — generated by the accounting engine for a source subledger transaction, retained here for audit, reconciliation, and historical reporting after the operational data has been removed.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning. This is a modeling suggestion: the table behaves as a descriptive satellite hanging off a header key rather than as an independent hub or a pure associative link. Its grain is defined by the combination of journal sequence, header, and line number, so it answers "what were the distribution lines for this accounting entry" once the header identity is established.

Key Information Stored

The primary key AX_SLE_LINES_ARCH_PK is a composite surrogate composed of JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, and SLE_LINE_NUM. A separate unique index, AX_SLE_LINES_ARCH_U1, provides the business-key candidate: SET_OF_BOOKS_ID, JOURNAL_SEQUENCE_ID, SLE_HEADER_ID, SLE_LINE_NUM. This confirms that accounting identity is scoped by ledger.

Common Use Cases and Queries

Because the table is archival, the most common queries start from a known header or journal identity and retrieve all associated lines, or aggregate amounts for historical audit and reconciliation. A typical pattern filters by header and ledger:

SELECT sle_line_num, code_combination_id, accounted_dr, accounted_cre FROM ax.ax_sle_lines_arch WHERE sle_header_id = :p_header_id AND set_of_books_id = :p_sob_id ORDER BY sle_line_num;

Other recurring scenarios include reconciling purged subledger distributions against GL balances; auditing tax lines via TAX_LINK_ID and TAX_CODE_ID; tracing applied transactions through APPLIED_FROM_DOC_ID / APPLIED_TO_DOC_ID; and reconstructing which lines were posted by checking GL_POSTED_FLAG and GL_POSTED_DATE. Reporting on SOURCE_TABLE and SOURCE_ID supports lineage analysis back to the originating subledger. Because the table can hold many rows per header, queries should always be filtered by SLE_HEADER_ID or JOURNAL_SEQUENCE_ID to use the PK efficiently.

Related Objects

  • AX_SLE_HEADERS_ARCH — parent header archive; joined on JOURNAL_SEQUENCE_ID and SLE_HEADER_ID, matching the documented foreign key from AX_SLE_LINES_ARCH.JOURNAL_SEQUENCE_ID to AX_SLE_HEADERS_ARCH.
  • AX_SLE_LINES — the live source table from which these rows are purged and archived.
  • AX_SLE_HEADERS — the live header table that pairs with the current lines.
  • GL_JE_LINES / GL_JE_HEADERS — General Ledger journal lines and batches produced from posted AX accounting, linked via GL_SL_LINK_ID and GL_TRANSFER_LINE_NUM.
  • GL_CODE_COMBINATIONS — resolves CODE_COMBINATION_ID to accounting flexfield segments.
  • GL_IMPORT_REFERENCES — correlates transferred subledger lines with GL journal entries.
  • FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — resolves PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID for the purge process that moved rows into this archive.