Search Results okl_ext_ar_header_sources_b_pk

Overview

The OKL_EXT_AR_HEADER_SOURCES_B table is a core extension table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It functions as a critical repository for extended attributes associated with the header records of Receivables (AR) transactions. In the context of Oracle EBS 12.1.1 and 12.2.2, this table enables the OKL product to store specialized leasing and financing data that augments the standard Oracle Receivables transaction headers. Its primary role is to facilitate the integration of complex lease-specific financial logic with the foundational AR accounting and processing engine, ensuring that transactional data adheres to both standard accounting practices and industry-specific leasing requirements.

Key Information Stored

The table's structure is centered on linking extended leasing data to standard transaction identifiers. The primary key, HEADER_EXTENSION_ID, uniquely identifies each record in this extension table. Based on the documented foreign key relationships, two other critical columns define its associations. The KHR_ID column serves as a foreign key, linking the extended header data to its corresponding base transaction header within the OKL data model, typically a lease or contract header. The TRY_ID column acts as a foreign key to the OKL_TRX_TYPES_B table, which stores the definitions of transaction types specific to leasing operations. This structure allows the system to categorize and process extended AR transactions according to predefined leasing business rules.

Common Use Cases and Queries

This table is primarily accessed during the generation and inquiry of lease-related invoices, credit memos, and adjustments within Receivables. A common operational use case involves retrieving the extended header information for a specific lease contract to validate or report on billing activities. For reporting and reconciliation, analysts often join this table to standard AR tables to create unified views of transactional data. A typical query pattern would involve joining to the base OKL header table via KHR_ID and to the transaction type table via TRY_ID to produce a descriptive dataset.

• Sample SQL Pattern: SELECT ext.*, typ.NAME FROM OKL_EXT_AR_HEADER_SOURCES_B ext, OKL_TRX_TYPES_B typ WHERE ext.TRY_ID = typ.TRY_ID AND ext.KHR_ID = :p_contract_id;

Related Objects

The OKL_EXT_AR_HEADER_SOURCES_B table maintains defined relationships with other key objects in the OKL schema, as per the provided metadata. Its primary key ensures data integrity for any dependent objects or interfaces. The documented foreign key relationships are as follows:

• Primary Key: OKL_EXT_AR_HEADER_SOURCES_B_PK on column HEADER_EXTENSION_ID.
• Foreign Key Relationship 1: The table references itself via the column KHR_ID. This recursive relationship likely models hierarchical structures within transaction headers.
• Foreign Key Relationship 2: The table references OKL_TRX_TYPES_B via the column TRY_ID. This links each extended header to a specific leasing transaction type, which governs its accounting and processing behavior.

This table is a foundational component for any custom reporting or integration that requires a complete view of lease-billed receivables transactions, bridging the standard AR and specialized OKL data models.