Results for “str_elm”

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

Overview

The view APPS.OKL_CS_SCHPRINC_PAYMENTS_UV is a reporting and integration object within the Oracle E-Business Suite (EBS) Lease and Finance Management (also referred to as ETRM / Oracle Lease Management) module. It exposes a consolidated, query-ready projection of scheduled principal payment stream elements associated with lease contracts. Rather than requiring downstream consumers — reports, concurrent programs, interfaces, or custom extensions — to join three separate stream tables manually, this view pre-applies the join and filtering logic that isolates the principal payment component of an active lease contract's current financial schedule.

The view is particularly relevant to users searching for the term principal_payment, since that literal value is the central filter (via STREAM_TYPE_PURPOSE = 'PRINCIPAL_PAYMENT') that defines the population of records returned. In EBS 12.1.1 and 12.2.2, the object resides in the APPS schema and is intended to be queried through synonyms or direct references from PL/SQL and BI Publisher/XML Publisher report data templates.

Underlying Base Objects

The view is defined as a three-way join across the following documented base objects, all exposed through synonyms in the APPS layer:

• OKL_STRM_TYPE_B — the stream type definition table. The join condition STR_TYPE.ID = STRM.STY_ID links each stream to its type, while STREAM_TYPE_PURPOSE = 'PRINCIPAL_PAYMENT' restricts the result set to principal payment stream types.
• OKL_STREAMS — the header-level stream table, joined via STRM.STY_ID to the type and via STRM.ID = STR_ELM.STM_ID to the elements. It is filtered to current streams (SAY_CODE = 'CURR'), active streams (ACTIVE_YN = 'Y'), and streams without an overriding purpose code (PURPOSE_CODE IS NULL).
• OKL_STRM_ELEMENTS — the line-level detail table holding individual scheduled amounts and dates. Its AMOUNT and STREAM_ELEMENT_DATE columns form the transactional payload of the view.

The join effectively returns one row per principal-payment stream element belonging to an active, current, unpurposed stream on a lease contract.

Key Columns

• KLE_ID — sourced from STRM.KLE_ID. Identifies the lease contract header (KLE) to which the stream and its principal payment elements belong. This is the primary linkage back to the contract entity and is typically the join key to other lease reporting views and tables.
• AMOUNT — sourced from STR_ELM.AMOUNT. Represents the monetary value of the individually scheduled principal payment stream element. Sign conventions follow the underlying element configuration.
• STREAM_ELEMENT_DATE — sourced from STR_ELM.STREAM_ELEMENT_DATE. The scheduled due date or effective date of the corresponding principal payment element, enabling period-based aggregation and aging analysis.

Because the view projects only these three columns, it is a narrow, purpose-built object. Additional stream or contract attributes must be obtained by joining back to OKL_STREAMS or the contract tables on KLE_ID.

Common Use Cases and Queries

Typical applications include principal amortization reporting, cash-flow forecasting, lease schedule reconciliation, and data extraction for downstream financial systems. The view is commonly consumed by XML Publisher report templates and custom concurrent programs. A representative query totals scheduled principal by contract:

• SELECT kle_id, SUM(amount) total_principal FROM apps.okl_cs_schprinc_payments_uv GROUP BY kle_id;
• SELECT kle_id, stream_element_date, amount FROM apps.okl_cs_schprinc_payments_uv WHERE kle_id = :p_kle_id ORDER BY stream_element_date;
• SELECT TRUNC(stream_element_date,'MM') period, SUM(amount) FROM apps.okl_cs_schprinc_payments_uv GROUP BY TRUNC(stream_element_date,'MM');

Callers should confirm appropriate MO: Operating Unit or security context where multi-org or lease security is enforced by surrounding data models, as this view itself applies no organizational filter.