Search Results poc_id




Overview
Explore in AI Chat

Overview

OKL_POOL_TRANS_CONTENTS_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, belonging to the OKL – Leasing and Finance Management product family. Its purpose is to present the contents of securitization pool transactions in a denormalized, user-friendly format suitable for reporting, integration, and OAF-based inquiry pages. Securitization pools group lease and finance contracts whose cash flows are packaged for financing arrangements, and the view answers the operational question of which contracts, assets, lessees, and streams belong to a given pool, together with the transaction numbers flowing in and out of the pool.

Because the view resolves foreign keys to descriptive names (lessee party name, asset number, stream type name, and lookup meanings), it eliminates the need for report developers and integrators to re-implement the underlying join logic. This makes it a convenient single source for pool transaction content reporting in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a join of transactional, contract, party, and lookup objects:

Additional documented references include FND_GLOBAL and OKL_ACCOUNTING_UTIL packages, which support session context and accounting logic within the OKL stack.

Key Columns

Common Use Cases and Queries

Typical scenarios include pool reconciliation reports, securitization audit extracts, and OAF inquiry pages filtering on pool, contract, or stream subclass. A representative query:

  • SELECT poc_id, contract_number, asset_number, lessee, stream_type_name, sty_subclass_code, sty_subclass, streams_from_date, streams_to_date FROM okl_pool_trans_contents_uv WHERE sty_subclass_code = :p_subclass AND status_code = 'ACTIVE';
  • Filtering by pol_id to list all contracts and assets within a specific securitization pool.
  • Joining to OKL_POOLS to aggregate stream amounts by pool for financing disclosure reporting.

The view is read-only and intended for query use; it should not be treated as a base table for DML operations.