Results for “variable_code”

50+ results




Overview
Explore in AI Chat

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

Overview

OKC_TERMS_CLM_UDV_T is a table in the OKC schema (Contracts Core) that stores user-defined variable values attached to contract terms, clauses, and document content within Oracle E-Business Suite ETRM. In the context of Oracle EBS 12.1.1 and 12.2.2, it acts as a flexible attribute store that allows contracts to capture business-specific data elements that are not modeled as fixed columns. Each row represents a variable binding — a variable code paired with a value — scoped to a particular document and category combination.

Based on the heuristic Data Vault classification mined from the foreign key structure, this table is best modeled as a satellite. It carries descriptive attributes (variable values) that depend on parent business keys supplied by surrounding entities such as article versions and category definitions, rather than serving as an independent hub or a link between two hubs.

Key Information Stored

The documented physical schema exposes six columns, of which the most significant are:

  • VARIABLE_CODE — The identifier for the user-defined variable being populated. Together with CAT_ID, this forms the unique business key (index OKC_TERMS_CLM_UDV_T_U1), ensuring a single value per variable per category.
  • VARIABLE_VALUE — The actual value assigned to the variable, holding the user-defined data captured during contract authoring.
  • CAT_ID — Foreign key to BEN_TCS_CAT, identifying the category that scopes the variable. Combined with VARIABLE_CODE, it is the business-key candidate for uniqueness.
  • ARTICLE_VERSION_ID — Foreign key to OKC_ARTICLE_VERSIONS, linking the variable value to a specific article version in the contract document.
  • DOC_TYPE — Indicates the document type context for the variable binding.
  • DOC_ID — The document identifier that anchors the record to its owning contract document.

No dedicated surrogate primary key column is documented in the metadata; the unique index OKC_TERMS_CLM_UDV_T_U1 (VARIABLE_CODE, CAT_ID) serves as the business-key candidate. All six columns are documented above.

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all variable values for a given contract document, auditing populated user-defined variables by category, and joining variable data to contract headers for downstream analytics.

  • Listing variables for a specific document: SELECT variable_code, variable_value, cat_id FROM okc_terms_clm_udv_t WHERE doc_id = :doc_id AND doc_type = :doc_type;
  • Resolving a variable's category definition: join to BEN_TCS_CAT on CAT_ID to retrieve category names and properties.
  • Cross-referencing with article versions: join ARTICLE_VERSION_ID to OKC_ARTICLE_VERSIONS to report variables per article version.
  • Detecting missing or default variables by comparing expected VARIABLE_CODE values against populated rows for a document.

Related Objects

The following objects are most significant in relation to this table:

  • OKC_ARTICLE_VERSIONS — referenced via ARTICLE_VERSION_ID; provides the article version context for each variable value.
  • BEN_TCS_CAT — referenced via CAT_ID; supplies the category definition that scopes the variable code.
  • OKC_TERMS_CLM_UDV_V — the corresponding view, if defined, for querying user-defined variable values.
  • OKC_TERMS_CLM_UDV — the base terms/clause user-defined variable entity that this table extends.
  • OKC_CONTRACTS / OKC_K_HEADERS — contract header tables used to enrich reports by joining through DOC_ID.

Together these relationships allow contract variables to be resolved, categorized, and reported within the broader Oracle Contracts Core data model.