Results for “okl_kle_strm_v”

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

Overview

OKL_KLE_STRM_V is a reporting view owned by the APPS schema within the Oracle Leasing and Finance Management (OKL) module. It is delivered in Oracle E-Business Suite 12.1.1 and 12.2.2 and presents the next billable stream element associated with active lease contracts. The view consolidates stream, stream type, and stream element data into a single denormalized result set, restricted to streams whose status is either current or on hold, that are linked to a lease (KLE_ID), and whose stream type is flagged as billable. Because it surfaces the earliest unbilled element per stream, it functions as a forward-looking billing queue.

In reporting and integration contexts, the view is frequently the source for billing extracts, revenue forecasting reports, and feeder programs that need to identify upcoming billing events. The user search term "billed_amount" maps directly to the BILLED_AMOUNT column, which is the element amount expected to be billed on the next billing date. This makes the view particularly relevant to finance teams reconciling scheduled billings against actual invoices.

Underlying Base Objects

The view is defined over three OKL views and is documented with a reference to the OKL_ACCOUNTING_UTIL package. The primary objects are:

• OKL_STRM_TYPE_V — supplies the stream type name (NAME) and the BILLABLE_YN flag used to filter non-billable streams.
• OKL_STREAMS_V — supplies the stream identifier (ID), lease identifier (KLE_ID), contract identifier (KHR_ID), status code (SAY_CODE), and purpose code. The join to OKL_STRM_TYPE_V is on STM.ID = STY.STY_ID.
• OKL_STRM_ELEMENTS_V — supplies the stream element amount (mapped to BILLED_AMOUNT) and the element date (mapped to NEXT_BILLED_DATE). It is joined on STEM.STM_ID = STY.ID and constrained by a correlated subquery returning the minimum STREAM_ELEMENT_DATE where DATE_BILLED IS NULL.

The correlated subquery effectively selects only the nearest unbilled element for each stream, preventing multiple rows per stream and ensuring a single next-billing projection.

Key Columns

• NAME — The stream type name from OKL_STRM_TYPE_V, describing the nature of the billing stream.
• ID — The stream identifier from OKL_STREAMS_V, the primary join key for downstream queries.
• KLE_ID — The lease identifier linking the stream to a specific lease contract; non-null is enforced by the view filter.
• KHR_ID — The associated contract identifier, useful for joining to contract headers.
• BILLED_AMOUNT — The amount of the next unbilled stream element; this is the column matched by the "billed_amount" search.
• NEXT_BILLED_DATE — The scheduled date of the next billing event, derived from the minimum unbilled element date.
• STATUS — The stream status code (SAY_CODE), restricted to CURR (current) or HOLD.

Common Use Cases and Queries

Typical scenarios include extracting scheduled billings for a lease portfolio, forecasting cash inflows, and feeding billing or accounting processes. A general query returning all scheduled billings is:

SELECT name, id, kle_id, khr_id, billed_amount, next_billed_date, status FROM apps.okl_kle_strm_v ORDER BY next_billed_date;

To isolate billings due within a period, filter on NEXT_BILLED_DATE. To reconcile amounts against actual billed transactions, join KLE_ID and ID to the stream element tables and compare BILLED_AMOUNT with posted amounts. Because the view already restricts to billable, active streams with an unbilled element, it provides a ready-made worklist for billing operations without additional filtering.