Results for “okc_article_intent”

50+ results




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

Overview

APPS.OKC_BUS_VARIABLES_SEARCH_V is a reporting and inquiry view within the Oracle E-Business Suite Contracts (OKC) module, specifically the Contract Terms and Conditions (ETRM) library. It exposes the catalog of business variables defined for use in contract terms authoring, templating, and clause generation. In Oracle EBS 12.1.1 and 12.2.2, the view functions as a denormalized presentation layer that joins the business variable definition tables to their translation records and to the various lookups that give each attribute a user-facing meaning. Its purpose is to support the "search variables" user interface and any external integration that needs to enumerate available contract variables along with their type, data type, value set, source, and usage status.

The presence of the okc_art_var_datatype lookup type in the view text is the key point of interest for users searching that term: the view resolves the variable data type by outer-joining FND_LOOKUPS on lookup_type = 'OKC_ART_VAR_DATATYPE'.

Underlying Base Objects

The view is constructed over the following documented base objects:

  • OKC_BUS_VARIABLES_B — the base (non-translated) table holding the variable definition itself, including type, data type, value set, application, and flags.
  • OKC_BUS_VARIABLES_TL — the translation table supplying the variable name and description in the session language (constrained via userenv('LANG')).
  • OKC_ARTICLE_VARIABLES — referenced through a scalar subquery to determine whether a variable is currently used in any article.
  • FND_LOOKUPS — joined three times: for the variable intent (OKC_ARTICLE_INTENT), variable type (OKC_ART_VAR_TYPE), and data type (OKC_ART_VAR_DATATYPE, outer-joined).
  • FND_FLEX_VALUE_SETS — outer-joined to resolve the associated value set name.
  • FND_APPLICATION_VL — outer-joined to supply the owning application name.
  • FND_GLOBAL — implicitly referenced through userenv('LANG') for language resolution.

Key Columns

Common Use Cases and Queries

Typical usage includes populating variable-selection lists in contract authoring, auditing which variables carry a given data type, and integration extracts.

SELECT variable_code, variable_name, variable_datatype, valueset_name
FROM   apps.okc_bus_variables_search_v
WHERE  variable_datatype IS NOT NULL
ORDER BY variable_name;
SELECT variable_code, variable_type, application_name, disabled_yn
FROM   apps.okc_bus_variables_search_v
WHERE  disabled_yn = 'N';

The view is language-sensitive and should be queried with an initialized EBS session so that userenv('LANG') returns the appropriate language.