Search Results okl_txl_ap_inv_lns_b




Overview
Explore in AI Chat

Overview

The OKL_TXL_AP_INV_LNS_B table is a core transactional entity within the Oracle E-Business Suite's Leasing and Finance Management (OKL) module, specifically in the context of the Payables integration. Its primary role is to serve as a staging and mapping table for transaction lines that are destined for inclusion in Oracle Payables invoices. It acts as a critical bridge between the leasing-specific transaction data and the general ledger accounting processes, ensuring that financial obligations from lease contracts are accurately captured and prepared for payment processing within the broader EBS financial ecosystem. The table's structure facilitates the grouping of individual lease transaction lines into consolidated Payables invoices.

Key Information Stored

While specific column details are not fully enumerated in the provided metadata, the foreign key relationships define the essential data linkages stored in this table. Each record typically represents a single transaction line earmarked for a Payables invoice and contains identifiers that map to related entities. The primary key is the ID column. Crucially, the table stores foreign keys such as KLE_ID (linking to the OKL_K_LINES table for the source lease line), TAP_ID (linking to the parent OKL_TRX_AP_INVOICES_B header), and CODE_COMBINATION_ID (linking to GL_CODE_COMBINATIONS for the accounting flexfield). It also maintains relationships to stream types (STY_ID), consolidated streams (LSM_ID), and supports reversals through a self-referential key (TPL_ID_REVERSES). The presence of a link to OKL_XTL_PAY_INVS_B suggests integration with extended payment processing.

Common Use Cases and Queries

This table is central to processes that generate supplier invoices for lease-related expenses or payments. A common operational use case is the batch creation of Payables invoices from accrued lease charges. For reporting and reconciliation, queries often join this table to its related sources to trace the flow of a transaction from the lease contract to the payable invoice. A typical validation or audit query might follow this pattern:

  • SELECT tpl.id, kle.line_number, tap.invoice_number, gcc.segment1, gcc.segment2 FROM okl_txl_ap_inv_lns_b tpl JOIN okl_k_lines kle ON tpl.kle_id = kle.id JOIN okl_trx_ap_invoices_b tap ON tpl.tap_id = tap.id JOIN gl_code_combinations gcc ON tpl.code_combination_id = gcc.code_combination_id WHERE tap.invoice_date BETWEEN :p_start_date AND :p_end_date;

This identifies the invoice lines, their source lease lines, the target invoice, and the associated accounting codes for a given period.

Related Objects

The OKL_TXL_AP_INV_LNS_B table is a nexus within the OKL schema, with dependencies to several key objects. Its primary foreign key relationships, as documented, are:

  • OKL_TRX_AP_INVOICES_B: The parent invoice header table.
  • OKL_K_LINES: The source transaction lines from lease contracts.
  • GL_CODE_COMBINATIONS: The general ledger accounting flexfield combination.
  • OKL_CNSLD_AR_STRMS_B: For associated consolidated receivable streams.
  • OKL_STRM_TYPE_B: For the type classification of the financial stream.
  • OKL_XTL_PAY_INVS_B: For extended payment invoice processing.

The table also has a self-referential relationship (TPL_ID_REVERSES) to manage reversal transactions. It is protected by the primary key constraint OKL_TXL_AP_INV_LNS_B_PK.