Results for “ax_sle_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AX_SLE_HEADERS is a table in the AX (Global Accounting Engine) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores journal entry header information generated by the Subledger Accounting (SLE) engine, representing one accounting event header per journal entry created from subledger transactions. Each row corresponds to a single journal entry, identified by the combination of JOURNAL_SEQUENCE_ID and SLE_HEADER_ID, which form the primary key AX_SLE_HEADERS_PK.

Under the heuristic Data Vault classification mined from the foreign key structure, AX_SLE_HEADERS is characterized as satellite-leaning. In Data Vault modeling terms, this suggests the table functions primarily as a descriptive satellite attached to a business hub (the underlying accounting event), carrying contextual attributes such as currency, period, references, and dates. This classification should be treated as a modeling suggestion rather than a strict architectural constraint, since the table also carries references that behave link-like (EVENT_ID pointing to AX_EVENTS, DOC_SEQUENCE_ID pointing to FND_DOCUMENT_SEQUENCES).

Key Information Stored

The table contains 47 documented columns. The most operationally significant are:

• JOURNAL_SEQUENCE_ID and SLE_HEADER_ID — the composite surrogate primary key, uniquely identifying each journal header row.
• SET_OF_BOOKS_ID, JOURNAL_SEQUENCE_ID, and SLE_HEADER_ID — the business-key candidate exposed by unique index AX_SLE_HEADERS_U1, scoping a journal to a ledger and journal sequence.
• EVENT_ID — foreign key to AX_EVENTS, linking the header to its originating accounting event.
• APPLICATION_ID and PERIOD_NAME — participate in the foreign key relationship to GL_PERIOD_STATUSES, defining the accounting period context.
• DOC_SEQUENCE_ID and DOC_SEQUENCE_NUMBER — link to FND_DOCUMENT_SEQUENCES, supporting document numbering.
• CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, and CURRENCY_CONVERSION_TYPE — capture the currency and conversion basis for the journal.
• EFFECTIVE_DATE, TRANSACTION_DATE, and PERIOD_NAME — provide temporal anchoring for accounting and reporting.
• REFERENCE_1..5 and REFERENCE_NUM1..5 — flexible free-form reference attributes widely used for subledger-specific identity and cross-referencing.
• GL_TRANSFER_FLAG, GL_TRANSFER_DATE, and GL_TRANSFER_RUN_ID — track whether and when the journal was transferred to General Ledger, and by which run.
• GL_CATEGORY and ACCOUNTING_SEQUENCE_ID — associate the header with its GL journal category and accounting sequence context.
• LEGAL_SEQUENCE_ID and LEGAL_SEQUENCE_VALUE — support legal sequencing requirements.
• ORG_ID — multi-org operating unit context.
• DESCRIPTION — free-text journal description.

Common Use Cases and Queries

AX_SLE_HEADERS is typically queried to trace subledger accounting output back to GL transfer activity, to reconcile journals by period and ledger, and to audit currency conversion behavior. Common patterns include joining to AX_SLE_LINES for the debit/credit detail, filtering on GL_TRANSFER_FLAG to isolate journals pending transfer, and grouping by PERIOD_NAME for period-close reporting.

• Journal header detail: SELECT h.SLE_HEADER_ID, h.JOURNAL_SEQUENCE_ID, h.PERIOD_NAME, h.CURRENCY_CODE, h.GL_TRANSFER_FLAG FROM AX.AX_SLE_HEADERS h WHERE h.SET_OF_BOOKS_ID = :ledger AND h.PERIOD_NAME = :period
• Header-to-line drill: join AX_SLE_HEADERS h to AX_SLE_LINES l ON l.JOURNAL_SEQUENCE_ID = h.JOURNAL_SEQUENCE_ID AND l.SLE_HEADER_ID = h.SLE_HEADER_ID
• Event traceability: join to AX_EVENTS e ON e.EVENT_ID = h.EVENT_ID to inspect the source accounting event.
• Transfer reconciliation: aggregate rows where GL_TRANSFER_FLAG = 'N' grouped by GL_TRANSFER_RUN_ID or SET_OF_BOOKS_ID.

Related Objects

• AX_SLE_LINES — child table; joined on JOURNAL_SEQUENCE_ID and SLE_HEADER_ID, holding the journal line details.
• AX_EVENTS — parent event source; joined on EVENT_ID.
• GL_PERIOD_STATUSES — period validation; joined on APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME.
• FND_DOCUMENT_SEQUENCES — document numbering; joined on DOC_SEQUENCE_ID.
• GL_JE_HEADERS / GL_JE_LINES — the downstream General Ledger journal headers and lines produced once GL_TRANSFER_FLAG is set.