Results for “okl_ael_gl_ctr_v”

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

Overview

OKL_AEL_GL_CTR_V is a VALID Oracle E-Business Suite view owned by the APPS schema, delivered with the OKL – Leasing and Finance Management product. Its purpose is to expose all contract-related leasing transactions that have been transferred to the General Ledger, and it is the primary data source that enables the Oracle Lease Management GL Drilldown functionality. Through this view, users can navigate from a GL journal entry back to the originating lease contract, transaction, stream, and accounting line without leaving the EBS environment.

The view consolidates accounting event data with contract header, transaction, stream, and GL import information. Because the drilldown must reconcile subledger accounting lines to posted GL journals, the view links Accounting Event Lines (AEL) to the corresponding GL Import References and journals. In the ETRM metadata, the view text explicitly aliases its accounting source as the literal value 'OKLECL' AEL_TABLE, and a related AEL_TABLE coding convention identifies the subledger event line source. This is why a search for "ael_table" surfaces OKL_AEL_GL_CTR_V: it embeds the AEL_TABLE identifier used by the GL Drilldown framework to determine the origin table for each row.

Underlying Base Objects

The documented base objects reveal a multi-layer join. Contract and party data come from OKC_K_HEADERS_B, OKC_K_PARTY_ROLES_B, OKL_K_HDRS_FULL_UV, OKX_PARTIES_V, and ARP_ADDR_LABEL_PKG. Transaction and stream detail is drawn from OKL_TRX_CONTRACTS_ALL, OKL_TXL_CNTRCT_LNS_ALL, OKL_TRX_TYPES_B, and OKL_STRM_TYPE_V. Accounting data is sourced from OKL_AE_HEADERS_ALL, OKL_AE_LINES_ALL, OKL_ACC_EVENTS_ALL, OKL_AE_TEMPLATES_ALL, and OKL_FORMULAE_B. GL-side references come from GL_IMPORT_REFERENCES, GL_JE_CATEGORIES_VL, and GL_DAILY_CONVERSION_TYPES. Lookup decoding and helper logic rely on OKL_ACCOUNTING_UTIL and OKC_UTIL packages. The view text confirms joins across these families using aliases such as KHR (contract header), TCN (transaction), STY (stream type), TRY (transaction type), AEL (accounting event line), AEH (accounting event header), and REF (GL import reference).

Key Columns

• CHR_CONTRACT_NUMBER, CHR_START_DATE, CHR_END_DATE, CHR_STS_CODE – Lease contract identity and status exposed from the contract header.
• TRX_NUMBER, TSU_CODE, TRX_TYPE_CLASS – Transaction number, stream/type usage code, and the decoded transaction type class via OKL_ACCOUNTING_UTIL.
• AEL_TABLE – Literal identifier (e.g., 'OKLECL') indicating the accounting event line source; central to GL Drilldown routing.
• ACCOUNTED_DR, ACCOUNTED_CR, ENTERED_DR, ENTERED_CR – Accounted and entered debit/credit amounts from OKL_AE_LINES_ALL.
• CODE_COMBINATION_ID, CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE – Accounting flexfield and currency conversion attributes.
• JE_HEADER_ID, JE_LINE_NUM, JE_CATEGORY, USER_JE_CATEGORY_NAME – Links to the GL journal header and category.
• SET_OF_BOOKS_ID, ORG_ID, GL_TRANSFER_STATUS, ACCOUNTING_DATE – Ledger, operating unit, transfer flag, and accounting date context.
• AE_HEADER_ID (AEH_ID), AE_LINE_ID (AEL_ID), ACCT_LINE_TYPE – Subledger accounting event header/line identifiers and line type.
• THIRD_PARTY_ID, DOC_SEQUENCE_VALUE, DOC_SEQUENCE_ID – Party reference and subledger document sequencing.

Common Use Cases and Queries

Typical uses include GL Drilldown from a posted journal back to lease contracts, reconciling leasing subledger transfers to GL, and auditing accounting event lines by contract or transaction.

• Drilldown from a GL journal line: SELECT CHR_CONTRACT_NUMBER, TRX_NUMBER, ACCOUNTED_DR, ACCOUNTED_CR FROM OKL_AEL_GL_CTR_V WHERE JE_HEADER_ID = :p_je_header_id AND JE_LINE_NUM = :p_je_line_num;
• All GL-transferred activity for a contract: SELECT TRX_NUMBER, ACCOUNTING_DATE, ACCOUNTED_DR, ACCOUNTED_CR, GL_TRANSFER_STATUS FROM OKL_AEL_GL_CTR_V WHERE CHR_CONTRACT_NUMBER = :p_contract_number ORDER BY ACCOUNTING_DATE;
• Reconciliation by ledger and period: SELECT SET_OF_BOOKS_ID, ACCOUNTING_DATE, SUM(ACCOUNTED_DR), SUM(ACCOUNTED_CR) FROM OKL_AEL_GL_CTR_V WHERE SET_OF_BOOKS_ID = :p_sob GROUP BY SET_OF_BOOKS_ID, ACCOUNTING_DATE;
• Isolating the AEL_TABLE source: SELECT DISTINCT AEL_TABLE FROM OKL_AEL_GL_CTR_V;

Because the view joins numerous accounting and contract objects, queries should always be filtered by contract, journal, or ledger to avoid full scans.