Search Results okl_trx_contracts




Overview
Explore in AI Chat

Overview

The OKL_TRX_CONTRACTS table is a core data object within the Oracle E-Business Suite (EBS) module OKL (Lease and Finance Management). It functions as the primary header table for lease and finance transaction processing. In the context of Oracle EBS 12.1.1 and 12.2.2, this table serves as the central repository for recording the essential metadata of a transaction, linking it to the underlying contract, transaction type, and related system entities. Its role is pivotal in orchestrating the financial and contractual lifecycle events, such as billing, adjustments, and modifications, by providing the header-level context for detailed line items stored in related tables.

Key Information Stored

While the provided metadata does not list specific columns, the foreign key relationships define the critical data linkages stored in the table. The primary identifier is the ID column, which is the primary key. The table's structure is designed to associate a transaction with its originating and related contracts via foreign keys to OKL_K_HEADERS (KHR_ID, KHR_ID_NEW, KHR_ID_OLD). It categorizes the transaction through TRY_ID linking to OKL_TRX_TYPES_B and ties it to a specific product definition via PDT_ID. Furthermore, it connects to supporting documents and system setups, such as quotes (QTE_ID), accounting event templates (AES_ID), and provisions (PVN_ID). This design ensures every transaction is fully contextualized within the leasing ecosystem.

Common Use Cases and Queries

This table is central to transaction inquiry and reporting. A common use case is tracing all financial transactions associated with a specific lease contract. For instance, to retrieve a summary of transactions for a contract, one might join to the contract header and transaction type tables. Another critical scenario is supporting the generation of accounting entries, where the header information in OKL_TRX_CONTRACTS is used to determine the correct accounting rules and natural accounts. A typical reporting query would follow this pattern:

  • SELECT tcn.id, tcn.trx_number, kh.contract_number, tt.name trx_type FROM okl_trx_contracts tcn, okl_k_headers kh, okl_trx_types_b tt WHERE tcn.khr_id = kh.id AND tcn.try_id = tt.id AND kh.contract_number = '<CONTRACT_NUM>';

It is also essential for reconciliation processes, linking header transactions to their detailed lines in OKL_TXL_CNTRCT_LNS or to specific AP/AR documents.

Related Objects

The foreign key metadata explicitly defines this table's central position in the OKL schema. Key related objects include:

  • OKL_K_HEADERS: The master lease contract table. Multiple foreign keys (KHR_ID, KHR_ID_NEW, KHR_ID_OLD) link a transaction to the original, old, and new contracts, supporting contract modifications and restructures.
  • OKL_TXL_CNTRCT_LNS: The transaction lines table, which holds the detailed line items for each header record in OKL_TRX_CONTRACTS.
  • OKL_TRX_TYPES_B: Defines the type of transaction (e.g., Invoice, Credit Memo, Adjustment).
  • OKL_TRX_AR_ADJSTS_B & OKL_TRX_AP_INVOICES_B: Specific transaction sub-type tables that reference the header for receivables adjustments and payables invoices, respectively.
  • OKL_TRX_QUOTES_B, OKL_PRODUCTS, OKL_PROVISIONS, OKL_AE_TMPT_SETS: Supporting tables that provide quote, product, provision, and accounting template data for the transaction.