Results for “okl_txd_id”

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

Overview

OKL_AR_INV_KHR_IA_REF_VL is an APPS-owned database view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. Its documented status is VALID. The view exposes lease transaction line detail data in a denormalized, presentation-ready form, correlating Accounts Receivable invoice extension records with their associated header definitions, translated header and line attributes, and the underlying transaction line detail rows stored in OKL_TXD_AR_LN_DTLS_B. The name suffix "KHR_IA_REF" reflects its role as a keyed reference structure for invoice and agreement attributes, while "VL" denotes that it is a value/validation view typically consumed by Oracle Application Framework (OAF) pages, lookup validations, and dependent reporting queries rather than by interactive end users directly.

The view is significant because the search term "okl_txd_id" maps to its first projected column. This column is the primary correlation key that links AR invoice extension rows back to the originating leasing transaction detail record, making the view a natural entry point for diagnostics and reconciliation of lease-to-invoice data flows.

Underlying Base Objects

The view is defined over five documented base objects, all exposed as APPS synonyms:

• OKL_TXD_AR_LN_DTLS_B — the transaction line detail base table that supplies the OKL_TXD_ID key and the driving row source.
• OKL_EXT_AR_HEADER_SOURCES_B — AR invoice header extension base table providing header-level extension identifiers.
• OKL_EXT_AR_HEADER_SOURCES_TL — translated header extension table supplying language-dependent header attributes.
• OKL_EXT_AR_LINE_SOURCES_B — AR invoice line extension base table linking line and header extension identifiers and the source row.
• OKL_EXT_AR_LINE_SOURCES_TL — translated line extension table supplying language-dependent line attributes.

The join logic enforces RXL.SOURCE_TABLE = 'OKL_TXD_AR_LN_DTLS_B', equates header extension IDs across RXH, RXHL, and RXL, equates line extension IDs across RXL and RXLL, links RXL.SOURCE_ID to TXD.ID, and constrains RXHL.LANGUAGE = RXLL.LANGUAGE so that only matching-language header and line translations are returned.

Key Columns

• OKL_TXD_ID — the transaction detail identifier, sourced from TXD.ID; the primary join key to OKL_TXD_AR_LN_DTLS_B.
• OKL_LANGUAGE — the language code governing the translated attributes returned.
• OKL_CONTRACT_STATUS — the contract status of the lease.
• OKL_INV_AGRMNT_STATUS — the invoice agreement status.
• OKL_STREAM_TYPE_NAME — the payment stream type (for example, rent, residuals, or fees).
• OKL_TRANSACTION_TYPE_NAME — the transaction type description.
• OKL_TRANS_LINE_DESCRIPTION — the descriptive text for the transaction line.
• OKL_INVENTORY_ORG_NAME — the inventory organization name associated with the line.

Common Use Cases and Queries

Typical uses include verifying that a leasing transaction line generated the expected AR invoice extension rows, reporting stream-level invoice composition by contract status, and troubleshooting missing or duplicated translation rows caused by language mismatches.

Retrieve all referenced attributes for a specific transaction detail:

• SELECT okl_txd_id, okl_contract_status, okl_stream_type_name, okl_trans_line_description FROM okl_ar_inv_khr_ia_ref_vl WHERE okl_txd_id = :txd_id;

List transactions by contract status and language:

• SELECT okl_txd_id, okl_transaction_type_name FROM okl_ar_inv_khr_ia_ref_vl WHERE okl_contract_status = :status AND okl_language = USERENV('LANG');

Aggregate line counts by stream type for reconciliation:

• SELECT okl_stream_type_name, COUNT(*) FROM okl_ar_inv_khr_ia_ref_vl GROUP BY okl_stream_type_name;

Because the view performs inner joins across all five base objects, rows are returned only where complete header and line extension records exist in the matching language; absent translations or extension rows will suppress the transaction from the result set, which is a common cause of apparent data gaps during reconciliation.