Results for “okl_pool_srch_v”

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

Overview

OKL_POOL_SRCH_V is a reporting and search view owned by the APPS schema in Oracle Lease and Finance Management (OKL), part of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description, "Securitization - Pool search view," identifies its purpose: it consolidates the contract, customer, asset, and cash-flow stream attributes required to identify and evaluate lease contracts and their associated assets for securitization pool processing. The view is registered as VALID and is intended for inquiry and integration use rather than transactional maintenance.

Securitization in OKL requires assembling a pool of eligible leases, then analyzing their yield, classification, residual position, and cash-flow schedules. OKL_POOL_SRCH_V exposes exactly those attributes in a single denormalized row set, allowing users and downstream processes to search for candidate pool members without joining the four separate pool inquiry views manually. It complements the underlying pool inquiry views and supports the investigation of metrics such as PRE_TAX_YIELD, the column most directly associated with the search term referenced above.

Underlying Base Objects

The view is defined over four documented view objects, joined on the contract identifier (DNZ_CHR_ID) and the asset line identifier (KLE_ID):

• OKL_POOL_CUSTOMERS_UV — supplies customer and lessee attributes such as LESSEE, SIC_CODE, and CUST_OBJECT1_ID1.
• OKL_POOL_CONTRACTS_UV — supplies contract-level data including CONTRACT_NUMBER, PRE_TAX_YIELD, BOOK_CLASSIFICATION, PDT_ID, ASSIGNABLE_YN, STS_CODE, START_DATE, END_DATE, OPERATING_UNIT, CURRENCY_CODE, AUTHORING_ORG_ID, and TAX_OWNER.
• OKL_POOL_ASSETS_UV — supplies asset detail including ASSET_ID, ASSET_NUMBER, MODEL_NUMBER, MANUFACTURER_NAME, ITEM_ID1, VENDOR_ID1, OEC, RESIDUAL_PERCENTAGE, and KLE_ID.
• OKL_POOL_STREAMS_UV — supplies payment stream data including STY_ID, STREAM_TYPE_CODE, STREAM_TYPE_NAME, STREAM_TYPE_SUBCLASS, STREAM_SAY_CODE, STREAM_ACTIVE_YN, stream element due dates and amounts, and STM_ID.

The documented join condition is: POKS.DNZ_CHR_ID = POCS.DNZ_CHR_ID AND POKS.DNZ_CHR_ID = POAS.DNZ_CHR_ID AND POAS.KLE_ID = POST.KLE_ID. Because the streams join is at asset-line level, a contract with multiple asset lines and multiple streams produces a multiplied row set. OKL_ACCOUNTING_UTIL (PACKAGE) is also listed as a referenced base object, indicating the view's dependency chain reaches into accounting utility logic used by the underlying inquiry views.

Key Columns

• PRE_TAX_YIELD — the contract's pre-tax yield, a primary securitization screening metric used to compare and rank candidate leases.
• DNZ_CHR_ID / CONTRACT_NUMBER — the internal contract identifier and user-facing contract number.
• KLE_ID / ASSET_ID / ASSET_NUMBER — the asset line and asset identifiers linking contract to equipment.
• LESSEE / SIC_CODE — customer name and industry classification, useful for concentration analysis.
• BOOK_CLASSIFICATION / PDT_ID / TAX_OWNER — lease classification and product/tax ownership attributes affecting securitization eligibility.
• RESIDUAL_PERCENTAGE / OEC — residual position and original equipment cost for valuation.
• STREAM_TYPE_CODE / STREAM_ELEMENT_AMOUNT / STREAM_ELEMENT_DUE_DATE — payment stream type and scheduled cash flows.
• START_DATE / END_DATE / CURRENCY_CODE / OPERATING_UNIT — term and organizational context.

Common Use Cases and Queries

Typical usage includes identifying contracts that satisfy yield thresholds, aggregating residual exposure by lessee or SIC code, and extracting stream schedules for a selected pool. A representative query filtering on the yield metric is:

• SELECT CONTRACT_NUMBER, LESSEE, PRE_TAX_YIELD, BOOK_CLASSIFICATION, RESIDUAL_PERCENTAGE FROM OKL_POOL_SRCH_V WHERE PRE_TAX_YIELD >= 8 ORDER BY PRE_TAX_YIELD DESC;
• SELECT OPERATING_UNIT, CURRENCY_CODE, COUNT(DISTINCT DNZ_CHR_ID) CONTRACTS FROM OKL_POOL_SRCH_V GROUP BY OPERATING_UNIT, CURRENCY_CODE;

Because the view carries no bind variables or organization security enforcement of its own, callers should apply operating unit and ledger filters explicitly using OPERATING_UNIT and AUTHORING_ORG_ID, and should deduplicate on DNZ_CHR_ID when contract-level rather than asset-line-level results are required.