Search Results attribute_group_name

Overview

OKC_BUS_VARIABLES_SEARCH_V is an Oracle EBS Contracts Core (OKC) dictionary view owned by the APPS schema and shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide the "Variables view definition used in Variables Search." In practice it is the flattened, presentation-ready representation of contract business variables that the Contracts authoring and search framework queries when a user searches for a variable to insert into a contract clause, template, or document. Rather than joining the multiple normalized lookup, translation, and value set tables at runtime, the view presents a single denormalized row per variable with human-readable meanings for code-based attributes.

Underlying Base Objects

The view is defined over a mixture of base tables, views, synonyms, and PL/SQL packages. The core variable definition is stored in OKC_BUS_VARIABLES_B (the base table) and OKC_BUS_VARIABLES_TL (the translation table, joined on VARIABLE_CODE and restricted to the user's session language via USERENV('LANG')). Supporting reads include FND_LOOKUPS for lookup meanings, FND_FLEX_VALUE_SETS for value set names, FND_APPLICATION_VL for the owning application name, OKC_ARTICLE_VARIABLES for article usage, and FND_GLOBAL for environment context. Two OKC_MRV_UTIL package functions are invoked inline: GETTEMPLATENAME for the template description and GETATTRIBUTEGROUPDISPNAME for the attribute group display name. Notably, the attribute group column is not sourced from a table in this view; it is derived by calling OKC_MRV_UTIL.GETATTRIBUTEGROUPDISPNAME on the CLM_REF1 column when the MRV_FLAG is 'Y'.

Key Columns

• VARIABLE_CODE / VARIABLE_NAME / DESCRIPTION – The identifier, translated display name, and description of the business variable.
• VARIABLE_TYPE / VARIABLE_TYPE_MEANING – The variable's type code and its OKC_ART_VAR_TYPE lookup meaning.
• VARIABLE_INTENT – The article intent, resolved against the OKC_ARTICLE_INTENT lookup.
• USED_IN_ARTICLES – A DECODE flag ('Y'/'N') indicating whether the variable is referenced in OKC_ARTICLE_VARIABLES.
• VALUE_SET_ID / VALUE_SET_NAME / XPRT_VALUE_SET_NAME – The flex value set restricting the variable's values.
• DATATYPE / VARIABLE_DATATYPE – Data type code and its OKC_ART_VAR_DATATYPE lookup meaning.
• ATTRIBUTE_GROUP_NAME – The MRV attribute group display name, derived via OKC_MRV_UTIL.GETATTRIBUTEGROUPDISPNAME when MRV_FLAG is set.
• MRV_FLAG / TEMPLATE_NAME / CLM_SOURCE – Multi-row variable indicators and the associated template name.
• APPLICATION_ID / APPLICATION_NAME – The owning application of the variable.
• DISABLED_YN / EXTERNAL_YN / CONTRACT_EXPERT_YN / LINE_LEVEL_FLAG – Status and scope flags.

Common Use Cases and Queries

Typical usage is to populate Variables Search LOVs, to audit which variables belong to which value set or application, and to identify attribute-grouped MRV variables.

SELECT variable_code,
       variable_name,
       attribute_group_name,
       value_set_name,
       mrv_flag
  FROM apps.okc_bus_variables_search_v
 WHERE mrv_flag = 'Y'
   AND NVL(disabled_yn, 'N') = 'N'
 ORDER BY attribute_group_name, variable_name;

To find all variables referencing a specific value set:

SELECT variable_code, variable_name, datatype
  FROM apps.okc_bus_variables_search_v
 WHERE value_set_name = :p_value_set_name;

Because the view hides the multi-table joins, it is the recommended access path for custom reports; however, the inline OKC_MRV_UTIL function calls can affect performance on large scans, so filtering on MRV_FLAG or APPLICATION_ID first is advisable.