Search Results okc_bus_variables_v




Overview
Explore in AI Chat

Overview

OKC_BUS_VARIABLES_V is a consolidated, language-aware view owned by the APPS schema within the OKC - Contracts Core product of Oracle E-Business Suite. It presents the definition of business variables that drive contract authoring, clause substitution, and contract expert rule evaluation in Oracle Contracts (both the core Contracts module and the integrated Contract Terms Library). In EBS 12.1.1 and 12.2.2 the view is registered as VALID and is exposed for reporting, integration, and diagnostic purposes.

Business variables in OKC represent named, typed data elements — for example contract amount, counterparty name, or effective date — that can be referenced inside contract templates, clause text, and rules. The view joins the base (non-translated) definition to the translated (language-specific) description, resolving the user's session language through USERENV('LANG'). This makes it the natural entry point for any query that needs both the technical definition and the human-readable name/description of a variable.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKC_BUS_VARIABLES_B — the base table holding the language-independent definition of each variable, including variable code, datatype, default value, intent, and descriptive flexfield attributes. The view aliases this as B.
  • OKC_BUS_VARIABLES_TL — the translation table supplying VARIABLE_NAME and DESCRIPTION per language. The view aliases this as T.

The two are joined on VARIABLE_CODE, with the translation restricted to the session language (T.LANGUAGE = USERENV('LANG')). The B.ROWID is surfaced as ROW_ID, and B.XPRT_VALUE_SET_NAME is exposed under the alias XPRT_VALUE_SET_NAME. Because the view is defined with a join on a translation table, it is effectively a single-row-per-variable, single-language projection of the underlying base table.

Key Columns

Common Use Cases and Queries

Typical uses include listing active variables available to authors, locating the value set bound to a variable, and auditing variables used by Contract Expert or external integrations.

List all enabled variables with their display names:

  • SELECT variable_code, variable_name, description, variable_datatype, variable_default_value FROM apps.okc_bus_variables_v WHERE disabled_yn = 'N' ORDER BY variable_name;

Identify Contract Expert variables and their value sets:

  • SELECT variable_code, variable_name, xprt_value_set_name FROM apps.okc_bus_variables_v WHERE contract_expert_yn = 'Y';

Find externally sourced variables bound to a specific value set:

  • SELECT variable_code, variable_name, value_set_id FROM apps.okc_bus_variables_v WHERE external_yn = 'Y' AND value_set_id IS NOT NULL;

Because the definition is filtered to USERENV('LANG'), results reflect the language of the querying session, which should be considered when extracting data for multilingual reporting or interfaces.