Search Results okl_trx_ap_invoices_b

Overview

The OKL_TRX_AP_INVOICES_B table is a core data repository within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the central transactional table for all lease and finance management activities that result in the generation of accounts payable (AP) invoices. Its primary role is to record the financial obligations arising from various OKL transactions, such as asset purchases, vendor payments, and contract-related expenses, before these obligations are formally interfaced to the Oracle Payables module for processing and payment. The table's structure facilitates the integration of leasing operations with the broader financial accounting system.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented foreign key relationships reveal the critical data entities linked to each payable invoice record. The table stores a unique identifier (ID) as its primary key. Each record is fundamentally associated with a lease or finance agreement via the KHR_ID, linking to the OKL_K_HEADERS table. It identifies the vendor (VENDOR_ID from PO_VENDORS) to be paid and the general ledger account (CODE_COMBINATION_ID from GL_CODE_COMBINATIONS) for accounting. The table also captures the transaction's context by linking to the originating transaction type (TRY_ID from OKL_TRX_TYPES_B), the specific contract transaction (TCN_ID from OKL_TRX_CONTRACTS), or a related quote (QTE_ID from OKL_TRX_QUOTES_B). Furthermore, it supports transactional integrity by storing references for reversals (TAP_ID_REVERSES, a self-referencing key) and links to related asset returns (ART_ID).

Common Use Cases and Queries

A primary use case is tracing the complete payable lifecycle for a lease contract. Analysts or support personnel often query this table to investigate why an expected vendor invoice was not created in Payables or to reconcile OKL transaction volumes with AP invoice batches. Common reporting needs include summarizing all pending payables generated by OKL for a specific vendor or during a specific accounting period. A sample query pattern would join OKL_TRX_AP_INVOICES_B to the lease header and vendor tables to create a payable invoice register:

• SELECT tap.id, khr.contract_number, pov.vendor_name, tap.creation_date FROM okl_trx_ap_invoices_b tap, okl_k_headers khr, po_vendors pov WHERE tap.khr_id = khr.id AND tap.vendor_id = pov.vendor_id(+) AND TRUNC(tap.creation_date) = :p_date;

Another critical scenario involves troubleshooting reversals or adjustments by querying records and their corresponding reversing entries using the self-referencing foreign key column TAP_ID_REVERSES.

Related Objects

The table is integral to the OKL data model, with numerous documented relationships. Key related objects, as per the provided foreign key metadata, include:

• OKL_K_HEADERS: The master lease/finance agreement, joined via OKL_TRX_AP_INVOICES_B.KHR_ID.
• PO_VENDORS: The supplier to be paid, joined via OKL_TRX_AP_INVOICES_B.VENDOR_ID.
• GL_CODE_COMBINATIONS: The accounting flexfield, joined via OKL_TRX_AP_INVOICES_B.CODE_COMBINATION_ID.
• OKL_TRX_CONTRACTS: The source contract transaction, joined via OKL_TRX_AP_INVOICES_B.TCN_ID.
• OKL_TRX_TYPES_B: The transaction type definition, joined via OKL_TRX_AP_INVOICES_B.TRY_ID.
• OKL_TXL_AP_INV_LNS_B: Child invoice lines reference the header via OKL_TXL_AP_INV_LNS_B.TAP_ID.
• OKL_TRX_AR_INVOICES_B: Related accounts receivable invoices may link via OKL_TRX_AR_INVOICES_B.TAP_ID.
• OKL_ASSET_RETURNS_B: Has a bidirectional relationship; it can be a source (ART_ID) or a destination (SECURITY_DEP_TRX_AP_ID) for payable invoice transactions.