Results for “okc_xprt_rule_outcomes”

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

Overview

The OKC_XPRT_RULE_OUTCOMES table is a core Contracts Core (OKC) repository object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the evaluated results, or outcomes, produced when the Contracts Expert Rules engine executes against a contract or related business object. Expert rules in Oracle Contracts provide extensible validation, defaulting, and derivation logic applied during contract authoring, approval, and amendment. Each time such a rule fires, its resulting determinations are captured as rows in this table, forming a persistent audit of what the rule engine decided and why.

The table is documented as a child entity of the rules header entity, meaning it holds a dependent, multi-row relationship to a parent rule definition. Under Oracle's heuristic Data Vault classification it is characterized as standalone, indicating it is not modelled as a strict hub, link, or satellite within the mined foreign-key structure. For modelling purposes it may nonetheless be treated as a satellite or detail record clustered beneath the rule header, keyed by its own surrogate identifier.

Key Information Stored

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

• RULE_OUTCOME_ID — surrogate primary key, enforced by OKC_XPRT_RULE_OUTCOMES_PK. Also carries a unique index (OKC_XPRT_RULE_OUTCOMES_U1).
• RULE_ID — identifies the parent expert rule whose execution produced this outcome; the principal link back to the rules header.
• OBJECT_TYPE and OBJECT_VALUE_ID — together identify the business object the rule was evaluated against (for example a contract or contract line).
• MANDATORY_YN and MANDATORY_RWA — flags indicating whether the outcome is enforced as mandatory and the associated rule-with-attribute behaviour.
• OBJECT_VERSION_NUMBER — optimistic locking column supporting concurrent maintenance.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO-column audit attributes recording row provenance.

A second unique index, OKC_XPRT_RULE_OUTCOMES_U2, spans (RULE_ID, OBJECT_TYPE, OBJECT_VALUE_ID), making this composite a business-key candidate that guarantees a single outcome per rule per business object instance.

Common Use Cases and Queries

Typical reporting retrieves all outcomes generated for a given contract by filtering on the object identity columns:

• Trace which rules fired on a contract: SELECT rule_id, mandatory_yn FROM okc_xprt_rule_outcomes WHERE object_type = :p_type AND object_value_id = :p_id;
• Audit rule behaviour over time using CREATION_DATE and the WHO columns.
• Validate mandatory outcomes prior to contract approval by checking MANDATORY_YN = 'Y'.
• Reconcile outcomes against the parent rule definition joined on RULE_ID.

Because the table is an accumulation of engine output, trend and exception reporting across rules and object types is a frequent requirement.

Related Objects

• OKC_XPRT_RULES — the parent rules header referenced through RULE_ID.
• OKC_XPRT_RULE_ATTRIBUTES — attribute-level rule configuration linked via RULE_ID.
• OKC_CONTRACTS / OKC_CONTRACT_LINES — the principal OBJECT_TYPE targets resolved through OBJECT_VALUE_ID.
• OKC_XPRT_RULE_GROUPS — grouping definitions tied to rule headers.
• OKC_XPRT_RULE_SETS — rule set membership driving execution order.
• OKC_RULES / OKC_RULE_ATTRIBUTES APIs — programmatic interfaces that evaluate rules and populate outcome rows.

Joins are consistently made on RULE_ID to reach rule headers and on OBJECT_VALUE_ID plus OBJECT_TYPE to reach the affected contract entity.