Search Results okc_xprt_rule_cond_vals




Overview
Explore in AI Chat

Overview

OKC_XPRT_RULE_COND_VALS is a child table within the Oracle Contracts Core (OKC) schema that stores the individual condition values belonging to expert rules defined in Oracle E-Business Suite. Expert rules are the declarative rule engine used throughout Oracle Contracts to drive conditional behavior — determining which clauses, templates, or actions apply based on a combination of attribute values. Because a single rule condition frequently needs to be satisfied by more than one allowable value, the rule-condition record is normalized so that the actual value payloads live in this separate child table. The entity therefore acts as a value-level detail store, supporting one-to-many cardinality between a condition and the values that satisfy it, and allows the rule engine to evaluate multi-value lists without duplicating condition header rows.

From a Data Vault modeling perspective, the heuristic classification of this object is standalone. It carries an independent surrogate key and a foreign key upward to its condition parent, so a modeler may reasonably treat it as a satellite hanging off the rule condition, or, where the value is treated as an independent business concept, as a standalone hub-like entity. The classification is a suggestion only; referential behavior in the physical model is what governs joins.

Key Information Stored

The documented physical schema at ETRM 12.2.2 contains nine columns owned by OKC. The most significant of these are:

Common Use Cases and Queries

The primary use case is diagnostic: tracing why a contract rule fired (or failed to fire) requires enumerating every value attached to a condition. A typical query joins the three levels of the rule hierarchy:

  • Reporting all values for a given condition: SELECT rule_condition_value_id, object_value_code FROM okc_xprt_rule_cond_vals WHERE rule_condition_id = :condition_id;
  • Resolving a rule to its combined condition/value set by joining OKC_XPRT_RULE_COND_VALS to OKC_XPRT_RULE_CONDITIONS on RULE_CONDITION_ID.
  • Auditing configuration changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who altered rule value lists during a period.
  • Data-migration or cloning validation: comparing value counts per condition between source and target instances to confirm expert-rule setup survived an environment refresh.
  • Detecting orphaned or duplicate values by grouping on RULE_CONDITION_ID and OBJECT_VALUE_CODE.

Related Objects

The object participates in a narrow but important relationship set within the OKC schema:

  • OKC_XPRT_RULE_CONDITIONS — the direct parent; joined via RULE_CONDITION_ID and the documented foreign key.
  • OKC_XPRT_RULES (and related expert-rule header tables) — reachable through the condition parent, providing the rule-level context for each value.
  • OKC_XPRT_RULE_CONDITIONS_PK / OKC_XPRT_RULE_COND_VALS_PK — the primary-key constraints that enforce integrity across the hierarchy.
  • Oracle Contracts APIs — the Contracts Core rule engine and related PL/SQL packages consume these tables indirectly when evaluating expert rules at runtime.
  • OKC business views that expose rule configuration to the Contracts authoring UI, which read this table through the condition join.

Because the table is a leaf-level detail store with a single documented foreign key, it should always be queried with its parent condition to preserve rule context.