Search Results pot_pk

Overview

The OKL_POOL_TYPES table is a foundational data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its primary function is to serve as a master reference table for categorizing and classifying asset or contract pools. In the context of leasing and finance operations, pools are logical groupings of assets or contracts, often used for portfolio management, securitization, risk assessment, and accounting processes. This table provides the standardized set of pool categories (types) that can be assigned to individual pool records, ensuring data consistency and enabling structured reporting and process execution based on pool classification.

Key Information Stored

The table's structure, as indicated by its primary and unique keys, is designed to uniquely identify each pool type. The most critical columns are the ID and CODE fields. The ID column (POT_ID) is the system-generated, numeric primary key used for all internal relationships and foreign key references. The CODE column holds a unique, typically short, alphanumeric identifier for the pool type, which is likely used within application logic and user interfaces. While the provided metadata does not list all columns, a typical configuration table like this would also include descriptive columns such as NAME and DESCRIPTION, along with standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and a START_DATE/END_DATE for enabling and disabling types.

Common Use Cases and Queries

The primary use case is to validate and constrain the types of pools that can be created in the system. When a user defines a new pool in the OKL_POOLS or OKL_POOLS_ALL table, they must select a valid type from OKL_POOL_TYPES. This classification then drives downstream business rules. Common reporting and query scenarios include listing all active pool types or analyzing the distribution of pools by type. Sample SQL patterns include:

• Basic lookup: SELECT code, name FROM okl_pool_types WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE) ORDER BY code;
• Joining to pool details: SELECT p.pool_number, pt.name as pool_type FROM okl_pools_all p, okl_pool_types pt WHERE p.pot_id = pt.id;
• Counting pools by type: SELECT pt.code, COUNT(p.id) FROM okl_pools p, okl_pool_types pt WHERE p.pot_id = pt.id GROUP BY pt.code;

Related Objects

As documented in the foreign key relationships, OKL_POOL_TYPES is directly referenced by the main pool tables. The OKL_POOLS_ALL table (the multi-org table) and its synonym OKL_POOLS both contain a POT_ID column, which is a foreign key to OKL_POOL_TYPES.ID. This means every record in these pool tables is explicitly linked to a single, valid record in the OKL_POOL_TYPES table. This relationship is fundamental to the data model. While not listed in the excerpt, other related objects may include application forms, views (like OKL_POOLS_V), and public APIs (such as OKL_POOL_PVT) that manage pool creation and maintenance, all of which would enforce or utilize the pool type classification.