Results for “okl_pool_contents_v”

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

Overview

OKL_POOL_CONTENTS_V is a reporting and integration view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module. Its documented purpose is to serve as an entity view for the OKL_POOL_CONTENTS base table, exposing that table's columns in a stable, named form suitable for forms, concurrent programs, and external interfaces in Oracle E-Business Suite 12.1.1 and 12.2.2. In the ETRM object registry the view carries a status of VALID, confirming it is compiled and available at runtime.

The view is a thin projection: it performs no joins, aggregation, or filtering, and simply renames the columns of the underlying table to the same names using a table alias (POC). Its role is therefore one of encapsulation. By directing consumers to OKL_POOL_CONTENTS_V rather than to the base table directly, Oracle preserves the ability to evolve the physical implementation of pool contents without breaking dependent code.

Underlying Base Objects

The view is defined exclusively over OKL_POOL_CONTENTS, referenced through the APPS synonym of the same name. The complete view text is a single SELECT over that one object with no WHERE clause, no set operators, and no outer joins:

• FROM OKL_POOL_CONTENTS POC — the sole documented base object.
• The view selects all columns of the base table aliased as POC, including the identifier, foreign keys, descriptive codes, dates, descriptive flexfield attributes, and the standard WHO audit columns.
• No other tables, views, or functions are referenced, so row-for-row cardinality between the view and the base table is preserved.

Key Columns

Given that the user search term was "sty_code", the STY_CODE column is central. It is a descriptive code carried on the pool contents record, stored alongside the surrogate foreign key STY_ID, and is typically the value used in list-of-values and report output because it is human-readable while STY_ID is not. Other significant columns include:

• ID and OBJECT_VERSION_NUMBER — primary key and optimistic locking version for the row.
• POL_ID — identifies the owning pool (OKL_POOLS) to which the content line belongs.
• KHR_ID, KLE_ID, STM_ID, POX_ID — foreign keys linking the content line to the associated contract, lease, stream, and related entity records.
• STY_ID / STY_CODE — the stream type identifier and its decoded code, determining the nature of the cash flow represented.
• STREAMS_FROM_DATE / STREAMS_TO_DATE — the effective date range for the stream content.
• TRANSACTION_NUMBER_IN / TRANSACTION_NUMBER_OUT — sequencing control values used when pool contents move into or out of the pool.
• DATE_INACTIVE, STATUS_CODE — lifecycle indicators used to filter active content.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments for client-specific extensions.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context for the creating process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes reporting the contents of a lease pool, verifying stream type coding, and feeding downstream integration extracts. A representative query filtered on stream type code, which matches the user's search term, is:

• SELECT poc.id, poc.pol_id, poc.khr_id, poc.kle_id, poc.sty_code, poc.streams_from_date, poc.streams_to_date, poc.status_code FROM apps.okl_pool_contents_v poc WHERE poc.sty_code = :sty_code AND poc.date_inactive IS NULL ORDER BY poc.streams_from_date;
• SELECT poc.sty_code, COUNT(*) FROM apps.okl_pool_contents_v poc WHERE poc.pol_id = :pol_id GROUP BY poc.sty_code;
• SELECT poc.id, poc.transaction_number_in, poc.transaction_number_out, poc.creation_date FROM apps.okl_pool_contents_v poc WHERE poc.date_inactive IS NULL AND poc.pol_id = :pol_id;

Because the view carries no business logic, all filtering, including on STATUS_CODE and DATE_INACTIVE, must be supplied by the calling report or interface.