Search Results okl_txl_ar_inv_lns_b

Overview

The table OKL_TXL_AR_INV_LNS_B is a core transaction table within the Oracle E-Business Suite (EBS) module OKL (Leasing and Finance Management). It serves as the primary repository for individual transaction lines that are designated for inclusion in invoices generated in Oracle Receivables (AR). This table acts as a critical integration point between the leasing operations managed in OKL and the financial invoicing and revenue recognition processes handled by the AR module. Each record represents a specific, billable line item—such as a rent charge, fee, or other contractual revenue stream—that is aggregated to form a complete customer invoice. Its status as a base table (indicated by the '_B' suffix) signifies it holds the fundamental transactional data, upon which other views or entities may be built.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the primary and foreign key relationships define its critical structural elements. The table's primary key is the ID column, uniquely identifying each invoice line. Essential foreign key columns establish its operational context. The KLE_ID links the line to its source contract line in the OKL_K_LINES table. The TAI_ID associates the line with a parent invoice header in the OKL_TRX_AR_INVOICES_B table. The STY_ID connects the line to a stream type definition in OKL_STRM_TYPE_B, classifying the nature of the charge (e.g., rent, interest). Additional columns like TIL_ID_REVERSES manage adjustments and reversals by linking to other records within the same table, while TPL_ID and ACN_ID_COST provide links to related payables lines and asset condition costs, respectively.

Common Use Cases and Queries

This table is central to billing, reporting, and reconciliation processes. A common operational use case is tracing the composition of a specific invoice issued to a lessee. For reporting, analysts query this table to summarize billed revenue by stream type, contract, or period. Technical consultants often reference it to debug invoice generation errors or to create custom integrations. A typical query pattern involves joining to the invoice header and contract lines to retrieve a detailed invoice line report:

• SELECT til.id, til.kle_id, kln.line_number, til.tai_id, inv.invoice_number, sty.name stream_type FROM okl_txl_ar_inv_lns_b til, okl_k_lines kln, okl_trx_ar_invoices_b inv, okl_strm_type_b sty WHERE til.kle_id = kln.id AND til.tai_id = inv.id AND til.sty_id = sty.id AND inv.invoice_number = 'INV-12345';

Another critical use case involves identifying reversed or adjusted lines by querying the self-referencing TIL_ID_REVERSES column.

Related Objects

The table maintains extensive relationships with other key OKL entities, as documented by its foreign keys. Key dependencies include:

• OKL_TRX_AR_INVOICES_B: The parent invoice header (via TAI_ID).
• OKL_K_LINES: The source leasing contract line (via KLE_ID).
• OKL_STRM_TYPE_B: The type of revenue stream being invoiced (via STY_ID).
• OKL_TXL_AR_INV_LNS_B (Self-Reference): For reversal transactions (via TIL_ID_REVERSES).
• OKL_TXL_AP_INV_LNS_ALL_B: For associated payables lines (via TPL_ID).
• OKL_AST_CNDTN_LNS_ALL_B: For asset condition cost lines (via ACN_ID_COST).
• OKL_TXL_ADJSTS_LNS_B / OKL_TXL_ADJSTS_LNS_ALL_B: For adjustment lines (via TIL_ID).
• OKL_TXD_AR_LN_DTLS_B: For additional line detail records (via TIL_ID_DETAILS).
• OKL_XTL_SELL_INVS_B: For sell invoice transactions (via TIL_ID).