Results for “ae_tmpt_set_name”

38 results




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

Overview

OKL_STRM_TMPT_CONTRACTS_UV is an Oracle E-Business Suite view owned by the APPS schema within the OKL (Lease and Finance Management) product family. Its documented purpose is to display all the stream types associated with a miscellaneous transaction, joining stream generation template definitions to the contracts that qualify under those templates. The view resolves a many-to-many relationship across stream generation lines, stream generation templates, template sets, accounting entry template sets, products, stream types, and contract headers.

In practice, this view answers the question: for a given contract, which stream types were generated by which stream generation template set, under which accounting entry template set and product? It is a reporting and diagnostic object rather than a transactional one, and it is typically queried during period-end reconciliation, template-impact analysis, and troubleshooting of stream generation setup. Because it already joins the contract header to its product and template lineage, it relieves report authors from reconstructing those chains manually.

Underlying Base Objects

The view is defined over the following documented base objects, all resolved through APPS synonyms except where noted:

The view text unions two branches. The first selects lines where GTL.PRIMARY_YN = 'Y' and joins PRIMARY_STY_ID to the stream type. The second selects lines where NVL(GTL.PRIMARY_YN, 'N') = 'N' and joins DEPENDENT_STY_ID. Both branches apply the same downstream joins and a date-range predicate comparing the contract start date against the template start and end dates.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list every contract using a specific stream generation template set, for example when a template set is being retired or modified. Because the searched term is the template set name, the following query is typical:

  • 1. SELECT st_gen_tmpt_set_name, contract_number, sty_name, product_name FROM okl_strm_tmpt_contracts_uv WHERE st_gen_tmpt_set_name = 'MY_GTS_NAME';
  • 2. SELECT contract_number, sty_name, sty_purpose_meaning FROM okl_strm_tmpt_contracts_uv WHERE contract_number = '123456';
  • 3. SELECT st_gen_tmpt_set_name, ae_tmpt_set_name, product_name, COUNT(*) FROM okl_strm_tmpt_contracts_uv GROUP BY st_gen_tmpt_set_name, ae_tmpt_set_name, product_name;

Reports typically join this view back to OKL_K_HEADERS or OKC_K_HEADERS_ALL_B when additional contract attributes are required, and filter on STY_PURPOSE to isolate primary versus dependent streams in analysis.