Search Results drop_rule_set

Overview

SYS.DBMS_RULE_ADM is the administrative interface to the Oracle Database Rules Manager and Expression Filter components. In the Oracle EBS 12.1.1 and 12.2.2 environments, this package supplies the DDL-level operations required to define, modify, and remove the objects that make up a rule engine: evaluation contexts, rule sets, and individual rules. Because EBS embeds the Rules Manager infrastructure to support configurable business logic — most notably within Oracle Advanced Pricing, Oracle Configurator, and various approval and eligibility frameworks — DBMS_RULE_ADM acts as the control layer through which those constructs are provisioned.

The package is declared AUTHID CURRENT_USER, so every call executes with the privileges of the invoking schema, and the EBS application code must therefore hold the necessary rule-engine privileges. It is owned by SYS and is part of the database kernel rather than the APPS schema, though APPS-based code frequently reaches it through synonyms and grants.

Key Procedures and Functions

The documented entry points cover three object families and follow a consistent lifecycle of create, alter, and drop, with internal (_INT) counterparts used to complete the privileged work. All are procedures:

• Evaluation context lifecycle — CREATE_EVALUATION_CONTEXT, ALTER_EVALUATION_CONTEXT, and DROP_EVALUATION_CONTEXT define the data model (table and column mappings, event structure, and evaluation function) against which rules are evaluated. The _INT variants perform the underlying dictionary operations.
• Rule set lifecycle — CREATE_RULE_SET, ALTER_RULE_SET (exposed through the internal form), and DROP_RULE_SET create and maintain named collections of rules. Rule sets are the unit that the evaluation engine iterates during a rules invocation.
• Rule lifecycle — CREATE_RULE, ALTER_RULE, and DROP_RULE manage the individual conditional statements (boolean expressions) that belong to a rule set. The _INT variants again carry out the internal work.
• Membership management — ADD_RULE and ADD_RULE_INT attach an existing rule to a rule set, while REMOVE_RULE and REMOVE_RULE_INT detach it. These provide the association layer between rules and their containing sets.

The package also publishes named constants — including privilege codes such as CREATE_ANY_EVALUATION_CONTEXT, EXECUTE_ON_RULE_SET, and ALL_ON_RULE — and return codes (EVALUATION_SUCCESS, EVALUATION_FAILURE, EVALUATION_CONTINUE) referenced by evaluation functions associated with a context.

Because the metadata for the “evaluation_context” search term maps directly to this domain, the context-management procedures are the most relevant subset for EBS administrators investigating rule-engine configuration.

Tables Accessed

The provided ETRM metadata does not enumerate specific tables referenced via APPS synonyms. In practice, DBMS_RULE_ADM operates primarily on the rule-engine dictionary views and underlying repository tables that store evaluation context definitions, rule set membership, and rule expressions. The metadata confirms that the package is referenced by 13 other packages, indicating heavy internal reuse across the EBS rule and pricing stack.

Usage Notes

DBMS_RULE_ADM is not typically invoked directly from EBS forms or concurrent programs. Instead, it is called by the higher-level EBS packages that the forms and concurrent managers delegate to during setup of pricing rules, eligibility criteria, or configurator models. Custom code and diagnostics should call the public procedures rather than the _INT variants. Because the package runs with invoker’s rights, the calling schema must hold the appropriate rule-engine system or object privileges before any create, alter, or drop operation succeeds.