Search Results wf_routing_rules




Overview
Explore in AI Chat

Overview

The WF_ROUTING_RULES table is a core data object within the Oracle E-Business Suite (EBS) Application Object Library (FND) module. It is owned by the APPLSYS schema and is integral to the Oracle Workflow engine. As documented, its primary purpose is to store user-defined rules for processing notifications. These rules govern the dynamic routing and assignment of workflow notifications, enabling sophisticated, condition-based logic that determines the appropriate recipient or role based on runtime attributes of the workflow item. This functionality is critical for automating and personalizing business processes within EBS, moving beyond static role assignments.

Key Information Stored

The table's structure is designed to define and link routing rules to specific workflow entities. Its primary key is the RULE_ID column, which uniquely identifies each rule definition. As indicated by the foreign key relationships, the table is fundamentally linked to workflow message and item type definitions through the MESSAGE_TYPE and MESSAGE_NAME columns. These columns specify the exact notification (message) to which the routing rule applies. Other critical columns, while not explicitly listed in the brief metadata, typically include RULE_NAME, SEQUENCE (for ordering rule evaluation), and columns controlling the rule's active status and execution phase (e.g., for assignment or subscription). The rule's conditional logic is stored separately in the related WF_ROUTING_RULE_ATTRIBUTES table.

Common Use Cases and Queries

A primary use case is troubleshooting notification routing or auditing active routing rules within the system. Administrators often need to identify all rules defined for a particular workflow notification. A common query pattern involves joining to WF_MESSAGES for descriptive information:

  • SELECT wrr.rule_id, wrr.message_type, wrr.message_name, wm.display_name FROM apps.wf_routing_rules wrr, apps.wf_messages wm WHERE wrr.message_type = wm.type AND wrr.message_name = wm.name AND wrr.message_type = '<ITEM_TYPE>';

Another frequent scenario is analyzing the rule hierarchy and dependencies before a modification or upgrade. This involves querying the rule definitions and their associated attributes stored in WF_ROUTING_RULE_ATTRIBUTES using the RULE_ID as the join key to understand the full conditional logic.

Related Objects

The foreign key metadata explicitly defines the table's key relationships within the Workflow schema:

  • WF_MESSAGES: WF_ROUTING_RULES references this table via the composite foreign key on (MESSAGE_TYPE, MESSAGE_NAME). This ensures a rule is associated with a valid, defined notification message.
  • WF_ITEM_TYPES: WF_ROUTING_RULES references this table via MESSAGE_TYPE. This links the rule to the broader workflow item type definition.
  • WF_ROUTING_RULE_ATTRIBUTES: This table holds the conditional attributes for each rule and has a foreign key (RULE_ID) referencing WF_ROUTING_RULES.RULE_ID. This is a critical child table where the actual rule conditions (attribute, value, operator) are stored.

These relationships form a cohesive model where a rule (WF_ROUTING_RULES) for a specific item type and message is evaluated based on its detailed conditions (WF_ROUTING_RULE_ATTRIBUTES).