Search Results okl_ext_ar_line_sources_b




Overview
Explore in AI Chat

Overview

The OKL_EXT_AR_LINE_SOURCES_B table is a core extension table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a detailed child table, extending the functionality of Receivables (AR) transaction lines for complex lease and finance contracts. Its primary role is to store supplementary sourcing and vendor information that is specific to the leasing context but not natively captured in standard Oracle Receivables tables. This enables the integration of detailed asset procurement and subsidy data with the financial invoicing and revenue recognition processes, supporting accurate billing and accounting for leased assets.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which indicate the critical data points it manages. The primary key, LINE_EXTENSION_ID, uniquely identifies each extended line record. The foreign keys reveal the table's central purpose: linking a standard contract line item (via KLE_ID to OKC_K_LINES_B) to specific lease-related attributes. Key stored information includes references to the associated header extension record (HEADER_EXTENSION_ID), the classification of the revenue or cost stream (via STY_ID to OKL_STRM_TYPE_B), and crucial vendor identifiers. These vendor links—ASSET_VENDOR_ID and SUBSIDY_VENDOR_ID, both referencing AP_SUPPLIERS—are essential for tracking the asset supplier and any third-party subsidy provider associated with the lease line.

Common Use Cases and Queries

This table is primarily accessed for reporting and data validation in scenarios requiring a consolidated view of lease billing details. A common use case is generating an invoice support report that lists all billed line items alongside their underlying asset vendors. Technical consultants often query this table to troubleshoot issues where vendor information is missing on invoices or to validate data integrity during migrations. A typical SQL pattern involves joining to the contract lines and supplier tables:

  • SELECT kll.line_number, sup.vendor_name, ext.*
  • FROM okl_ext_ar_line_sources_b ext,
  • okc_k_lines_b kll,
  • ap_suppliers sup
  • WHERE ext.kle_id = kll.id
  • AND ext.asset_vendor_id = sup.vendor_id(+);

Another critical use case is during the creation of accounting events, where the stream type (STY_ID) and vendor details from this table may be used to determine the correct accounting rules.

Related Objects

The OKL_EXT_AR_LINE_SOURCES_B table sits at a nexus between contract management, payables, and receivables data. Its documented foreign key relationships are fundamental for any integration or reporting logic.

  • OKL_EXT_AR_LINE_SOURCES_B (Self-Reference on HEADER_EXTENSION_ID): Links the line extension records to their parent header extension record, which is stored in the same table structure, forming a header-detail relationship.
  • OKC_K_LINES_B (via KLE_ID): The foundational relationship connecting the extension data to the standard contract line in the Contracts Core module.
  • OKL_STRM_TYPE_B (via STY_ID): Provides the stream type (e.g., Lease Rental, Interest) classification for the line item, critical for revenue scheduling and accounting.
  • AP_SUPPLIERS (via ASSET_VENDOR_ID): Identifies the supplier of the leased asset from the Payables module.
  • AP_SUPPLIERS (via SUBSIDY_VENDOR_ID): Identifies a third-party vendor providing a subsidy or incentive related to the lease line.