Search Results okl_pool_transactions




Overview
Explore in AI Chat

Overview

The OKL_POOL_TRANSACTIONS table is a core transactional entity within Oracle E-Business Suite's Leasing and Finance Management module (OKL). It serves as the system of record for all financial and administrative activities related to asset pools. In leasing and asset finance, assets are often aggregated into pools for purposes of securitization, risk management, or collective administration. This table captures the discrete events that affect the composition, valuation, or status of these pools, such as the addition or removal of contracts, principal payments, interest accruals, or fee assessments. Its role is to provide a complete, auditable history of all pool-level financial movements, which is essential for portfolio reporting, accounting entries, and compliance.

Key Information Stored

While the provided metadata does not list all columns, the primary and unique key constraints define the table's critical identifiers. The primary key is the ID column, a system-generated unique identifier for each transaction record. The table also enforces a unique constraint on the TRANSACTION_NUMBER column, indicating this is a business-facing identifier for the transaction, likely following a specific numbering convention. A fundamental foreign key column is POL_ID, which links each transaction to its parent pool in the OKL_POOLS_ALL table. Typical data stored would include the transaction date, type, amount, effective period, status, and references to the underlying financial instruments or contracts that are the subject of the transaction.

Common Use Cases and Queries

A primary use case is generating a complete audit trail for a specific asset pool. Financial analysts run queries to reconcile pool balances or to prepare reports for investors and regulators. Accountants use the data to drive the creation of journal entries for pool-related revenue and expenses. A common reporting query would join to the pools table to summarize transactions within a date range.

  • Sample Query (Transaction History): SELECT pox.transaction_number, pox.transaction_date, pox.transaction_type, pox.amount, pol.name pool_name FROM okl_pool_transactions pox, okl_pools_all pol WHERE pox.pol_id = pol.id AND pol.id = :p_pool_id ORDER BY pox.transaction_date;
  • Use Case: Identifying all transactions that added contracts to a pool for a securitization process.
  • Use Case: Calculating the total principal collected across all pools for a given period by summing transaction amounts filtered by transaction type.

Related Objects

The table sits at the center of a key data model for pool management. Its documented relationships are as follows:

  • Parent Table (Foreign Key): OKL_POOLS_ALL. Each transaction must be associated with a single pool. The join is made on OKL_POOL_TRANSACTIONS.POL_ID = OKL_POOLS_ALL.ID.
  • Child Table (Referenced by Foreign Key): OKL_POOL_CONTENTS. This table, which tracks the specific assets or contracts within a pool, references individual pool transactions. The relationship is OKL_POOL_CONTENTS.POX_ID = OKL_POOL_TRANSACTIONS.ID. This link allows the system to know which transaction (e.g., an "Add" transaction) was responsible for placing a specific item into the pool.