Search Results journal_sequence_name

Overview

The view AX_SLE_HEADERS_V is a reporting and integration artifact within the Oracle E-Business Suite (EBS) Global Accounting Engine (AX) module. It exposes the header-level records of Subledger Accounting (SLE) entries, presenting the top-level attributes that describe each accounting event entry before its individual distribution lines are considered. In EBS 12.1.1 and 12.2.2, the Global Accounting Engine historically served as the accounting derivation and posting engine, and the SLE header abstraction remains central to how accounting events are grouped, dated, and eventually transferred to the General Ledger.

The view is described in the data model simply as "Entry headers." It joins the core AX_SLE_HEADERS table to two reference tables so that derived descriptive values — the journal sequence name and the currency conversion type name — are surfaced alongside the stored identifiers. Its purpose is to provide a denormalized, query-friendly projection of entry headers for reports, diagnostics, and downstream interfaces without requiring consumers to assemble the joins themselves. As documented, the object is not implemented in the database referenced by the excerpt, meaning the view text is cataloged but no live instance existed in that environment at capture time.

Underlying Base Objects

The documented view text defines AX_SLE_HEADERS_V over three objects through an explicit join:

• AX_SLE_HEADERS H — the primary entry-header table supplying all stored accounting attributes.
• FND_DOCUMENT_SEQUENCES D — joined on H.JOURNAL_SEQUENCE_ID = D.DOC_SEQUENCE_ID to resolve the JOURNAL_SEQUENCE_NAME.
• GL_DAILY_CONVERSION_TYPES C — outer-joined (denoted by the (+) operator) on H.CURRENCY_CONVERSION_TYPE = C.CONVERSION_TYPE to resolve CURRENCY_USER_CONVERSION_TYPE.

The inner join to FND_DOCUMENT_SEQUENCES requires a matching document sequence for each header, while the outer join to the conversion types permits headers whose conversion type is not maintained in the daily conversion types reference. The view exposes H.ROWID as ROW_ID, enabling row-level identification of the underlying header record. The documented ETRM metadata lists no referenced base objects; the object names above are derived from the published view text.

Key Columns

The columns fall into several functional groups:

• Identity and keys: ROW_ID, SLE_HEADER_ID, APPLICATION_ID, SET_OF_BOOKS_ID, EVENT_ID, ORG_ID.
• Sequencing: JOURNAL_SEQUENCE_ID and JOURNAL_SEQUENCE_NAME, LEGAL_SEQUENCE_ID and LEGAL_SEQUENCE_VALUE, DOC_SEQUENCE_ID and DOC_SEQUENCE_NUMBER.
• Accounting context: EFFECTIVE_DATE, PERIOD_NAME, TRANSACTION_DATE, DESCRIPTION.
• Currency: CURRENCY_CODE, CURRENCY_CONVERSION_DATE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_USER_CONVERSION_TYPE (the descriptive type name sourced from GL_DAILY_CONVERSION_TYPES).
• References: REFERENCE_1 through REFERENCE_5, REFERENCE_NUM1 through REFERENCE_NUM5, and REFERENCE_DATE1 through REFERENCE_DATE5.
• GL transfer state: GL_TRANSFER_FLAG, GL_TRANSFER_DATE, GL_TRANSFER_RUN_ID.
• Audit/concurrency: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

REFERENCE_1 is the commonly queried user reference column, while the GL_TRANSFER_* columns allow rapid assessment of whether a header has already been pushed to the ledger.

Common Use Cases and Queries

Typical scenarios include reconciling subledger entries to GL, verifying currency conversion application, and reporting on unposted headers. The GL transfer flag supports exception reporting for entries that failed to post.

A simple listing of pending transfers for a given ledger and period:

• SELECT SLE_HEADER_ID, PERIOD_NAME, EFFECTIVE_DATE, CURRENCY_CODE, CURRENCY_CONVERSION_RATE, GL_TRANSFER_FLAG FROM AX_SLE_HEADERS_V WHERE SET_OF_BOOKS_ID = :p_sob AND PERIOD_NAME = :p_period AND GL_TRANSFER_FLAG = 'N';

A currency-focused query joining descriptive conversion information:

• SELECT SLE_HEADER_ID, CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_USER_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE FROM AX_SLE_HEADERS_V WHERE CURRENCY_CODE <> 'USD';

Reference lookups by user-defined identifiers for audit purposes:

• SELECT SLE_HEADER_ID, REFERENCE_1, REFERENCE_2, TRANSACTION_DATE FROM AX_SLE_HEADERS_V WHERE REFERENCE_1 = :p_reference;

Because the view carries audit and program columns, it also supports tracing which concurrent program (PROGRAM_ID) and request (REQUEST_ID) produced each header, a frequent requirement during reconciliation investigations.