Results for “pol_id”

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

Overview

The OKL_SEC_BUYBACK_STREAMS_UV view is a user interface (UI) view owned by the APPS schema within the OKL – Leasing and Finance Management module of Oracle E-Business Suite. Its documented purpose is to present securitized buyback streams. In operational terms, the view consolidates contract, pool, party, and stream element data into a single denormalized result set suitable for display in an Oracle Forms or OAF-based inquiry window, and equally usable as a reporting or integration source.

The view answers a specific business question: for each active pool content line associated with a buyback stream, what are the future (unbilled) stream element amounts attributable to a securitized agreement? Because it filters on SELB.DATE_BILLED IS NULL and a future STREAM_ELEMENT_DATE, the view is inherently forward-looking, exposing only amounts that remain to be billed within the pool content's effective stream date range. This makes it the natural driver for buyback projection screens and downstream securitization feeds.

Underlying Base Objects

The view joins ten base objects. Lease and contract identification is supplied by OKC_K_HEADERS_ALL_B, which is aliased twice, once as CHRB for the lessee contract and once as AGRB for the agreement. Party identity flows through OKC_K_PARTY_ROLES_B and HZ_PARTIES, restricted to the LESSEE role. The securitization and pooling layer is represented by OKL_POOL_CONTENTS, which links contracts to pools, and OKL_POOLS, which supplies the pool header including the POOL_NUMBER and the pool's agreement KHR_ID.

Stream data is drawn from OKL_STREAMS, OKL_STRM_ELEMENTS, and OKL_STRM_TYPE_V, with OKL_STRM_TYPE_V resolving the stream type subclass. Decoding of the subclass into a user-readable meaning is performed by FND_LOOKUPS on lookup type OKL_STREAM_TYPE_SUBCLASS. The documented base object list also includes the FND_GLOBAL and OKL_ACCOUNTING_UTIL packages, which are referenced for session context and accounting utility logic rather than as table sources. All base tables are accessed through APPS synonyms, so the view is subject to standard MOAC and security constraints applied by the calling form or report.

Key Columns

• KHR_ID – Contract header identifier from the pool content record; the primary linkage back to the lease.
• CONTRACT_NUMBER – Lessee contract number (CHRB.CONTRACT_NUMBER), used as the leading sort key.
• CURRENCY_CODE – Currency of the contract, carried from the contract header.
• LESSEE – Party name of the lessee, resolved via the LESSEE role on the contract.
• POL_ID – Pool identifier from OKL_POOL_CONTENTS.
• POOL_NUMBER – Pool number from OKL_POOLS; this is the item most often searched for, since users begin from a known pool and work outward to the contracts it contains.
• AGREEMENT_ID / AGREEMENT_NUMBER – Header ID and contract number of the agreement associated with the pool.
• STY_SUBCLASS_CODE / STY_SUBCLASS – Stream type subclass code and its decoded lookup meaning, serving as the secondary sort key.
• STREAMS_AMOUNT – Aggregate of OKL_STRM_ELEMENTS.AMOUNT for qualifying future, unbilled stream elements, coalesced to zero when no rows exist.

Common Use Cases and Queries

The principal use case is pool-centric inquiry: a user knows a pool number and needs the securitized buyback streams it contains. Because the view already restricts to active pool contents, unbilled elements, and future stream element dates within the pool content's date range, no additional business filtering is generally required.

SELECT contract_number, lessee, pool_number,
       agreement_number, sty_subclass, streams_amount
  FROM apps.okl_sec_buyback_streams_uv
 WHERE pool_number = :p_pool_number
 ORDER BY contract_number, sty_subclass;

A second common pattern aggregates by pool to obtain a portfolio-level total of remaining buyback exposure, which is useful for reconciliation against securitization schedules or for feeding a data warehouse extract:

SELECT pool_number, currency_code,
       COUNT(DISTINCT contract_number) contracts,
       SUM(streams_amount) total_buyback
  FROM apps.okl_sec_buyback_streams_uv
 GROUP BY pool_number, currency_code
 ORDER BY pool_number;

A third pattern drives from the lessee or from a specific stream subclass, for example isolating all future buyback amounts of a given subclass across every pool to which a contract has been assigned. Because sorting is applied as ORDER BY CONTRACT_NUMBER, STREAM_TYPE_SUBCLASS, results arrive naturally grouped by contract and subclass, which suits direct display in a multi-record block or a formatted report. Users should note that STREAMS_AMOUNT is a conditional aggregate and may be zero for a contract and subclass that exist in the pool but hold no future unbilled elements.