Results for “okl_pools”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_POOLS is the securitization pool header table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It stores the master record for each securitization pool, representing a grouping of lease contracts or financial assets that are bundled together for securitization, financing, or investor reporting purposes. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the parent container that ties together contract header information and pool type definitions used throughout the leasing securitization workflow.

Based on the documented foreign key structure, the metadata classifies OKL_POOLS heuristically as a link in Data Vault modeling terms. This is a reasonable modeling suggestion: the table sits between OKL_K_HEADERS (lease/contract headers) and OKL_POOL_TYPES (pool classifications), carrying the associations that define which contracts belong to which pool categories. The table also carries descriptive attributes that would make it a hub-lite or link-with-attributes candidate depending on design conventions.

Key Information Stored

The documented metadata confirms the following key columns and structural attributes:

• POL_PK (ID) — The surrogate primary key uniquely identifying each pool header record. This is the system-generated identifier and the reference target for any child tables attached to a pool.
• POOL_NUMBER — The business key. The unique index POL_POL_UK enforces uniqueness on POOL_NUMBER alone, making it the user-facing identifier for a securitization pool.
• KHR_ID — Foreign key to OKL_K_HEADERS. Associates the pool with a contract or header-level record in the leasing module, anchoring the pool to its underlying lease instruments.
• POT_ID — Foreign key to OKL_POOL_TYPES. Classifies the pool by its securitization type, governing the rules applied to pool composition and reporting.

The distinctive feature of this metadata is the dual uniqueness guarantee: POL_PK as a technical surrogate key and POOL_NUMBER as the business-key candidate constrained by POL_POL_UK. Any reporting or integration logic should treat POOL_NUMBER as the stable external identifier and POL_PK as the internal join key.

Implementation note: the metadata explicitly states "Not implemented in this database," indicating that OKL_POOLS exists in the data model but is only instantiated when the Securitization feature is licensed and configured. In many installations the table will be empty or absent from the physical schema.

Common Use Cases and Queries

Typical usage centers on pool composition reporting, contract-to-pool assignment validation, and reconciliation of securitization structures. A standard join pattern retrieves the pool with its type and header context:

• List all active pools by type: SELECT p.POOL_NUMBER, pt.name FROM OKL_POOLS p, OKL_POOL_TYPES pt WHERE p.POT_ID = pt.POT_ID;
• Identify contracts linked to a pool: SELECT k.* FROM OKL_K_HEADERS k, OKL_POOLS p WHERE p.KHR_ID = k.KHR_ID AND p.POOL_NUMBER = :pool_num;
• Locate a pool by business key using the unique index: SELECT * FROM OKL_POOLS WHERE POOL_NUMBER = :pool_num;

Because the table is a header, most reporting joins outward to detail tables rather than aggregating here. It is frequently used as the starting point for securitization audit trails and for validating that each pool type is applied consistently across contract assignments.

Related Objects

The following tables are the most significant given the documented relationships:

• OKL_K_HEADERS — Joined via OKL_POOLS.KHR_ID = OKL_K_HEADERS.KHR_ID. The contract header holding lease instrument details.
• OKL_POOL_TYPES — Joined via OKL_POOLS.POT_ID = OKL_POOL_TYPES.POT_ID. Defines the pool classification.

Beyond these, detail tables in the OKL securitization schema (pool lines, pool-to-contract assignments) typically reference POL_PK through POL_PK = POL_FK relationships, though such children are not documented in the supplied metadata. Integrations extracting pool data should always resolve POOL_NUMBER via the POL_POL_UK index for performance, and treat POL_PK as the internal referential anchor.