Search Results okl_strm_tmpt_all_types_uv




Overview

OKL_STRM_TMPT_ALL_TYPES_UV is a reporting view owned by the APPS schema in Oracle Lease and Finance Management (OKL). Its documented purpose is to display all stream template types that are associated with a given stream generation template. The view is a UNION ALL construct that consolidates two distinct relationship paths from the template-line table to the stream type definition, exposing primary and dependent stream types through a single, uniform column projection.

The view exists to simplify application and reporting logic. Rather than requiring callers to query the template-line table twice — once for primary stream types and once for dependent stream types — the view merges both sets into one result set. This makes it suitable for LOV definitions, concurrent program parameter queries, and downstream integration extracts that must enumerate the complete set of stream types attached to a stream generation template. The view is marked VALID and is documented as part of the ETRM 12.2.2 metadata set; because it is a pure query view with no version-specific procedural logic, its behavior is substantially the same on 12.1.1 and 12.2.2.

Underlying Base Objects

The view text references three documented base objects:

The first UNION ALL branch selects rows where PRIMARY_YN = 'Y' and joins on PRIMARY_STY_ID. The second branch selects rows where NVL(PRIMARY_YN, 'N') = 'N' and joins on DEPENDENT_STY_ID. The NVL wrapper ensures that null primary flags are treated as dependent rows, so no template line is silently dropped. DISTINCT is applied within each branch, which suppresses duplicate stream type references arising from multiple template lines pointing at the same stream type.

Key Columns

  • STY_ID — the stream type identifier, sourced from either PRIMARY_STY_ID or DEPENDENT_STY_ID depending on the branch. This is the join key back to OKL_STRM_TYPE_V and to downstream stream type references.
  • STY_NAME — the stream type name (STY.NAME). This is the column most commonly used in user-facing lists and is the attribute associated with the search term "sty_name".
  • STY_PURPOSE — the raw lookup code for the stream type purpose (STY.STREAM_TYPE_PURPOSE).
  • STY_PURPOSE_MEANING — the translated meaning of STY_PURPOSE, derived from the OKL_STREAM_TYPE_PURPOSE lookup type via OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING. This column presents the purpose in business language.
  • BILLABLE_YN — indicates whether the stream type is billable (STY.BILLABLE_YN).
  • DESCRIPTION — the stream type description (STY.DESCRIPTION).

Common Use Cases and Queries

The view is typically consumed when an application or report needs the full catalogue of stream types available on a stream generation template, without distinguishing primary from dependent types. Typical scenarios include populating stream type selection lists, validating that a chosen stream type belongs to a template, and extracting template configuration for reconciliation.

Because the view carries no template identifier column of its own, filtering to a specific template requires joining back to OKL_ST_GEN_TMPT_LNS. A representative query retrieving the stream types of a given template is:

  • SELECT t.STY_ID, t.STY_NAME, t.STY_PURPOSE_MEANING, t.BILLABLE_YN FROM OKL_STRM_TMPT_ALL_TYPES_UV t, OKL_ST_GEN_TMPT_LNS l WHERE l.PRIMARY_STY_ID = t.STY_ID AND l.TEMPLATE_ID = :template_id;
  • SELECT STY_ID, STY_NAME, DESCRIPTION FROM OKL_STRM_TMPT_ALL_TYPES_UV WHERE BILLABLE_YN = 'Y' ORDER BY STY_NAME;
  • SELECT DISTINCT STY_PURPOSE, STY_PURPOSE_MEANING FROM OKL_STRM_TMPT_ALL_TYPES_UV ORDER BY STY_PURPOSE_MEANING;

These patterns rely only on the documented columns and base objects, and are stable across the 12.1.1 and 12.2.2 releases.