Results for “okl_ext_ap_header_sources_v”

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

Overview

OKL_EXT_AP_HEADER_SOURCES_V is an APPS-owned reporting view within the Oracle Lease and Finance Management (OKL) module. It exposes header-level information originating from the external Accounts Payable header source extension tables used by OKL. In the Oracle EBS 12.1.1 and 12.2.2 data models, the underscore-V designation confirms that this object is a view rather than a base table, and it is defined over the corresponding _B (base) and _TL (translation) tables through synonyms. Its status is VALID, and it resides in the APPS schema alongside the other OKL objects.

The view plays a supporting role in the OKL integration flow with Oracle Payables, where lease-related transactions are converted into AP invoice headers. It exposes the descriptive and classificatory attributes captured on those header sources, allowing reporting, reconciliation, and diagnostic queries without requiring joins directly to the underlying base and translation tables.

Underlying Base Objects

The documented referenced base objects for this view are OKL_EXT_AP_HEADER_SOURCES_B and OKL_EXT_AP_HEADER_SOURCES_TL, both accessed via synonyms. The _B table holds the primary base-language rows and the core column values, while the _TL table supplies translated, language-dependent descriptions. The view consolidates these two sources so that a single SELECT returns complete header source detail.

This structure is consistent with standard EBS multi-language object design: the _B table stores the transactional or attribute data, the _TL table stores translated descriptive fields keyed by the same primary key with a language column, and the view abstracts the join. Consumers should treat the view as read-only and should not attempt DML against it, since writes belong to the underlying base tables and their associated PL/SQL APIs.

Key Columns

The view exposes a broad set of identification, classification, and descriptive columns. Notable identifiers include HEADER_EXTENSION_ID (the primary key of the extension record), SOURCE_ID and SOURCE_TABLE (which together identify the originating record and its parent table), KHR_ID and TRY_ID (foreign references to lease and transaction-related entities), and OBJECT_VERSION_NUMBER for optimistic locking. Business-facing identifiers include TRANS_NUMBER, CONTRACT_NUMBER, CONVERTED_NUMBER, CUSTOMER_NAME, CUST_ACCOUNT_NUMBER, PRODUCT_NAME, PO_ORDER_NUMBER, and VENDOR_PROGRAM_NUMBER.

Classification and control columns include BOOK_CLASSIFICATION_CODE, TAX_OWNER_CODE, INT_CALC_METHOD_CODE (interest calculation method), REV_REC_METHOD_CODE (revenue recognition method), SCS_CODE, CONTRACT_CURRENCY_CODE, and CONTRACT_EFFECTIVE_FROM. Boolean-style indicators are represented as flags, such as ASSIGNABLE_FLAG, CONVERTED_ACCOUNT_FLAG, and ACCRUAL_OVERRIDE_FLAG. The view also carries two descriptive flexfield segments: the KHR_ATTRIBUTE_CATEGORY with KHR_ATTRIBUTE1 through KHR_ATTRIBUTE15, and the CUST_ATTRIBUTE_CATEGORY with CUST_ATTRIBUTE1 onward. Note that the excerpted view text does not expose a column literally named CONTRACT_STATUS_CODE; contract status is typically derived from the source contract tables, so queries seeking contract status should resolve it through the source table referenced by SOURCE_TABLE and SOURCE_ID.

Common Use Cases and Queries

Typical usage centers on reporting, reconciliation, and troubleshooting of the OKL-to-AP header conversion. The view is useful when validating which lease contracts and transactions contributed to a given AP header, confirming classification codes and currency, and auditing flexfield attribute values.

• Locate extension records by contract: SELECT CONTRACT_NUMBER, TRANS_NUMBER, CUSTOMER_NAME, CONTRACT_CURRENCY_CODE FROM APPS.OKL_EXT_AP_HEADER_SOURCES_V WHERE CONTRACT_NUMBER = :p_contract;
• Trace a source record: SELECT HEADER_EXTENSION_ID, SOURCE_ID, SOURCE_TABLE, KHR_ID, TRY_ID FROM APPS.OKL_EXT_AP_HEADER_SOURCES_V WHERE SOURCE_ID = :p_source_id;
• Review classification and flags: SELECT CONTRACT_NUMBER, BOOK_CLASSIFICATION_CODE, INT_CALC_METHOD_CODE, REV_REC_METHOD_CODE, ASSIGNABLE_FLAG, ACCRUAL_OVERRIDE_FLAG FROM APPS.OKL_EXT_AP_HEADER_SOURCES_V;
• Audit flexfield attributes: SELECT CONTRACT_NUMBER, KHR_ATTRIBUTE_CATEGORY, KHR_ATTRIBUTE1, CUST_ATTRIBUTE_CATEGORY, CUST_ATTRIBUTE1 FROM APPS.OKL_EXT_AP_HEADER_SOURCES_V WHERE CUST_ATTRIBUTE_CATEGORY IS NOT NULL;

Because the view is not indexed independently, restrictive WHERE clauses on SOURCE_ID, CONTRACT_NUMBER, or HEADER_EXTENSION_ID generally produce the most efficient execution plans in high-volume environments.