Results for “column_values”

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

Overview

SYS.DBMS_RULE is the server-side rule engine supplied with Oracle Database and exposed to Oracle E-Business Suite through the SYS schema as a VALID package body. Within the EBS 12.1.1 and 12.2.2 environments, its business purpose is to evaluate a stored rule set against a client-supplied event context and return the subset of rules whose conditions are satisfied. The package is the internal engine behind the Oracle Rules Manager and Expression Filter features: rules are registered once, and at runtime the engine performs fast matching rather than iterative per-rule evaluation. In the ETRM inventory the object is classified under API classification OTHER, indicating it is not an EBS-owned business API; it is a database-supplied utility invoked indirectly by other components. Its presence in the ETRM reference confirms that the body is valid, compiled, and available to any session with EXECUTE privilege.

Key Procedures and Functions

The documented interface comprises rule evaluation and iterator control entry points:

• EVALUATE — Evaluates all rules in a named rule set against a provided event context and returns the matching rules. This is the primary entry point for batch or transactional rule firing.
• EVALUATE_EXPRESSION — Evaluates a single expression against a supplied data context, used where a discrete predicate test is required instead of a full rule-set pass.
• IS_FAST — Returns an indicator of whether a given rule or rule set can be evaluated using the optimized fast-path algorithm. It allows callers to choose between immediate evaluation and iterator-based retrieval.
• GET_NEXT_HIT — Retrieves the next matching rule from an open evaluation iterator, supporting incremental consumption of hits without materializing the entire result set.
• CLOSE_ITERATOR — Releases resources associated with an iterator opened by the evaluation routines, and must be called once iteration is complete.

These signatures are not documented in the supplied metadata; only names and functional intent are asserted here.

Tables Accessed

The ETRM dependency listing shows the body referencing the RE$ family of dictionary tables: RE$ATTRIBUTE_VALUE_LIST, RE$COLUMN_VALUE_LIST, RE$NV_LIST, RE$RULE_HIT, RE$RULE_HIT_LIST, RE$TABLE_ALIAS_LIST, RE$TABLE_VALUE_LIST, RE$VARIABLE_TYPE_LIST, and RE$VARIABLE_VALUE_LIST. These tables persist rule definitions, nested-table bind data, attribute and variable metadata, and the runtime hit lists produced during evaluation. The package also depends on SYS.DBMS_RULE_INTERNAL and SYS.DBMS_RULES_LIB for internal processing, and on the STANDARD package. No APPS synonym tables are recorded for this object.

Usage Notes

DBMS_RULE is not invoked directly by standard EBS forms or concurrent programs; it is called by EBS and database components that build rule sets, typically through the higher-level Rules Manager interface. Custom code that requires rule evaluation may call the package directly, but must first register rules and contexts in the RE$ tables. Callers should check IS_FAST before selecting an evaluation strategy, and must always pair iterator usage with CLOSE_ITERATOR to avoid session resource leaks. Because the object resides in SYS and is documented as not referenced by any database object, it should be treated as a stable database-owned facility rather than an EBS-supported customization point; the user search string "10.25.4.41/re" reflects a host-relative ETRM reference path rather than a schema object.