Search Results ax_sle_headers




Overview
Explore in AI Chat

Overview

The AX_SLE_HEADERS table is a core data object within the Global Accounting Engine (GAE), a subledger accounting module in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the primary repository for journal entry header information generated by the accounting engine. This table is fundamental to the Subledger Accounting (SLA) architecture, acting as the staging point for detailed accounting entries before they are transferred to the General Ledger (GL). Each record represents a distinct journal entry batch or header, encapsulating the accounting context for one or more detailed lines stored in the related AX_SLE_LINES table.

Key Information Stored

The table's structure is defined by a composite primary key and critical foreign keys that enforce data integrity. The primary key consists of JOURNAL_SEQUENCE_ID and SLE_HEADER_ID, uniquely identifying each journal header. Key columns include EVENT_ID, which links the accounting entry to its originating transaction event in the AX_EVENTS table. The table also stores vital accounting period context through the APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME columns, which reference the GL_PERIOD_STATUSES table to ensure entries are created only in open or future-enterable periods. Other essential data points typically held in this header table include the accounting date, ledger ID, journal entry description, and status flags indicating the entry's processing state within the subledger accounting flow.

Common Use Cases and Queries

This table is central for troubleshooting accounting issues, auditing subledger journal creation, and building custom reports on accounted transactions before summarization and transfer to GL. A common use case involves tracing accounting entries back to their source transactions by joining AX_SLE_HEADERS with AX_EVENTS. Developers and functional consultants often query this table to verify that expected accounting events have been generated. A typical diagnostic SQL pattern is:

  • SELECT sleh.journal_sequence_id, sleh.sle_header_id, sleh.event_id, sleh.period_name, sleh.accounting_date FROM ax_sle_headers sleh WHERE sleh.set_of_books_id = :ledger_id AND sleh.accounting_date BETWEEN :date_from AND :date_to;

Another critical pattern joins the header to its corresponding lines to review full journal entries: SELECT sleh.*, sll.* FROM ax_sle_headers sleh JOIN ax_sle_lines sll ON sleh.journal_sequence_id = sll.journal_sequence_id AND sleh.sle_header_id = sll.sle_header_id WHERE sleh.event_id = :p_event_id;

Related Objects

The AX_SLE_HEADERS table exists within a tightly integrated schema. Its documented relationships, as per the provided ETRM metadata, are as follows:

  • Referenced Foreign Keys (This table references):
    • AX_EVENTS: Joined via AX_SLE_HEADERS.EVENT_ID = AX_EVENTS.EVENT_ID. This links the accounting header to the original business event.
    • GL_PERIOD_STATUSES: Joined via AX_SLE_HEADERS.APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME. This validates the accounting period status.
  • Referencing Foreign Keys (Tables that depend on this table):
    • AX_SLE_LINES: This child table holds the detailed accounting lines. It is joined to AX_SLE_HEADERS via AX_SLE_LINES.JOURNAL_SEQUENCE_ID = AX_SLE_HEADERS.JOURNAL_SEQUENCE_ID and AX_SLE_LINES.SLE_HEADER_ID = AX_SLE_HEADERS.SLE_HEADER_ID.