Results for “okc_xprt_rule_outcomes_active”

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

Overview

OKC_XPRT_RULE_OUTCOMES_ACTIVE is a child table within the OKC (Contracts Core) schema of Oracle E-Business Suite, holding the outcome definitions that belong to expert rules configured in Oracle Contracts. Expert rules drive conditional behavior during contract authoring, and each rule can resolve to one or more outcomes that determine what the application subsequently does. This table stores those resolved outcomes and links them back to the parent rule header entity, making it the operational bridge between rule evaluation logic and the actions or values that result from a rule firing.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a standalone entity rather than a pure link or satellite. It carries its own surrogate key and business keys while referencing the rule header, so a practitioner could reasonably model it as a small hub with dependent attributes, or as a link table capturing a rule-to-outcome association.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• RULE_OUTCOME_ID — the surrogate primary key for each outcome row, and the target of the documented unique index OKC_XPRT_RULE_OUTCOMES_ACT_U1. This column is also the FK source pointing to OKC_XPRT_RULE_OUTCOMES.RULE_OUTCOME_ID.
• RULE_ID — identifies the parent expert rule header to which the outcome belongs, forming part of the second unique index.
• OBJECT_TYPE — classifies the object against which the outcome is defined.
• OBJECT_VALUE_ID — the specific object instance value paired with OBJECT_TYPE. Together, RULE_ID, OBJECT_TYPE, and OBJECT_VALUE_ID form unique index OKC_XPRT_RULE_OUTCOMES_ACT_U2, a strong business-key candidate.
• MANDATORY_YN — flag indicating whether the outcome is mandatory when the rule fires.
• MANDATORY_RWA — the read/write/access indicator associated with the mandatory setting.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns maintained automatically by the EBS "Who" columns framework.

Common Use Cases and Queries

Typical usage centers on diagnosing why a contract rule produced a particular result, or auditing which rules carry mandatory outcomes. A common query joins the outcomes table back to its parent rule:

• SELECT r.RULE_ID, r.RULE_NAME, o.RULE_OUTCOME_ID, o.OBJECT_TYPE, o.OBJECT_VALUE_ID, o.MANDATORY_YN
• FROM OKC_XPRT_RULE_OUTCOMES_ACTIVE o, OKC_XPRT_RULE_OUTCOMES r
• WHERE o.RULE_OUTCOME_ID = r.RULE_OUTCOME_ID;

Reporting scenarios include identifying all mandatory outcomes (filtering MANDATORY_YN = 'Y'), auditing rule definitions by OBJECT_TYPE, and validating orphaned outcomes that lack a matching rule header. Because the table carries OBJECT_VERSION_NUMBER, care should be taken when performing bulk updates via the Contracts APIs, since framework-managed version checks may reject writes that bypass the standard DML path.

Related Objects

• OKC_XPRT_RULE_OUTCOMES — the immediate parent, joined on RULE_OUTCOME_ID. This is the primary documented relationship.
• OKC_XPRT_RULES / rule headers — referenced via RULE_ID, the logical grouping of the outcome.
• OKC_RULES_B / OKC_RULES_TL — rule definition base and translated tables that feed outcome resolution.
• OKC_TERMS_UTIL / OKC_CONTRACT_UTIL packages — PL/SQL units that evaluate expert rules and read the outcomes defined here.
• OKC_XPRT_RULE_TEMP / API-layer tables — transient structures used during rule processing that reference outcome identifiers.
• OE_ORDER_HEADERS, OKC_K_HEADERS_B — contract and order header tables whose qualifying behavior may be influenced by rule outcomes during authoring.

Because the metadata is limited to the documented schema above, developers should validate any additional dependencies against the actual database catalog in their 12.1.1 or 12.2.2 instance.