Search Results okl_pool_types_v




Overview
Explore in AI Chat

Overview

OKL_POOL_TYPES_V is a VALID, APPS-owned entity view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, delivered under the OKL product family (Oracle Lease and Finance Management). The view is a thin, single-table projection defined over the OKL_POOL_TYPES base object and is documented in the ETRM repository as the "Entity view for OKL_POOL_TYPES." Its purpose is to expose pool type master data — the classification records that group leases, contracts, and financed assets into pools for accounting, reporting, and portfolio-level processing — through a stable, security-consistent read interface. Because the view is owned by APPS and carries WHO audit columns, it participates in Oracle EBS multi-org and audit conventions, allowing reporting tools, concurrent programs, and external integrations to consume pool type definitions without binding directly to the underlying base table. It is a read-oriented object intended for query and extraction rather than transactional maintenance, which is typically performed through the OKL application forms and APIs.

Underlying Base Objects

The documented metadata identifies exactly one referenced base object: the synonym OKL_POOL_TYPES (which resolves to the OKL base table of the same name in the OKL schema). The view text confirms this relationship precisely — it is a straightforward SELECT ... FROM OKL_POOL_TYPES POT with every column aliased from the base table alias POT. There is no join, union, aggregation, or filter predicate: the view is a one-to-one column mapping over the base table. Consequently, the cardinality of OKL_POOL_TYPES_V equals that of the base table, and no data transformation or derivation occurs. Any row visible in the base object is visible through the view, subject to synonyms and grants applied to APPS. Because the definition includes OBJECT_VERSION_NUMBER, the view supports Oracle EBS optimistic-locking semantics for any OAF-based or programmatic consumer that reads through it.

Key Columns

  • ID — Primary identifier of the pool type record; the key used for joins to related OKL pool, contract, and asset tables.
  • CODE — Business-meaningful short code for the pool type, used as the user-facing reference in transactions and reports.
  • DESCRIPTION / SHORT_DESCRIPTION — Full and abbreviated descriptive text for the pool type.
  • FROM_DATE / TO_DATE — Effective dating of the pool type, supporting date-ranged validation and historical reporting.
  • OBJECT_VERSION_NUMBER — Optimistic-locking token used by OAF and programmatic updates.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle descriptive flexfield (DFF) columns, exposing customer-defined pool type attributes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns recording record creation and modification metadata.

Common Use Cases and Queries

The view is principally used to populate LOVs, validations, and extract feeds for pool-based leasing processes. A representative query follows:

  • Active pool types: SELECT code, description FROM okl_pool_types_v WHERE TRUNC(SYSDATE) BETWEEN NVL(from_date, SYSDATE) AND NVL(to_date, TRUNC(SYSDATE));
  • Full lookup extract: SELECT id, code, short_description FROM okl_pool_types_v ORDER BY code;
  • DFF reporting: SELECT code, attribute_category, attribute1, attribute2 FROM okl_pool_types_v WHERE attribute_category IS NOT NULL;
  • Integration staging: selecting ID, CODE, OBJECT_VERSION_NUMBER, and WHO columns to reconcile pool type records against an external lease portfolio system.

These patterns reflect the view's role as the sanctioned read surface for pool type reference data across Oracle EBS 12.1.1 and 12.2.2.