Results for “okl_strm_elements_v”

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

Overview

OKL_STRM_ELEMENTS_V is a VALID Oracle E-Business Suite view owned by the APPS schema in the OKL (Lease and Finance Management) product. The ETRM documentation describes it as holding "the actual payment schedules for a payment header." In practice, the view exposes the line-level stream elements that make up a contractual payment schedule — individual due dates, amounts, accrual flags, and adjustment flags that together form the disbursement and billing stream for a lease, loan, or financing contract.

The view functions as a pass-through projection over the OKL_STRM_ELEMENTS base table, which is exposed in APPS through the synonym of the same name. Because it is a view rather than a table, consumers obtain read-oriented access to stream element data without direct DML privileges on the base table. The view is used across ETRM inquiry pages, payment schedule displays, and downstream reporting, including accounting event generation and integration extracts where scheduled cash flows must be reported by date.

The user search term "date_disbursed" corresponds directly to the DATE_DISBURSED column in this view. That column carries the disbursement date associated with a stream element, distinguishing it from the contractual billing date represented by DATE_BILLED and the generic STREAM_ELEMENT_DATE.

Underlying Base Objects

The documented base object is OKL_STRM_ELEMENTS, referenced in the 12.2.2 metadata as a synonym in the APPS schema. The view definition selects every column from OKL_STRM_ELEMENTS using the SELB alias, including ROWID as ROW_ID. No join, filter, aggregation, or decode is applied — the view is a straight column-for-column projection of the base table, augmented with a ROW_ID pseudocolumn that facilitates row identification for updating frameworks such as Oracle Forms or OAF-based pages.

Because the view is defined only over OKL_STRM_ELEMENTS, any change to the base table's structure propagates to the view. The STM_ID column links each element to its parent payment header in the stream header structure, making OKL_STRM_ELEMENTS_V the detail side of a header-detail relationship. The metadata lists the referenced base object as a synonym, confirming that the physical table resides in the OKL schema and is synonymed into APPS for application access.

Key Columns

The following columns are the most significant for reporting and integration.

• ID — Primary identifier of the stream element line.
• STM_ID — Foreign key to the stream header (payment header) that owns this schedule line.
• SE_LINE_NUMBER — Ordering sequence of the element within its stream.
• STREAM_ELEMENT_DATE — The effective date of the stream element within the schedule.
• DATE_BILLED — Date on which the element is billed.
• DATE_DISBURSED — Date on which the related amount is disbursed; the focus of the user's search.
• AMOUNT — Monetary value of the individual schedule line.
• ACCRUED_YN — Indicates whether the element has been accrued.
• BILL_ADJ_FLAG and ACCRUAL_ADJ_FLAG — Flags identifying billing and accrual adjustments.
• SEL_ID, SOURCE_ID, SOURCE_TABLE — Traceability back to the originating source record.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the concurrent program columns PROGRAM_ID, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include reconstructing a payment schedule for a given header, reporting disbursements by date, reconciling billed versus disbursed amounts, and identifying adjustment lines. The following query retrieves all elements for a specific payment header, ordered by line number:

• SELECT se_line_number, stream_element_date, date_billed, date_disbursed, amount, accrued_yn FROM okl_strm_elements_v WHERE stm_id = :p_stm_id ORDER BY se_line_number;

To isolate actual disbursements within a period, filter on DATE_DISBURSED:

• SELECT stm_id, se_line_number, date_disbursed, amount FROM okl_strm_elements_v WHERE date_disbursed BETWEEN :p_from_date AND :p_to_date ORDER BY date_disbursed, stm_id;

To identify billing and accrual adjustments, query the adjustment flags:

• SELECT id, stm_id, amount, bill_adj_flag, accrual_adj_flag FROM okl_strm_elements_v WHERE bill_adj_flag = 'Y' OR accrual_adj_flag = 'Y';

Because the view is unfiltered, production queries should always constrain on STM_ID, ID, or a date range to avoid full scans of the base table.