Results for “stream_active_yn”

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

Overview

OKL_POOL_STREAMS_UV is a PL/SQL view owned by the APPS schema within the OKL — Leasing and Finance Management product family. Its documented purpose is "Securitization - Pool Streams UI," indicating that it is designed to feed user-interface elements and analytics related to the streams associated with securitization pools. The view joins stream headers, stream elements, and stream type definitions into a single denormalized projection, allowing developers and report authors to retrieve stream-level detail without reconstructing the underlying joins manually. Because it carries the _UV suffix, it is typically classified as a user-facing or "user view" variant, and Oracle does not guarantee it as a stable public API. The user's search term, stream_type_code, is exposed by this view as STREAM_TYPE_CODE, which is sourced from the OKL_STRM_TYPE_V view. In Oracle EBS 12.1.1 and 12.2.2, the object resides in the APPS schema and reports a VALID status.

Underlying Base Objects

The view is defined over three principal sources, plus a documented package reference:

• OKL_STREAMS (synonym) — the stream header or master table, aliased as STMB. It supplies KHR_ID, KLE_ID, STY_ID, SAY_CODE, ACTIVE_YN, and the primary key ID (aliased STM_ID).
• OKL_STRM_ELEMENTS (synonym) — the stream element (line) table, aliased as SELB. It provides the amount, due date, and billed date attributes.
• OKL_STRM_TYPE_V (view) — the stream type definition view, aliased as STYV. It supplies the code, name, and subclass that describe each stream's category.
• OKL_ACCOUNTING_UTIL (package) — documented as a referenced base object, though it does not appear directly in the SELECT text; it may be involved in dependent logic or grants.

The join predicates link stream headers to elements on STMB.ID = SELB.STM_ID and link stream headers to type definitions on STMB.STY_ID = STYV.ID.

Key Columns

• KHR_ID / KLE_ID — identifiers anchoring the stream to its owning funding or lease context.
• STY_ID — the stream type identifier, which is the join key to OKL_STRM_TYPE_V.
• STREAM_TYPE_CODE — the code from OKL_STRM_TYPE_V.CODE, the principal answer to the user's search for stream_type_code.
• STREAM_TYPE_NAME / STREAM_TYPE_SUBCLASS — descriptive and classification attributes of the stream type.
• STREAM_SAY_CODE / STREAM_ACTIVE_YN — the source/reference code and the active flag of the stream header.
• STREAM_ELEMENT_DUE_DATE, STREAM_ELEMENT_AMOUNT, STREAM_ELEMENT_DATE_BILLED — the due date, amount, and billed date for each stream element.
• STM_ID — the stream identifier surviving the join (alias for OKL_STREAMS.ID).

Common Use Cases and Queries

Typical uses include securitization pool reporting, cash-flow projection, stream-type analysis, and reconciliation of billed versus due amounts. A representative query filters on the stream type code and active status:

• SELECT stm_id, khr_id, kle_id, stream_type_code, stream_type_name, stream_element_due_date, stream_element_amount, stream_element_date_billed FROM apps.okl_pool_streams_uv WHERE stream_type_code = 'RENT' AND stream_active_yn = 'Y';
• SELECT stream_type_code, stream_type_name, COUNT(*), SUM(stream_element_amount) FROM apps.okl_pool_streams_uv GROUP BY stream_type_code, stream_type_name;
• SELECT stm_id, stream_element_amount - NVL(stream_element_amount_billed,0) FROM apps.okl_pool_streams_uv WHERE stream_element_date_billed IS NULL;
• SELECT a.stm_id FROM apps.okl_pool_streams_uv a WHERE a.stream_element_due_date BETWEEN :start_date AND :end_date;

Because the view is not documented as a public interface, joins to it should be treated with caution and validated against the OKL data model across EBS 12.1.1 and 12.2.2.