Search Results okl_ae_headers_v

Overview

OKL_AE_HEADERS_V is a reporting and integration view in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available across releases 12.1.1 and 12.2.2. It exposes accounting entry header records generated by the OKL subledger accounting engine, which produces journal entries for lease and finance contracts. Each row in the view represents a logical accounting event header that groups the individual accounting entry lines belonging to a single event, category, and accounting period.

The view is most commonly queried during reconciliation, period-close, and diagnostic activities. Users searching for the column post_to_gl_flag are typically investigating whether a given accounting entry header has been marked for transfer to the General Ledger, or troubleshooting why entries did not appear in GL. The view also surfaces related status columns such as GL_TRANSFER_FLAG, GL_TRANSFER_ERROR_CODE, and ACCOUNTING_ERROR_CODE, making it the primary read-only interface for reviewing the lifecycle of OKL accounting headers without touching the base table directly.

Underlying Base Objects

The view is defined over the single base table OKL_AE_HEADERS, aliased AEHB in the view text. All columns are drawn directly from that table, including the pseudo-column ROWID, which is exposed as ROW_ID. No joins or aggregations are present, so the view is a projected, security-filtered representation of the base table rather than a composite object.

The distinguishing characteristic is its WHERE clause, which enforces multi-organization security using the Client Info context. The predicate compares NVL(ORG_ID, ...) against a value extracted from USERENV('CLIENT_INFO'), effectively restricting rows to the organization currently set in the user session. When no organization context exists, the expression resolves to -99, limiting visibility to records without an assigned ORG_ID. This confirms the view is intended as an org-secured, read-only layer over the OKL accounting headers.

ETRM documentation notes the view is "Not implemented in this database," indicating it may not exist in every environment or schema where the base table is present. The documented referenced base objects list is empty, so OKL_AE_HEADERS is the sole named source per the view text.

Key Columns

• AE_HEADER_ID – Primary identifier for the accounting entry header; joins to line-level tables such as OKL_AE_LINES.
• ACCOUNTING_EVENT_ID – Links the header to the originating accounting event in the OKL event model.
• SET_OF_BOOKS_ID – The ledger (set of books) to which the entries belong.
• ORG_ID – Operating unit; drives the view's org-security filter.
• AE_CATEGORY – Classifies the accounting entry, such as accrual, cash, or depreciation-related categories.
• PERIOD_NAME / ACCOUNTING_DATE – The GL period and accounting date governing when entries post.
• POST_TO_GL_FLAG – Indicates whether the header is eligible for posting to the General Ledger.
• GL_TRANSFER_FLAG – Reflects the transfer status of the header to GL.
• GL_TRANSFER_ERROR_CODE / ACCOUNTING_ERROR_CODE – Diagnostic codes when transfer or accounting creation fails.
• GL_TRANSFER_RUN_ID – Identifies the transfer-to-GL concurrent request that processed the header.
• GL_REVERSAL_FLAG / CROSS_CURRENCY_FLAG – Indicate reversal status and whether the event involved cross-currency accounting.
• SEQUENCE_ID / SEQUENCE_VALUE – Support ordering and grouping of related events.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID – Standard audit and concurrent-program provenance columns.

Common Use Cases and Queries

A frequent scenario is identifying headers that should have posted to GL but did not. The following query lists candidates by period:

• SELECT ae_header_id, accounting_event_id, period_name, post_to_gl_flag, gl_transfer_flag, gl_transfer_error_code FROM okl_ae_headers_v WHERE period_name = :period AND post_to_gl_flag = 'Y' ORDER BY ae_header_id;
• Reconciliation against GL: compare headers by GL_TRANSFER_FLAG and GL_TRANSFER_RUN_ID to trace which concurrent request transferred each entry.
• Error triage: filter on ACCOUNTING_ERROR_CODE or GL_TRANSFER_ERROR_CODE IS NOT NULL to isolate failed entries.
• Period-close review: aggregate counts by AE_CATEGORY and SET_OF_BOOKS_ID to confirm completeness before closing.

Because the view applies organization security through CLIENT_INFO, queries executed outside an initialized org context return only records with a null or -99 ORG_ID. Report developers should therefore ensure the correct operating unit is set before relying on results.