Search Results object_code_datatype




Overview
Explore in AI Chat

Overview

The OKC_XPRT_RULE_CONDITIONS table is a core child entity within the Oracle E-Business Suite Contracts Core (OKC) module, specifically belonging to the Expert Rules (OKC_XPRT) subsystem. It stores the individual condition rows that, together with their parent rule header, define the conditional logic applied during contract authoring, generation, and validation. Where the rule header establishes the identity and overall purpose of a rule, this table captures the discrete tests that must be satisfied for the rule to fire. Each row therefore represents a single condition evaluated against an object attribute within the contract domain.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. This suggests the table can be treated as an independent hub-like entity keyed by RULE_CONDITION_ID, rather than as a strict satellite hanging off the rule header. In practice, implementers building a warehouse layer may prefer to model it as a link connecting the rule header to condition values, but the documented schema supports a standalone interpretation. The table is owned by the OKC schema and is marked VALID in the ETRM repository.

Key Information Stored

The table is documented with fifteen physical columns. The most significant are summarized below.

Common Use Cases and Queries

Typical scenarios include auditing rule configuration after an upgrade, reproducing why a rule failed to trigger, and migrating rule definitions between environments. A minimal query to list all conditions for a given rule:

  • SELECT rule_condition_id, object_type, object_code, operator, object_value_code FROM okc.okc_xprt_rule_conditions WHERE rule_id = :rule_id;
  • Join to the header for readable reporting: SELECT h.rule_name, c.object_code, c.operator, c.object_value_code FROM okc.okc_xprt_rule_hdrs_all h, okc.okc_xprt_rule_conditions c WHERE h.rule_id = c.rule_id;
  • Obtain condition values through the child table: SELECT c.rule_condition_id, v.* FROM okc.okc_xprt_rule_conditions c, okc.okc_xprt_rule_cond_vals v WHERE c.rule_condition_id = v.rule_condition_id;

These patterns are frequently used in reconciliation reports comparing seeded versus custom rules, and in diagnostic queries following contract generation errors.

Related Objects

The following objects are the most significant in relation to this table, based on the documented foreign key and primary key metadata.

  • OKC_XPRT_RULE_HDRS_ALL — Parent rule header; joined on RULE_ID. Every condition belongs to exactly one header.
  • OKC_XPRT_RULE_COND_VALS — Child table holding the discrete permitted values for a condition; joined on RULE_CONDITION_ID.
  • OKC_XPRT_RULE_CONDITIONS_PK — Primary key constraint on RULE_CONDITION_ID.
  • OKC_XPRT_RULE_CONDITIONS_U1 — Unique index on RULE_CONDITION_ID, the documented business-key candidate.
  • OKC Expert Rules APIs and concurrent programs — The OKC_XPRT processing layer that evaluates rules reads these conditions and their values at runtime.

Together these objects form the complete expert-rule definition chain: header, condition, and condition value.