Search Results okl_trx_ar_invoices_b




Overview
Explore in AI Chat

Overview

The table OKL_TRX_AR_INVOICES_B is a core transactional entity within the Oracle E-Business Suite (EBS) module OKL (Leasing and Finance Management). It serves as the central repository for all leasing and finance transactions that generate invoices in the Oracle Receivables (AR) module. Its primary role is to act as the bridge between the specialized leasing operations managed in OKL and the standard financial processing handled by AR. Every record in this table represents a distinct business event, such as a lease booking, fee assessment, or adjustment, that results in a billable invoice to a customer. The table's structure, including its numerous foreign key relationships, is designed to maintain the integrity and traceability of these financial transactions from their source contract through to the final receivable.

Key Information Stored

The table's primary key is the ID column, uniquely identifying each transaction that generates an AR invoice. The most critical data points are the foreign key columns that link the invoice transaction to its originating source documents and define its context. These include KHR_ID, linking to the lease contract header in OKL_K_HEADERS; TRY_ID, identifying the transaction type from OKL_TRX_TYPES_B; and QTE_ID and SVF_ID, referencing transaction quotes and service fees, respectively. The TAI_ID_REVERSES column supports corrective accounting by pointing to the original transaction that a given record reverses. Additional links to insurance policies (IPY_ID) and related AP invoices (TAP_ID) provide a comprehensive financial picture.

Common Use Cases and Queries

This table is fundamental for reconciliation, audit, and custom reporting. A common use case involves tracing all invoices generated for a specific lease contract to verify billing completeness. Another critical scenario is identifying reversal transactions for audit trails. Sample queries often join this table with related leasing and Receivables interfaces.

  • Find invoices for a lease: SELECT tai.id, tai.khr_id, kh.contract_number FROM okl_trx_ar_invoices_b tai, okl_k_headers kh WHERE tai.khr_id = kh.id AND kh.contract_number = 'L-10001';
  • List transactions by type: SELECT tt.name, COUNT(tai.id) FROM okl_trx_ar_invoices_b tai, okl_trx_types_b tt WHERE tai.try_id = tt.id GROUP BY tt.name;
  • Identify reversal pairs: SELECT original.id AS orig_id, reversal.id AS rev_id FROM okl_trx_ar_invoices_b original, okl_trx_ar_invoices_b reversal WHERE reversal.tai_id_reverses = original.id;

Related Objects

OKL_TRX_AR_INVOICES_B is a central hub with extensive relationships. It is a parent table to line-level details stored in OKL_TXL_AR_INV_LNS_B and to records in OKL_CURE_PAYMENT_LINES. As documented, it is primarily a child table, referencing key master data: lease contracts (OKL_K_HEADERS), transaction types (OKL_TRX_TYPES_B), and source documents like quotes (OKL_TRX_QUOTES_ALL_B) and service fees (OKL_SERVICE_FEES_ALL_B). The self-referencing foreign key on TAI_ID_REVERSES allows for transaction reversals within the same table. For complete invoice data, this base table is typically accessed via its associated entity object or through the standard Receivables interface tables populated by the OKL invoice generation process.