Results for “okl_pool_types”

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

Overview

OKL_POOL_TYPES is a reference (setup) table in the Oracle Leasing and Finance Management (OKL) module, which is part of the Oracle E-Business Suite. Its documented description is "Categorization of pools," indicating that it defines the classification or type hierarchy applied to leases, contracts, and financial pools managed within OKL. Each row represents a pool type that can later be assigned to pool records, driving grouping, reporting, and accounting behavior across the leasing lifecycle.

From a Data Vault modeling perspective, the mined FK structure classifies OKL_POOL_TYPES as hub-leaning. This suggests that the table functions as a durable business hub of distinct pool-type identities, referenced by dependent transactional or detail tables, rather than as a link or satellite. In practice, this reinforces its role as a stable reference entity whose rows persist over time and are pointed to by foreign keys in pool-level tables.

Key Information Stored

The table is physically owned by the OKL schema and contains 28 documented columns. The most important among these are:

• ID — the surrogate primary key (POT_PK). It also anchors the unique index OKL_POOL_TYPES_U1, making it the primary business-key candidate from an indexing standpoint.
• CODE — the user-facing unique business key (POT_POL_UK). This is the value typically exposed to users when selecting a pool type.
• DESCRIPTION and SHORT_DESCRIPTION — long and abbreviated text labels used in lookups, forms, and reports.
• FROM_DATE and TO_DATE — effective-dating columns that bound the active validity window of each pool type.
• OBJECT_VERSION_NUMBER — the optimistic-locking versioning column used by the Oracle Applications Framework (OAF) and concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the mandatory DFF (Descriptive Flexfield) segment columns that allow customer-specific extension of the pool-type definition without schema changes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard WHO (audit) columns capturing creation and last-modification metadata.

The surrogate ID (POT_PK) should be used for all referential joins, while CODE serves as the unique business identifier (POT_POL_UK). Practical queries typically filter on CODE and DESCRIPTION for lookups and on the FROM_DATE/TO_DATE range to isolate currently effective types.

Common Use Cases and Queries

The table is primarily consumed for validation, lookup, and reporting. A typical lookup to retrieve all currently effective pool types is:

• SELECT ID, CODE, DESCRIPTION FROM OKL.OKL_POOL_TYPES WHERE TRUNC(SYSDATE) BETWEEN FROM_DATE AND NVL(TO_DATE, SYSDATE);

A common join pattern resolves the pool type for each pool record:

• SELECT p.ID pool_id, t.CODE pool_type_code, t.DESCRIPTION pool_type_desc FROM OKL.OKL_POOLS p, OKL.OKL_POOL_TYPES t WHERE p.POT_ID = t.ID;

Reporters frequently aggregate pool counts or balances grouped by pool type code to compare portfolio composition across categories. DFF columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) support client-specific segmentation reporting when standard CODE granularity is insufficient. Because the table is reference data, changes should be made through the OKL setup UI rather than direct DML to preserve flexfield validation and audit integrity.

Related Objects

OKL_POOL_TYPES sits at the head of a small hub-style cluster in the OKL schema. Documented foreign-key relationships include:

• OKL_POOLS_ALL — references OKL_POOL_TYPES via OKL_POOLS_ALL.POT_ID. Stores the full pool definition including type assignment.
• OKL_POOLS — references OKL_POOL_TYPES via OKL_POOLS.POT_ID, providing pool-level detail joined to its pool type.

Additional OKL objects that logically depend on this reference table include pool-related DFF/value-set configurations (ATTRIBUTE_CATEGORY), OKL concurrent programs that populate and validate pool data, and the OKL Leasing setup forms that drive pool-type creation and maintenance. Together these objects form the controlling reference layer for pool classification across Oracle Leasing and Finance Management.