Search Results okl_trx_contracts_all




Overview
Explore in AI Chat

Overview

The OKL_TRX_CONTRACTS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically for the OKL (Lease and Finance Management) product module. As documented, it serves as the primary header table for lease transactions. This table functions as the central repository for high-level information pertaining to financial transactions processed within the leasing and financing lifecycle, such as bookings, amendments, terminations, and settlements. Its role is critical for maintaining the integrity and audit trail of all contractual financial events, linking transactional data to the master lease contract, accounting rules, and associated quotes.

Key Information Stored

While the provided metadata does not list specific columns, the primary and foreign key relationships define its critical data points. The table's primary key is the ID column, uniquely identifying each transaction header record. Essential foreign key columns establish relationships to other master data entities. These include KHR_ID, linking the transaction to its originating lease contract in OKL_K_HEADERS, and TRY_ID, which associates the transaction with a specific type defined in OKL_TRX_TYPES_B. Other significant references are QTE_ID for related quotes (OKL_TRX_QUOTES_ALL_B), AES_ID for accounting event sets (OKL_AE_TMPT_SETS_ALL), and PDT_ID for product definitions (OKL_PRODUCTS). Columns like KHR_ID_NEW and KHR_ID_OLD are indicative of the table's role in tracking contract amendments or replacements.

Common Use Cases and Queries

This table is central to transaction reporting and process inquiries. A common use case is generating a summary report of all financial transactions for a specific lease contract or within a date range. Technical consultants often query this table to troubleshoot transaction flows or validate data integrity during month-end close or system integrations. A typical SQL pattern involves joining to related descriptive tables:

  • Identifying transactions for a contract: SELECT * FROM OKL_TRX_CONTRACTS_ALL WHERE KHR_ID = :contract_id.
  • Reporting transaction headers with their types: SELECT tc.id, tc.khr_id, tt.name FROM okl_trx_contracts_all tc, okl_trx_types_b tt WHERE tc.try_id = tt.id AND tc.creation_date > SYSDATE - 30.
  • Tracing the lineage of amended contracts by joining on KHR_ID, KHR_ID_OLD, and KHR_ID_NEW.

Related Objects

The table maintains documented foreign key relationships with several key OKL tables, forming the backbone of the transaction data model. The primary relationships, as per the metadata, are:

  • OKL_K_HEADERS: Joined via KHR_ID, KHR_ID_NEW, and KHR_ID_OLD. This is the most critical link, tethering every transaction to its lease contract.
  • OKL_TRX_TYPES_B: Joined via TRY_ID, providing the transaction type classification.
  • OKL_TRX_QUOTES_ALL_B: Joined via QTE_ID, linking to the originating quote for the transaction.
  • OKL_AE_TMPT_SETS_ALL: Joined via AES_ID, connecting to the accounting event template set for financial posting.
  • OKL_PRODUCTS: Joined via PDT_ID, referencing the financial product.
  • OKL_PROVISIONS: Joined via PVN_ID, linking to specific lease provisions.

As a header table, OKL_TRX_CONTRACTS_ALL is expected to have child detail tables (e.g., for lines, distributions) that reference its primary key (ID), though these are not listed in the provided excerpt.