Search Results okc_xprt_rule_condition_s

Overview

The OKC_XPRT_RULE_PVT package body in the APPS schema implements the private application logic for the Oracle E-Business Suite (EBS) Expert Rules engine within Oracle Contract Terms Management (ETRM), a component of Oracle Contracts. In EBS 12.1.1 and 12.2.2, this package provides the underlying programmatic interface used to build, maintain, and destroy the rule definitions that drive automated clause, article, and template selection during contract authoring. Rules in ETRM consist of a header, one or more conditions, condition values, and one or more outcomes; the private package encapsulates the mechanics of persisting this multi-table structure so that the rules engine can evaluate which clauses or contract terms are applicable to a given contract. Because it is classified as a PVT (private) API, it is intended as an internal implementation layer invoked by the public ETRM APIs and by the Expert Rules maintenance user interface, not as a supported entry point for customer extensions.

Key Procedures and Functions

The documented ETRM metadata identifies three procedures exposed by this package body:

• CREATE_RULE — Establishes a new expert rule by inserting the rule header and its associated child entities (conditions, condition values, and outcomes) in a single coordinated transaction.
• UPDATE_RULE — Modifies an existing expert rule, applying changes to the header and synchronizing the dependent condition and outcome records.
• DELETE_RULE_CHILD_ENTITIES — Removes the subordinate rows belonging to a rule (such as conditions, condition values, and outcomes) so that parent records can be redefined or purged without violating referential integrity.

These procedures collaborate with sibling package OKC_XPRT_RULE_PVT dependencies and the utility package OKC_XPRT_UTIL_PVT, and they rely on the FND_API error-handling and message-publishing framework (FND_MSG_PUB, FND_API) to return standardized success and failure statuses.

Tables Accessed

The package reads and writes the core Expert Rules schema through APPS synonyms:

• OKC_XPRT_RULE_HDRS_ALL and OKC_XPRT_RULE_HDRS_ALL_S — rule header definitions.
• OKC_XPRT_RULE_CONDITIONS (and the _S sequence/interface variant OKC_XPRT_RULE_CONDITION_S) — the condition rows that qualify a rule; this is the object referenced in the user's search term.
• OKC_XPRT_RULE_COND_VALS and OKC_XPRT_RULE_COND_VALS_S — the values compared within each condition.
• OKC_XPRT_RULE_OUTCOMES and OKC_XPRT_RULE_OUTCOMES_S — the actions produced when a rule evaluates true.
• OKC_XPRT_TEMPLATE_RULES and OKC_XPRT_TEMPLATE_RULES_S — the mapping of rules to contract terms templates.
• OKC_XPRT_QUESTIONS_B, OKC_BUS_VARIABLES_V, OKC_TERMS_TEMPLATES_ALL, OKC_ARTICLES_ALL, OKC_ARTICLE_VERSIONS, and OKC_ARTICLE_ADOPTIONS — supporting metadata consumed when validating and applying rules.
• Foundation tables FND_FLEX_VALUE_SETS, FND_LOOKUPS/FND_LOOKUP_VALUES, HR_OPERATING_UNITS, and HR_ORGANIZATION_INFORMATION — leveraged for value-set validation, lookup translation, and multi-org security context.

Usage Notes

OKC_XPRT_RULE_PVT is invoked indirectly rather than by direct customer calls. Typical invocations originate from the Expert Rules setup forms in the Contracts Manager responsibility, where a user creating or editing a rule triggers the CREATE_RULE and UPDATE_RULE paths; deletion flows through DELETE_RULE_CHILD_ENTITIES. The package is also referenced by one other database package, which orchestrates higher-level rule processing, and it calls FND_GLOBAL and MO_GLOBAL/MO_UTILS to establish the correct application and operating-unit context before DML. Because the ETRM metadata notes it is not referenced by any database object of its own, customizations should treat it as an internal dependency: developers requiring rule manipulation should call the supported public ETRM APIs instead, and any direct use must respect the FND_API messaging contract and org-security initialization expected by the package.