Search Results okl_txd_ar_ln_dtls_b

Overview

The table OKL_TXD_AR_LN_DTLS_B is a core transaction staging table 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 a critical data repository for detailed line-level information that is destined for integration into Oracle Receivables (AR) invoices. The table's primary function is to hold the granular transactional data—such as billing line details, adjustments, and stream elements—that is aggregated and processed to create final invoice lines in the AR module. This object is fundamental to the order-to-cash cycle for lease and finance contracts, acting as a bridge between the specialized calculations of the OKL module and the standardized invoicing processes of Oracle Receivables.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key relationships and description clearly indicate the nature of the data stored. The table's primary key is the ID column. Crucially, it stores foreign key references to various source objects, allowing it to link invoice line details back to their originating transactions. Based on the documented foreign keys, the table holds identifiers for billing contract lines (BCL_ID), billing sub-lines (BSL_ID), stream elements (SEL_ID), indices (IDX_ID), and stream types (STY_ID). It also maintains relationships to adjustment lines (via TLD_ID) and to the parent transaction invoice lines (TIL_ID_DETAILS). A key column is BCH_ID, which likely groups detail lines into a batch for processing. The presence of a TLD_ID_REVERSES self-referencing foreign key suggests the table also manages reversal transactions for audit and correction purposes.

Common Use Cases and Queries

This table is central to troubleshooting and reporting on the invoice generation process for lease contracts. Common operational scenarios include diagnosing why specific billing lines failed to appear on an invoice, reconciling billed amounts to source contract calculations, and auditing adjustment histories. A typical query would join this table to its related source tables to trace invoice line details back to the original contract data. For example, to analyze details pending invoicing for a specific batch, one might use a SQL pattern such as: SELECT tld.*, bcl.amount FROM OKL_TXD_AR_LN_DTLS_B tld JOIN OKS_BILL_CONT_LINES bcl ON tld.BCL_ID = bcl.ID WHERE tld.BCH_ID = :batch_id;. Reporting use cases often involve aggregating data from this table by stream type, customer, or contract to provide pre-invoice summaries and revenue recognition support.

Related Objects

The table maintains extensive relationships with other OKL transactional objects, as evidenced by its foreign keys. Key related tables include:

• OKS_BILL_CONT_LINES and OKS_BILL_SUB_LINES: Source billing line details are linked via BCL_ID and BSL_ID.
• OKL_STRM_ELEMENTS and OKL_STRM_TYPE_B: Links to the accounting stream components (SEL_ID) and their types (STY_ID) being invoiced.
• OKL_TXL_AR_INV_LNS_B: The parent invoice line table is referenced via TIL_ID_DETAILS.
• OKL_TXL_ADJSTS_LNS_B and OKL_TXL_ADJSTS_LNS_ALL_B: Adjustment transactions are linked via TLD_ID.
• OKL_XTL_SELL_INVS_B: Indicates a relationship with sell invoice transactions.
• Self-Reference: The table has a recursive relationship on TLD_ID_REVERSES to track reversing entries.

These relationships form the backbone of the invoice line detail staging and processing workflow within Oracle Lease Management.