Search Results okl_trx_ap_invs_all_b




Overview
Explore in AI Chat

Overview

The OKL_TRX_AP_INVS_ALL_B table is a core transactional entity within Oracle E-Business Suite's Lease and Finance Management (OKL) module. It serves as the central repository for all lease and finance transactions that result in the generation of invoices in the Oracle Payables (AP) module. This table acts as a critical integration point, linking the specialized leasing transactions of OKL to the standard financial processing workflows of Accounts Payable. Its design follows the Oracle EBS multi-org structure, as indicated by the "_ALL_B" suffix, meaning it stores data for all operating units with appropriate security via the ORG_ID column. The table's primary function is to record the essential header-level information for payables invoices originating from lease contracts, asset returns, quotes, and other financial events.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which reveal the critical data points it manages. The primary key is the unique identifier (ID column). Essential foreign keys define the transaction's context: KHR_ID links to the lease contract in OKL_K_HEADERS, VENDOR_ID identifies the supplier in AP_SUPPLIERS, and TRY_ID references the transaction type in OKL_TRX_TYPES_B. The table tracks financial reversal activity via the TAP_ID_REVERSES column, which self-references the table to indicate which invoice record is reversing another. Integration with General Ledger is managed through the CODE_COMBINATION_ID link to GL_CODE_COMBINATIONS. Other significant relationships include links to asset returns (ART_ID), transaction contracts (TCN_ID), and quotes (QTE_ID), providing a comprehensive audit trail for the payable invoice's origin within the leasing lifecycle.

Common Use Cases and Queries

This table is central for troubleshooting, reporting, and data validation for payables invoices generated from leasing operations. Common use cases include reconciling OKL transactions to Payables, auditing invoice generation history for a specific lease contract, and identifying reversed transactions. A typical query might join this table to the lease header and supplier tables to report on all payables invoices for a given vendor or contract.

  • Sample Query Pattern: SELECT tap.id, tap.khr_id, k.contract_number, tap.vendor_id, sup.vendor_name, tap.creation_date FROM okl_trx_ap_invs_all_b tap, okl_k_headers k, ap_suppliers sup WHERE tap.khr_id = k.id AND tap.vendor_id = sup.vendor_id AND k.contract_number = '<CONTRACT_NUM>';
  • Reporting: Generating reports to analyze supplier liabilities arising from lease transactions, or tracking the volume and value of payables invoices created by different OKL transaction types.
  • Data Fix: Identifying invoices in an error state by joining with related interface or transaction line tables to diagnose posting failures to Payables.

Related Objects

The OKL_TRX_AP_INVS_ALL_B table is a nexus within the OKL schema, with dependencies to several key objects. As documented, its primary foreign key relationships are with: OKL_K_HEADERS (lease contracts), AP_SUPPLIERS, OKL_TRX_TYPES_B, GL_CODE_COMBINATIONS, OKL_ASSET_RETURNS_ALL_B, OKL_TRX_QUOTES_ALL_B, and OKL_TRX_CONTRACTS_ALL_B (via TCN_ID). Crucially, it serves as the parent table for the OKL_TXL_AP_INV_LNS_ALL_B table, which holds the individual line items for each payable invoice header. For comprehensive reporting or data extraction, one must also consider related interface tables and public APIs, such as those in the OKL_PROCESS_AP_INVOICE_PVT package, which are responsible for the business logic of creating and managing these invoice records.