Search Results wf_routing_rules_s

Overview

APPS.WF_ROUTE is the Oracle Workflow routing engine package body responsible for evaluating routing rules and rendering the administrative interface used to maintain them. In Oracle E-Business Suite 12.1.1 and 12.2.2, WF_ROUTE serves two distinct business functions. First, it provides the runtime logic that determines how a workflow item is routed to the appropriate role or performer based on the routing rules defined for an item type and activity. Second, it exposes the HTML-based administrative screens — list frames, buttons, and selection lists — through which administrators create, update, and delete those routing rules. The package is classified as OTHER in the ETRM metadata and is validated in the APPS schema. It is a foundational component of the Workflow Notification System, and its rule maintenance routines are what populate and modify the WF_ROUTING_RULES tables that drive runtime routing decisions across every workflow-enabled application in the E-Business Suite.

Key Procedures and Functions

The documented API surface of WF_ROUTE comprises thirteen procedures and functions. The rule maintenance entry points are CREATERULE, CREATERULE1, CREATERULE2, CREATERULE3, and CREATERULE (the framework recursion overloads), which together persist a new routing rule and its associated rule attributes. UPDATERULE and SUBMITUPDATE handle modification of existing rules and the submission of those changes from the HTML interface. DELETERULE removes a rule and its dependent attribute records. FIND performs rule lookup and validation against the routing rules tables. CHANGEMESSAGENAME updates the message name associated with a rule, supporting the maintenance of notification message bindings. The presentation-layer routines LISTFRAME, LIST, and LISTBUTTON generate the HTML list frame and the associated list and button widgets used by the routing rule administration pages. No parameter lists are invented here; the ETRM metadata documents procedure existence and dependency only.

Tables Accessed

WF_ROUTE reads and writes the core routing rule entities. WF_ROUTING_RULES stores the routing rule header definitions, and WF_ROUTING_RULES_S is the corresponding sequence and surrogate identifier source referenced by the user search term "wf_routing_rules_s". WF_ROUTING_RULE_ATTRIBUTES holds the per-rule attribute conditions that determine when a rule fires. WF_ITEM_ATTRIBUTES supplies item type attribute metadata used to validate and resolve rule conditions, while WF_ITEM_TYPES_VL provides the item type definitions against which rules are scoped. Supporting lookups come from WF_LOOKUPS, WF_MESSAGES_VL, and WF_MESSAGE_ATTRIBUTES_VL. Directory and role data are obtained from WF_DIRECTORY and WF_ROLE_LOV_VL, and workflow engine services are accessed through WF_CORE and WF_PREF. The HTML output routines depend on the PL/SQL web toolkit packages HTF, HTP, and OWA_UTIL, which are resolved through APPS synonyms.

Usage Notes

WF_ROUTE is not a public integration API and is not referenced by any other database object, including within APPS. It is invoked internally by the Workflow Administration HTML pages when an administrator defines or maintains routing rules, and by the workflow engine when routing rules must be evaluated during notification processing. Custom code should not call the CREATERULE, UPDATERULE, or DELETERULE routines directly, because they assume the presence of the HTML session context and perform no external validation. Developers integrating with workflow routing should instead treat WF_ROUTING_RULES, WF_ROUTING_RULES_S, and WF_ROUTING_RULE_ATTRIBUTES as read-only reference data and use the supported Workflow APIs exposed by WF_CORE and the Workflow definition loader for any programmatic rule changes. When diagnosing routing behavior, querying WF_ROUTING_RULES and its attribute table through the standard Workflow administrator responsibility remains the supported approach.