Results for “okl_ext_ar_header_sources_v”

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

Overview

OKL_EXT_AR_HEADER_SOURCES_V is an APPS-owned view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, delivered as part of the OKL – Leasing and Finance Management product family. The view exposes information about external receivables (AR) header sources originating from Oracle Lease and Finance Management contracts, providing a consolidated, read-only projection of contract- and quote-related header attributes that would otherwise require joining several storage objects. Its principal role is to support reporting, inquiry, and integration scenarios in which downstream Oracle Receivables processing, conversion handling, or third-party systems require visibility into the attributes that qualify a leasing contract for AR header generation.

The name carries the "EXT_AR" prefix, indicating external AR header sourcing, and the suffix "_V" confirms it is a database view rather than a physical table. As with most OKL views, it is intended for query access only; direct DML against the view is not supported and must be performed against the underlying base tables through the standard OKL concurrent processes or public APIs.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, OKL_EXT_AR_HEADER_SOURCES_V is defined over two referenced base objects, both exposed to APPS through synonyms:

• OKL_EXT_AR_HEADER_SOURCES_B (SYNONYM) – the base table holding the header source extension identifier, source identifiers, and the majority of the scalar and descriptive attributes.
• OKL_EXT_AR_HEADER_SOURCES_TL (SYNONYM) – the translation table that supplies language-dependent descriptive text, joined to the base table on the primary key in the standard multi-language pattern used throughout EBS.

The view text confirms that nearly all columns are sourced from the base table alias RXH, including the primary header extension ID, source ID, and source table reference. The view therefore functions as a convenience layer combining the operational base table and its translations, rather than as a transformation or aggregation object.

Key Columns

The view exposes a broad set of columns. The most significant for reporting and integration purposes include:

• HEADER_EXTENSION_ID – primary identifier for the external AR header extension record.
• SOURCE_ID and SOURCE_TABLE – identify the originating record and its source table, allowing traceability back to the contract or quote.
• KHR_ID and TRY_ID – links to the contract header and related terms, essential for joining to OKL contract structures.
• CONTRACT_NUMBER and TRANS_NUMBER – human-readable contract and transaction references.
• PRODUCT_NAME – the contract product description; this is frequently the column users search for, since "inv_agrmnt_product_name" commonly maps to this attribute when reconciling invoices and agreements.
• BOOK_CLASSIFICATION_CODE, TAX_OWNER_CODE, INT_CALC_METHOD_CODE, REV_REC_METHOD_CODE, and SCS_CODE – accounting and methodology indicators that drive downstream AR treatment.
• CONTRACT_EFFECTIVE_FROM and CONTRACT_CURRENCY_CODE – effective dating and currency context.
• SALES_REP_NAME, PO_ORDER_NUMBER, and VENDOR_PROGRAM_NUMBER – commercial reference attributes.
• ASSIGNABLE_FLAG, CONVERTED_ACCOUNT_FLAG, and ACCRUAL_OVERRIDE_FLAG – control flags influencing eligibility and accounting behaviour.
• TERM_QUOTE_ACCEPT_DATE, TERM_QUOTE_NUM, and TERM_QUOTE_TYPE_CODE – quotation references associated with the contract.
• KHR_ATTRIBUTE1..15, KHR_ATTRIBUTE_CATEGORY, CUST_ATTRIBUTE1..15, and CUST_ATTRIBUTE_CATEGORY – the standard EBS descriptive flexfield segments for contract header and customer-defined extensions.
• OBJECT_VERSION_NUMBER – optimistic locking / row version indicator.

Common Use Cases and Queries

Typical uses include reconciling leasing contracts against invoices, auditing conversion and accrual overrides, and feeding external AR integration interfaces. A representative query retrieving contract and product information for a specific contract number is shown below:

• SELECT header_extension_id, contract_number, product_name, book_classification_code, contract_currency_code FROM okl_ext_ar_header_sources_v WHERE contract_number = :p_contract_number;
• SELECT contract_number, product_name, sales_rep_name, po_order_number FROM okl_ext_ar_header_sources_v WHERE product_name LIKE :p_product_name; – useful when resolving the "inv_agrmnt_product_name" search, as it locates header source records by product description.
• SELECT h.contract_number, h.product_name, h.book_classification_code FROM okl_ext_ar_header_sources_v h WHERE h.assignable_flag = 'Y' AND h.converted_account_flag = 'N'; – identifies contracts eligible for AR assignment.

Because the view includes KHR_ID and TRY_ID, it is commonly joined to OKL contract header and term tables to retrieve additional contract detail. All queries should be run under an APPS or appropriately privileged reporting responsibility, and performance is best when filtering on indexed identifiers such as CONTRACT_NUMBER, KHR_ID, or HEADER_EXTENSION_ID.