Results for “okl_pools_v”

16 results




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

Overview

OKL_POOLS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). In the EBS 12.1.1 and 12.2.2 releases, this view presents a security-filtered projection of the OKL_POOLS base table, which stores the master records for leasing pools. A pool in OKL represents a grouping of contracts and related financial instruments assembled for syndication, securitization, investor reporting, or internal portfolio management purposes.

The view does not add calculated columns or joins; it exposes the pool record set as-is while applying an organizational security filter. Its primary role is to support inquiry screens, reports, and external interfaces that need to present pool data scoped to the operating unit (ORG_ID) of the current session, thereby enforcing multi-org data access rules consistently across the Leasing and Finance Management application.

Underlying Base Objects

The view is defined over a single base table, OKL_POOLS, aliased as POL. The ETRM metadata for release 12.2.2 documents no other referenced base objects, no additional joins, and no aggregation logic. The defining characteristic of OKL_POOLS_V is its WHERE clause, which filters rows by organizational context:

  • The predicate compares the table's ORG_ID column against a value derived from the client session information via USERENV('CLIENT_INFO').
  • It uses the standard multi-org pattern, extracting the first ten characters of CLIENT_INFO and converting them to a number.
  • NVL wrappers default both sides of the comparison to -99 when ORG_ID is null or the session value cannot be derived, which is the conventional method for allowing access to global (non-org-specific) rows.

Because no joins or functions are applied to the column list, the view is effectively a row-level secured synonym-like wrapper. The metadata notes that the object is not implemented in the reference database from which the documentation was generated, so it should be validated in the target environment against the OKL_POOLS table definition.

Key Columns

The view exposes the full column list of OKL_POOLS. The most significant columns, several of which are directly relevant to the "pot_id" search term, include:

Common Use Cases and Queries

Typical uses include pool inquiry reports, reconciliation of pool balances, integration extracts to downstream securitization systems, and cross-referencing pools to their pots via POT_ID. A basic query to retrieve pools for the current operating unit is:

  • SELECT pool_number, description, currency_code, total_principal_amount, status_code FROM okl_pools_v ORDER BY pool_number;

To locate the pool associated with a specific pot, query by POT_ID:

  • SELECT id, pool_number, pot_id, khr_id, status_code FROM okl_pools_v WHERE pot_id = :pot_id;

Because ORG_ID filtering depends on CLIENT_INFO, direct SQL*Plus sessions must initialize the client information (typically via the FND client-info initialization routine) before the view returns the intended rows; otherwise the default -99 comparison applies. Reports and OA Framework pages that run under an EBS session inherit this context automatically.