Results for “sort_key”

50+ results




Overview
Explore in AI Chat

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

Overview

OKE_TERMTYPE_ASSIGNED_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered with the OKE – Project Contracts module (Oracle Procurement Contracts / Project Contracts). Its documented purpose is to present contract terms and conditions that have already been classified, exposing the hierarchical relationship between term types and the individual terms that belong to them. In EBS 12.1.1 and 12.2.2, the view is used primarily by the Terms and Conditions authoring and reporting infrastructure, and it is a convenient integration point for custom reports, extracts, and LOV queries that need a flattened list of term type/term combinations.

The view does not store data itself; it is a pure UNION ALL construct over existing term definition views. The first branch emits term type records at depth 1, and the second branch emits the terms assigned to each term type at depth 2, effectively producing a two-level tree that clients can render or filter.

Underlying Base Objects

The documented base objects referenced by the view are:

The UNION ALL combines a synthetic "term type" row set (aliased TT) with a joined "term" row set (T joined to TT on TERM_TYPE_CODE). The join enforces that only terms whose TERM_TYPE_CODE matches a valid term type are returned, which is consistent with the description that the view returns terms "that have already been classified."

Key Columns

The view exposes six columns:

  • INIT_STAT – a numeric status/initialization indicator; the UNION branches hard-code -1 for term type rows and 0 for term rows, distinguishing the two levels.
  • DEPTH – the hierarchy level; 1 for term types, 2 for terms. Useful for ordering and for tree-style rendering.
  • LABEL – the display label; the term type name for level 1, and the term name for level 2.
  • ICON – an icon identifier; 'OKEATGRP' for term type rows (group icon) and 'OKEATTR' for term rows (attribute icon).
  • DATA – the lookup/poplist value; the raw TERM_TYPE_CODE for level 1, and a concatenation of the RPAD-padded TERM_TYPE_CODE and TERM_CODE for level 2.
  • SORT_KEY – the ordering key; TERM_TYPE_NAME for level 1, and the RPAD-padded TERM_TYPE_NAME concatenated with TERM_NAME for level 2, so terms sort together under their parent type.

The column semantics above are inferred directly from the documented view text, which is authoritative for this object.

Common Use Cases and Queries

Typical scenarios include building a terms-and-conditions LOV, generating a tree of term types and their assigned terms for a contract template, and extracting a flattened list for a custom report. Because DEPTH and SORT_KEY are supplied, the view is well suited to ORDER BY DEPTH, SORT_KEY.

List all term types and their assigned terms:

  • SELECT depth, label, data, sort_key FROM apps.oke_termtype_assigned_v ORDER BY depth, sort_key;
  • SELECT label, data FROM apps.oke_termtype_assigned_v WHERE depth = 1 ORDER BY sort_key;
  • SELECT label FROM apps.oke_termtype_assigned_v WHERE depth = 2 AND data LIKE 'TERM_TYPE_CODE%' ORDER BY sort_key;
  • SELECT t.label term_type, x.label term_name FROM apps.oke_termtype_assigned_v t, apps.oke_termtype_assigned_v x WHERE t.depth = 1 AND x.depth = 2 AND x.data LIKE t.data || '%' ORDER BY t.sort_key, x.sort_key;

In all cases, qualify the view with the APPS schema (apps.oke_termtype_assigned_v) and grant appropriate privileges to any custom reporting schema. Note that the view is defined in APPS and marked VALID; no DML should be attempted against it.