Results for “okc_bus_variables_vl”

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

Overview

OKC_BUS_VARIABLES_VL is a seeded, VALID view owned by the APPS schema within the OKC — Contracts Core product of Oracle E-Business Suite (documented in ETRM 12.2.2, applicable to 12.1.1 and 12.2.2). It presents the concatenated, language-translated definition of contract business variables: reusable placeholders (system, contract expert, and user-defined) whose values drive clauses, contract terms, templates, and merge logic in Oracle Contracts. The "_VL" suffix denotes a "V"iew with "L"anguage translation; the view joins translated attributes from OKC_BUS_VARIABLES_TL to the base setup rows in OKC_BUS_VARIABLES_B, resolving text columns to the session language via USERENV('LANG'). Because the view exposes friendly variable names, descriptions, data types, value-set references, and source metadata, it serves as the primary read-only interface for reporting, custom concurrent programs, and inbound/outbound integrations that need to enumerate or validate contract variable definitions without touching the base tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both accessible in APPS as synonyms:

• OKC_BUS_VARIABLES_B — the base table holding language-independent variable attributes: variable code, data type, default value, value set, flags (EXTERNAL_YN, CONTRACT_EXPERT_YN, DISABLED_YN, LINE_LEVEL_FLAG, MRV_FLAG), procedure/source metadata, and the standard WHO/descriptive flexfield columns.
• OKC_BUS_VARIABLES_TL — the translation table holding VARIABLE_NAME and DESCRIPTION per LANGUAGE.

The join condition is B.VARIABLE_CODE = T.VARIABLE_CODE AND T.LANGUAGE = USERENV('LANG'), so only rows whose translation matches the current session language are returned. ROW_ID is supplied from B.ROWID as a surrogate key for Tools/Forms-style access.

Key Columns

• VARIABLE_CODE — unique internal key linking the base and translated rows; the join key used by all dependent objects.
• VARIABLE_NAME / DESCRIPTION — translated display name and description shown to users.
• VARIABLE_DATATYPE — the data type of the variable's value (e.g., character, number, date).
• VARIABLE_DEFAULT_VALUE — default assigned when no explicit value is supplied.
• VALUE_SET_ID / XPRT_VALUE_SET_NAME — reference to an Oracle value set and its exported name, used to validate allowable values.
• VARIABLE_TYPE, VARIABLE_INTENT, VARIABLE_SOURCE — classify the variable's purpose and origin.
• EXTERNAL_YN, CONTRACT_EXPERT_YN, DISABLED_YN, LINE_LEVEL_FLAG, MRV_FLAG — behavioral flags controlling external visibility, Contract Expert participation, line-level evaluation, and multi-record variable (MRV) behavior.
• PROCEDURE_NAME, MRV_TMPL_CODE, CLM_SOURCE, CLM_REF1–CLM_REF5 — procedural and clause-mapping metadata.
• APPLICATION_ID, OBJECT_VERSION_NUMBER — owning application and optimistic-locking version.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — descriptive flexfield and audit columns.

Common Use Cases and Queries

Typical uses include validating variable setup before contract authoring, populating LOVs in custom extensions, and auditing which variables are active or line-level. Because translation is resolved by USERENV('LANG'), reports run under different language sessions yield localized names automatically.

List all enabled variables with their data types:

• SELECT variable_code, variable_name, variable_datatype, value_set_id FROM okc_bus_variables_vl WHERE NVL(disabled_yn,'N') = 'N' ORDER BY variable_name;

Find Contract Expert variables and their value sets:

• SELECT variable_code, variable_name, xprt_value_set_name FROM okc_bus_variables_vl WHERE contract_expert_yn = 'Y';

Join to clauses or templates using VARIABLE_CODE as the correlation key to trace which variables drive which terms. Always restrict or order by VARIABLE_CODE rather than translated text, and avoid DML against this view — it is a reporting interface over the underlying base tables.