Results for “pricing_engine”

50+ results




Overview
Explore in AI Chat

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

Overview

OKL_STRM_TMPT_CONTRACT_UV is an APPS-owned database view in the OKL – Lease and Finance Management product family. Its documented purpose is to display all stream types associated with a given contract. The view joins contract header data to stream generation template definitions, template sets, accounting template sets, product definitions, and stream type definitions, producing a consolidated picture of which stream types apply to each contract at any point in time.

Unlike a transactional table, this view is a read-only consolidation layer intended for inquiry and reporting. It is frequently encountered by implementers and support analysts searching on the term "pricing_engine", because one of its projected columns is GTSV.PRICING_ENGINE, sourced from the stream generation template set. This makes the view a convenient single point of reference for determining which pricing engine is associated with a contract's stream-generation configuration, without having to traverse the underlying template hierarchy manually.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms unless noted otherwise:

  • OKC_K_HEADERS_ALL_B – contract header, supplying the contract number and start date.
  • OKL_K_HEADERS – lease-specific header extension, linking the contract to its product.
  • OKL_ST_GEN_TMPT_LNS_ALL – stream generation template lines, the driving table for the stream types.
  • OKL_ST_GEN_TEMPLATES_ALL – the template header, providing version, effective dates, and status.
  • OKL_ST_GEN_TMPT_SETS – the template set, supplying product type, tax owner, deal type, and the pricing engine.
  • OKL_AE_TMPT_SETS_ALL – accounting template sets linked to the generation set.
  • OKL_PRODUCTS_V (VIEW) – product definition linked to the accounting template set.
  • OKL_STRM_TYPE_V (VIEW) – stream type definition, supplying name, purpose, billable and capitalize flags.
  • OKL_ACCOUNTING_UTIL (PACKAGE) – used functionally to translate the stream type purpose lookup value into its display meaning.

The definition is a UNION of two branches: the first selects the primary stream type (PRIMARY_YN = 'Y' and PRIMARY_STY_ID), and the second selects dependent stream types (DEPENDENT_STY_ID). Only templates with TMPT_STATUS = 'ACTIVE' are included, and the contract start date must fall between the template start date and the template end date (or the contract start date plus one day when the end date is null).

Key Columns

Common Use Cases and Queries

Typical uses include identifying the pricing engine applied to a contract, auditing which stream types are active for a contract, and reconciling stream generation configuration between the primary and dependent lines.

To list stream types and pricing engine for a specific contract:

SELECT contract_number, sty_name, sty_purpose_meaning, st_gen_tmpt_set_name, pricing_engine, tmpt_status FROM okl_strm_tmpt_contract_uv WHERE contract_number = :p_contract_number;

To find all contracts using a given pricing engine:

SELECT DISTINCT contract_number, product_name, st_gen_tmpt_set_name FROM okl_strm_tmpt_contract_uv WHERE pricing_engine = :p_pricing_engine ORDER BY contract_number;

To identify active billable and capitalized streams:

SELECT contract_number, sty_name, billable_yn, capitalize_yn FROM okl_strm_tmpt_contract_uv WHERE tmpt_status = 'ACTIVE' AND billable_yn = 'Y';

Because the view performs multi-table joins across template and product hierarchies, queries should be filtered by contract number or pricing engine wherever possible to limit the result set.