Results for “okl_ae_headers”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_AE_HEADERS is a transaction table within the Oracle E-Business Suite Release 12.1.1 / 12.2.2 Leasing and Finance Management (OKL) module. It stores accounting entry headers — the top-level grouping records that consolidate the debit and credit lines generated when the leasing engine processes an accounting event. Each header represents a single, balanced accounting entry (journal batch equivalent) produced for a contract, asset, or stream transaction during accounting generation, and it serves as the parent container for the individual distribution lines held in OKL_AE_LINES.
The table is a core component of the OKL subledger accounting flow: accounting events are captured, rules are applied, and the resulting entries are written first to a header row in this table and then to one or more line rows. Under the heuristic Data Vault classification supplied in the metadata, OKL_AE_HEADERS is characterized as satellite-leaning. This classification should be treated as a modeling suggestion rather than a documented fact: it reflects the table's descriptive, context-carrying role as a child of the accounting-event hub and its position above dependent line records. The designation is consistent with a table that holds descriptive attributes about an accounting entry rather than acting as a pure hub or a pure many-to-many link.
Key Information Stored
The only columns documented explicitly in the ETRM metadata are the primary key column and the foreign key column. In practice, these are the most significant structural attributes:
- AE_HEADER_ID — Surrogate primary key, enforced by the constraint OKL_AE_HEADERS_PK. It uniquely identifies each accounting entry header and is the value propagated to child line records.
- ACCOUNTING_EVENT_ID — Foreign key to OKL_ACCOUNTING_EVENTS. This is the principal business-key candidate, tying the header back to the originating accounting event and, through it, to the source lease or finance contract transaction.
Because the metadata for this object lists no additional business-key unique indexes beyond the surrogate PK, AE_HEADER_ID should be treated as the sole enforced unique identifier. Any uniqueness attributed to ACCOUNTING_EVENT_ID is a business assumption, not a documented constraint. Additional descriptive columns — entry status, GL date, currency, ledger, period, batch or group identifiers, and creation/audit columns — are conventionally present in OKL accounting header tables but are not part of the supplied metadata and should be verified against the actual data dictionary before being referenced in production SQL.
Common Use Cases and Queries
Typical use cases include subledger reconciliation, journal export validation, accounting-rule debugging, and period-close investigation of unbalanced or unposted entries.
- Header-to-line drill-down: join OKL_AE_HEADERS to OKL_AE_LINES on AE_HEADER_ID to reproduce the full debit/credit detail of a given accounting entry.
- Event traceability: join to OKL_ACCOUNTING_EVENTS on ACCOUNTING_EVENT_ID to trace an entry back to the contract or stream event that triggered it.
- Balancing checks: aggregate line amounts per header and compare debit and credit totals to detect entries where generation failed to balance.
- Volume and exception reporting: count headers per accounting event or per period to identify events that produced no entry or multiple entries unexpectedly.
A representative pattern:
SELECT h.ae_header_id, h.accounting_event_id, l.ae_line_id, l.amountFROM okl_ae_headers h, okl_ae_lines lWHERE h.ae_header_id = l.ae_header_idAND h.accounting_event_id = :event_id;
Related Objects
- OKL_ACCOUNTING_EVENTS — parent table referenced by OKL_AE_HEADERS.ACCOUNTING_EVENT_ID. Supplies the event context for every header.
- OKL_AE_LINES — principal child table, joined on OKL_AE_LINES.AE_HEADER_ID → OKL_AE_HEADERS.AE_HEADER_ID. Holds the individual distribution lines belonging to each header.
These two relationships constitute the documented FK structure of the object. Reporting views, subledger transfer programs, and GL interface routines that consume OKL accounting entries operate against this header/line pair. Because the metadata states the table is "Not implemented in this database," any reference to it should be confirmed against the target instance before being used in deliverables.
-
SYNONYM: APPS.OKL_AE_HEADERS 12.1.1
-
SYNONYM: APPS.OKL_AE_HEADERS 12.2.2
-
Table: OKL_AE_HEADERS 12.1.1
Accounting entry headers
Not implemented in this database·Explore OKL module →
-
Table: OKL_AE_HEADERS 12.2.2
Accounting entry headers
Not implemented in this database·Explore OKL module →
-
View: OKL_AE_LINES_UPDT_UV 12.1.1
APPS.OKL_AE_LINES_UPDT_UV·↳ GL_CODE_COMBINATIONS_KFV·↳ OKL_ACCOUNTING_UTIL·↳ OKL_ACC_EVENTS_ALL·Explore OKL module →
-
View: OKL_AE_LINES_UPDT_UV 12.2.2
APPS.OKL_AE_LINES_UPDT_UV·↳ GL_CODE_COMBINATIONS_KFV·↳ OKL_ACCOUNTING_UTIL·↳ OKL_ACC_EVENTS_ALL·Explore OKL module →
-
Table: OKL_ACCOUNTING_EVENTS 12.1.1
Accounting Events
Not implemented in this database·Explore OKL module →
-
VIEW: APPS.OKL_AEL_SL_V 12.2.2
-
Table: OKL_AE_LINES 12.1.1
Accounting Entry lines
Not implemented in this database·Explore OKL module →
-
Table: OKL_AE_LINES 12.2.2
Accounting Entry lines
Not implemented in this database·Explore OKL module →
-
Table: OKL_ACCOUNTING_EVENTS 12.2.2
Accounting Events
Not implemented in this database·Explore OKL module →