Search Results okl_txl_cntrct_lns




Overview
Explore in AI Chat

Overview

The table OKL_TXL_CNTRCT_LNS is a core transactional data structure within the Oracle E-Business Suite (EBS) module OKL (Lease and Finance Management). It functions as the lease transactions line table, storing detailed line-level information for financial transactions associated with lease and finance contracts. This table is critical for capturing the granular accounting and financial impacts of contract activities, such as billing, revenue recognition, and cash application. Its role is to support the detailed accounting entries required for compliance and financial reporting by linking transaction lines to specific contract streams, accounting templates, and cash management batches.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the foreign key relationships define the essential data entities linked to each transaction line. The primary key is a unique identifier (ID). Each record is fundamentally tied to a lease contract via the KHR_ID, which references the OKL_K_HEADERS table. The table links the transaction line to its parent transaction header (TCN_ID in OKL_TRX_CONTRACTS) and categorizes the financial nature of the line through the stream type (STY_ID in OKL_STRM_TYPE_B). For accounting, it references an accounting template (AVL_ID in OKL_AE_TEMPLATES) and can be associated with a specific accounting bucket (BKT_ID in OKL_BUCKETS). Furthermore, it integrates with cash management by linking to cash batch (BTC_ID in OKL_TRX_CSH_BATCH_B) and cash receipt (RCT_ID in OKL_TRX_CSH_RECEIPT_B) records.

Common Use Cases and Queries

This table is central to transaction inquiry, reconciliation, and audit reporting. A common use case involves tracing the accounting impact of a specific contract activity. For instance, to retrieve all transaction lines for a particular contract to understand revenue or billing details, a query would join on KHR_ID. Another critical scenario is reconciling cash receipts applied to contracts, which involves joining on RCT_ID. Financial analysts may query this table joined with OKL_STRM_TYPE_B and OKL_AE_TEMPLATES to analyze the distribution of transaction amounts across different revenue or expense stream types for a period. A sample query pattern is:

  • SELECT txl.*, sty.name STREAM_TYPE
  • FROM okl_txl_cntrct_lns txl, okl_strm_type_b sty
  • WHERE txl.sty_id = sty.id
  • AND txl.khr_id = <contract_id>;

Related Objects

OKL_TXL_CNTRCT_LNS is a hub table with dependencies to several key entities in the OKL schema. Its primary relationship is with the contract header (OKL_K_HEADERS) and the transaction header (OKL_TRX_CONTRACTS). It draws its accounting rules from OKL_AE_TEMPLATES and OKL_BUCKETS. The stream type (OKL_STRM_TYPE_B) classifies each line. For cash management integration, it references OKL_TRX_CSH_BATCH_B and OKL_TRX_CSH_RECEIPT_B. The primary key constraint OKL_TXL_CNTRCT_LNS_PK enforces uniqueness on the ID column. Developers and integrators must consider these relationships when writing custom reports or interfaces to ensure data integrity.