Search Results okl_pool_contents




Overview
Explore in AI Chat

Overview

The OKL_POOL_CONTENTS table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It functions as the detailed transaction and composition ledger for asset pools. In leasing and finance operations, assets such as contracts or individual payment streams are often aggregated into pools for purposes like securitization, risk management, or portfolio analysis. This table stores the granular records that define which specific financial components (like lines, streams, or contracts) belong to a given pool at any point in time, tracking their entry and exit via transaction numbers. Its role is critical for maintaining the integrity and audit trail of pool compositions, directly supporting complex financial structuring and reporting.

Key Information Stored

The table's structure is designed to link a pool member to its parent pool and identify the specific financial object. Key columns, as indicated by the primary and unique keys, include the unique identifier (ID), the pool identifier (POL_ID), and references to the specific leased asset components: the contract header (KHR_ID), line (KLE_ID), and stream type (STY_ID). The TRANSACTION_NUMBER_IN and TRANSACTION_NUMBER_OUT columns are vital for tracking the lifecycle of the pool member, recording the transaction IDs that added or removed the component. Foreign key relationships point to critical master and transaction tables, ensuring referential integrity for the stream (STM_ID), the pool transaction header (POX_ID), the pool itself, the contract line, and the stream type.

Common Use Cases and Queries

This table is central to queries that analyze pool composition, track asset movement, and support audit reports. Common operational scenarios include generating a list of all active contracts within a specific pool for a valuation report, identifying all components added to pools during a specific period for transaction reconciliation, or verifying the history of a particular contract line across different pools. A typical query pattern involves joining OKL_POOL_CONTENTS with OKL_POOLS_ALL and contract tables like OKL_K_LINES.

  • Sample Query (Pool Composition): SELECT pc.khr_id, pc.kle_id, p.pool_name FROM okl_pool_contents pc, okl_pools_all p WHERE pc.pol_id = p.id AND p.id = :pool_id AND pc.transaction_number_out IS NULL;
  • Use Case: This identifies all currently active components (those not yet removed) within a specified pool, which is fundamental for portfolio exposure analysis.

Related Objects

OKL_POOL_CONTENTS sits at the intersection of several key OKL entities. Its primary foreign key relationships define its dependencies:

  • OKL_POOLS_ALL: The master table for pool definitions, linked via POL_ID.
  • OKL_K_LINES: The contract lines table, linked via KLE_ID, identifying the specific leased asset line item in the pool.
  • OKL_POOL_TRANSACTIONS: The transaction header table, linked via POX_ID, providing the context for the entry/exit transaction.
  • OKL_STREAMS and OKL_STRM_TYPE_B: The cash flow stream and stream type tables, linked via STM_ID and STY_ID, detailing the financial payment obligations associated with the pool component.

These relationships make OKL_POOL_CONTENTS essential for any process or report that requires tracing the lineage between a financial pool and its underlying contractual assets.