Search Results okl_txl_ap_inv_lns_all_b

Overview

The table OKL_TXL_AP_INV_LNS_ALL_B is a core transaction storage object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the OKL (Leasing and Finance Management) product. Its primary role is to serve as a staging and linking table for transaction lines that are destined to be included in Payables invoices. This table acts as a bridge between the leasing-specific transaction processing in OKL and the standard Oracle Payables module (AP), facilitating the accurate flow of financial data for vendor payments related to lease contracts. It is a multi-org table, as indicated by the "_ALL_" suffix, meaning it stores data for multiple operating units with a security context managed via the ORG_ID column.

Key Information Stored

While the provided metadata does not list specific columns, the foreign key relationships and primary key structure reveal the critical data elements. The table's primary key is the ID column, uniquely identifying each payable invoice line record. Essential foreign key columns define its relationships: TAP_ID links the line to its parent payable invoice header in OKL_TRX_AP_INVS_ALL_B. KLE_ID associates the line with its source contract line in OKL_K_LINES. CODE_COMBINATION_ID stores the accounting flexfield (General Ledger account) for the transaction. STY_ID references the stream type from OKL_STRM_TYPE_B, classifying the nature of the payment stream. LSM_ID can link to a consolidated stream definition in OKL_CNSLD_AR_STRMS_B. The TPL_ID_REVERSES column supports reversal transactions by self-referencing the table's primary key, indicating which line a given record reverses.

Common Use Cases and Queries

A primary use case is tracing the lifecycle of a payable transaction from the lease contract through to invoice creation. Financial analysts and accountants may query this table to audit payable line items before they are transferred to Oracle Payables or to investigate discrepancies. Common reporting needs include listing all payable lines for a specific lease contract or vendor invoice. A sample query to fetch payable invoice lines for a specific contract header (KHR_ID) would involve joining through the OKL_K_LINES table:

• SELECT tpl.id, tpl.tap_id, kle.seq_no, tpl.code_combination_id FROM okl_txl_ap_inv_lns_all_b tpl JOIN okl_k_lines kle ON tpl.kle_id = kle.id WHERE kle.khr_id = <contract_id>;

Another critical scenario involves identifying reversal transactions by leveraging the self-referencing foreign key: SELECT * FROM okl_txl_ap_inv_lns_all_b WHERE tpl_id_reverses IS NOT NULL;

Related Objects

The table is central to a network of key OKL objects, as defined by its documented foreign keys:

• OKL_TRX_AP_INVS_ALL_B: The parent invoice header. Joined via TAP_ID = ID.
• OKL_K_LINES: The source lease contract line item. Joined via KLE_ID = ID.
• GL_CODE_COMBINATIONS: The General Ledger account. Joined via CODE_COMBINATION_ID = CODE_COMBINATION_ID.
• OKL_STRM_TYPE_B: The stream type (e.g., rent, interest). Joined via STY_ID = ID.
• OKL_CNSLD_AR_STRMS_B: Consolidated receivable streams. Joined via LSM_ID = ID.
• OKL_TXL_AR_INV_LNS_B: Related receivable invoice lines. Joined via OKL_TXL_AR_INV_LNS_B.TPL_ID = OKL_TXL_AP_INV_LNS_ALL_B.ID.
• Self-Reference (OKL_TXL_AP_INV_LNS_ALL_B): For reversal transactions. Joined via TPL_ID_REVERSES = ID.