Results for “okl_ar_inv_ia_ref_v”

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

Overview

The APPS.OKL_AR_INV_IA_REF_V view is a reporting and integration construct within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. It presents investor agreement billing reference information by joining header-level, line-level, and transaction detail records captured in the Oracle Lease Management external receivables extension tables. The view is explicitly restricted to investor billing scenarios; the defining query enforces a fixed predicate on the header source, RXH.SCS_CODE = 'INVESTOR', ensuring that only records associated with the investor source system are surfaced. This restriction is annotated in the view text as being applicable because the reference view serves investor billing exclusively.

The view carries a VALID status in the APPS schema and exposes a denormalized projection across the three source tables, allowing downstream processes, concurrent programs, and ad hoc reports to retrieve investor invoice agreement attributes without re-implementing the multi-table join logic. It is commonly consumed where investor billing settlement, contingency tracking, or memo-flag-based reporting is required.

Underlying Base Objects

The view is defined over three base objects, all referenced through synonyms in the APPS schema:

• OKL_EXT_AR_HEADER_SOURCES_B (aliased RXH) — supplies header-level investor agreement information. Joined via RXH.HEADER_EXTENSION_ID.
• OKL_EXT_AR_LINE_SOURCES_B (aliased RXL) — supplies line-level detail such as contingency, memo flag, and stream type attributes. The join is constrained with RXL.SOURCE_TABLE = 'OKL_TXD_AR_LN_DTLS_B' and RXL.HEADER_EXTENSION_ID = RXH.HEADER_EXTENSION_ID.
• OKL_TXD_AR_LN_DTLS_B (aliased TXD) — the transaction detail base table, joined on RXL.SOURCE_ID = TXD.ID.

The resulting key identifier from the transaction detail is exposed as OKL_TXD_ID, linking the header extension, line extension, and transaction detail rows into a single flattened record.

Key Columns

The view surfaces identifiers and descriptive attributes across the three source tables. Notable columns include:

• OKL_TXD_ID, OKL_KHR_ID, OKL_KLE_ID — primary identifiers for the transaction detail, header, and line extension records.
• OKL_MEMO_FLAG (sourced from RXL.MEMO_FLAG; documented column listing TEL_MEMO_FLAG) — indicates whether the investor billing line is treated as a memo item, a key criterion for users searching on "okl_memo_flag".
• OKL_INV_AGRMNT_NUMBER, OKL_INV_AGRMNT_STATUS_CODE, OKL_INV_AGRMNT_EFFECTIVE_FROM — investor agreement identity and lifecycle attributes.
• OKL_INV_AGRMNT_CURRENCY_CODE, OKL_INV_AGRMNT_SYND_CODE, OKL_INV_AGRMNT_POOL_NUMBER — financial and pooling attributes of the investor agreement.
• OKL_CONTINGENCY_CODE, OKL_STREAM_TYPE_CODE, OKL_STREAM_TYPE_PURPOSE_CODE — contingency and cash stream classification from the line source.
• OKL_AE_TEMPLATE_NAME (RXL.ACCOUNTING_TEMPLATE_NAME) — the accounting template applied to the line.

Common Use Cases and Queries

Typical uses include investor billing reconciliation, memo-flag analysis, and reconciliation of accounting template assignments. A representative query filtering on the memo flag follows:

• SELECT okl_inv_agrmnt_number, okl_memo_flag, okl_contingency_code, okl_stream_type_code FROM okl_ar_inv_ia_ref_v WHERE okl_memo_flag = 'Y';
• SELECT okl_txd_id, okl_khr_id, okl_inv_agrmnt_status_code FROM okl_ar_inv_ia_ref_v WHERE okl_inv_agrmnt_effective_from >= :from_date;

Because the view is pre-filtered to the INVESTOR source, consumers do not need to add the SCS_CODE predicate. All querying should be performed within the APPS schema context to resolve the underlying synonyms correctly.