Results for “clm_ref5”

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

Overview

OKC_BUS_VARIABLES_B is a core configuration table in the Oracle E-Business Suite Contracts Core (OKC) module. It stores the master definition of every business variable that can be referenced inside contract clauses. In the Contracts authoring framework, clauses are composed of boilerplate legal text interleaved with merge-style tokens, and each token is resolved at runtime from a row in this table. The variables captured here span all categories supported by the product: system-defined variables supplied by Oracle, user-defined variables created by implementers, table-based variables whose values are fetched by SQL, and deliverable variables tied to contract deliverables.

Because the table stores both the identifier and the behavioural metadata of each variable (datatype, allowable value set, default, and the PL/SQL entry point used to resolve it), it acts as the authoritative registry that the clause rendering engine consults. From a Data Vault modelling perspective, the documented foreign-key structure suggests this object is hub-leaning: VARIABLE_CODE is the durable business key around which descriptive and reference attributes cluster, and multiple dependent tables attach to it.

Key Information Stored

The primary key of the base table is defined by OKC_BUS_VARIABLES_B_PK1 on VARIABLE_CODE. A secondary unique index, OKC_BUS_VARIABLES_B_U1, covers VARIABLE_CODE together with ZD_EDITION_NAME, reflecting the multi-edition (ZD) architecture introduced in release 12.2. In this context VARIABLE_CODE is the true business-key candidate, while surrogate/system-generated key columns support the editioning model.

The most significant columns include:

• VARIABLE_CODE — the unique business identifier of the variable, referenced by clause definitions and dependent tables.
• VARIABLE_TYPE — the category of variable (for example system-defined, user-defined, table, or deliverable).
• VARIABLE_DATATYPE — the datatype of the value the variable returns (character, number, date, etc.).
• VARIABLE_INTENT and VARIABLE_SOURCE — classify the intent and originating source of the variable, governing how it is resolved.
• APPLICATION_ID — foreign key to FND_APPLICATION, identifying the owning application.
• VALUE_SET_ID — foreign key to FND_FLEX_VALUE_SETS, providing the list of valid values for the variable.
• VARIABLE_DEFAULT_VALUE — the value used when no runtime value is supplied.
• PROCEDURE_NAME — the PL/SQL routine invoked to compute the variable value at contract generation time.
• DISABLED_YN, EXTERNAL_YN, CONTRACT_EXPERT_YN, LINE_LEVEL_FLAG, and MRV_FLAG — behavioural flags controlling availability, external exposure, expert-mode use, line-level scope, and multi-record variable handling.
• DATE_PUBLISHED — the date the variable definition was published for use.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE — standard audit and concurrency columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 … ATTRIBUTE15 — the standard DFF extension block.

Common Use Cases and Queries

Typical usage centres on auditing and reporting the variable library. A frequent query lists all enabled variables of a given type with their value sets:

• SELECT VARIABLE_CODE, VARIABLE_TYPE, VARIABLE_DATATYPE, VALUE_SET_ID, DISABLED_YN FROM OKC_BUS_VARIABLES_B WHERE DISABLED_YN = 'N' AND VARIABLE_TYPE = :p_type.
• Join to FND_FLEX_VALUE_SETS to obtain the human-readable value-set name for validation reporting.
• Join to OKC_ARTICLE_VARIABLES to identify which clauses reference a given variable before retiring or disabling it.
• Filter by DATE_PUBLISHED or LINE_LEVEL_FLAG to profile line-level versus header-level variables for integration planning.

Report developers frequently expose the variable catalogue to legal and contract-administration teams, and interface developers use it to drive the token substitution logic when generating contract documents programmatically through the Contracts APIs.

Related Objects

The following objects are directly related through documented foreign keys or referencing relationships:

• FND_FLEX_VALUE_SETS — referenced by OKC_BUS_VARIABLES_B.VALUE_SET_ID; supplies valid values.
• FND_APPLICATION — referenced by OKC_BUS_VARIABLES_B.APPLICATION_ID; identifies the owning application.
• OKC_BUS_VARIABLES_TL — the translation table, keyed on VARIABLE_CODE, holding language-specific variable names and descriptions.
• OKC_ARTICLE_VARIABLES — maps variables to clause articles via VARIABLE_CODE.
• OKC_VARIABLE_DOC_TYPES — restricts variable availability by document type via VARIABLE_CODE.

Together these tables form the variable-definition sub-model that the OKC clause engine depends upon.