Results for “okl_line_strms_sum_uv”

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

Overview

OKL_LINE_STRMS_SUM_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management — and is classified as a User View (the "UV" suffix). Its stated purpose, per the ETRM documentation, is to present the summed amounts of Service, Fee, and Insurance streams associated with lease and finance contracts. Because it aggregates stream elements at the contract, line, and stream-type level, it functions as a reporting and integration layer that converts raw transactional stream data into consolidated monetary figures.

The view is especially relevant to searches on okl_stream_type_purpose, since one of its central outputs is the decoded stream type purpose. Rather than forcing report authors to join lookup tables manually, the view invokes OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING to translate the raw STREAM_TYPE_PURPOSE_CODE into a user-facing meaning. This makes it a convenient source for contract-level stream summaries in custom reports, extracts, and interfaces.

Underlying Base Objects

The view is defined over a UNION ALL of two SELECT statements, each joining contract, line, and stream objects. The documented referenced base objects are:

• OKC_K_HEADERS_B — contract headers, supplying CONTRACT_ID and CONTRACT_NUMBER.
• OKC_K_LINES_B and OKC_K_LINES_TL — contract lines (base and translated) providing the FEE line context.
• OKC_LINE_STYLES_B — line styles; the view filters on LTY_CODE = 'FEE'.
• OKC_K_ITEMS — links contract lines to stream type definitions via OBJECT1_ID1.
• OKL_STREAMS — the stream master rows, supplying activity codes and purpose codes.
• OKL_STRM_ELEMENTS — the individual stream elements whose AMOUNT values are summed.
• OKL_STRM_TYPE_B and OKL_STRM_TYPE_TL — stream type base and translated names, with the translated table joined twice (aliases STYT and STYA) to expose the line name and stream name.
• OKL_ACCOUNTING_UTIL — the package whose GET_LOOKUP_MEANING function decodes lookup codes.
• OKX_SYSTEM_ITEMS_V — an item view referenced by the UNION ALL branch that returns OSIB.NAME as K_LINE_NAME, indicating a second population of non-FEE or item-based stream summaries.

All OKC and OKL objects are accessed through APPS synonyms, so the view executes entirely within the APPS schema context.

Key Columns

• CONTRACT_ID / CONTRACT_NUMBER — identifiers of the lease or finance contract header.
• ACTIVITY_CODE and ACTIVITY — the raw stream activity code (SAY_CODE) and its decoded meaning from the OKL_STREAM_ACTIVITY lookup.
• K_LINE_NAME — the contract line name, taken from the translated stream type or from OKX_SYSTEM_ITEMS_V depending on the branch.
• NAME — the stream type name.
• STREAM_TYPE_PURPOSE_CODE — the raw purpose code stored on OKL_STRM_TYPE_B.
• STREAM_TYPE_PURPOSE — the decoded meaning of the purpose code via the OKL_STREAM_TYPE_PURPOSE lookup; this is the column most directly associated with the search term okl_stream_type_purpose.
• AMOUNT — the SUM of OKL_STRM_ELEMENTS.AMOUNT, aggregated across the grouped dimensions.
• PURPOSE_CODE and PURPOSE — the stream's general purpose code and its decoded meaning (OKL_STRM_G_PURPOSE).
• ID — the stream type identifier (STYB.ID).

Common Use Cases and Queries

Typical uses include contract-level financial summaries, reconciliation of service, fee, and insurance streams, and reporting that requires the decoded purpose rather than raw codes.

SELECT CONTRACT_NUMBER,
       K_LINE_NAME,
       STREAM_TYPE_PURPOSE,
       ACTIVITY,
       SUM(AMOUNT) TOTAL_AMOUNT
FROM   APPS.OKL_LINE_STRMS_SUM_UV
WHERE  STREAM_TYPE_PURPOSE = 'Insurance'
GROUP  BY CONTRACT_NUMBER, K_LINE_NAME, STREAM_TYPE_PURPOSE, ACTIVITY;

A second pattern filters by contract to inspect the composition of streams:

SELECT STREAM_TYPE_PURPOSE_CODE,
       STREAM_TYPE_PURPOSE,
       PURPOSE,
       AMOUNT
FROM   APPS.OKL_LINE_STRMS_SUM_UV
WHERE  CONTRACT_NUMBER = :p_contract_number
ORDER  BY STREAM_TYPE_PURPOSE;

Because lookups are decoded at runtime through OKL_ACCOUNTING_UTIL, results reflect current lookup definitions. The view should be treated as read-only and is not intended for direct DML; downstream integration should consume it through standard EBS reporting or extract mechanisms.