Results for “begin_date”

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

Overview

WF_ROUTING_RULES is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores user-defined routing rules that determine how Oracle Workflow processes notifications. When a notification message is generated, the Workflow Notification System evaluates the rules defined in this table to decide which role receives the notification and what action is applied, effectively tailoring default notification delivery behavior at the message and item type level.

From a dimensional modeling perspective, the ETRM metadata classifies this object as satellite-leaning. That classification is a heuristic suggestion rather than a physical constraint: the table carries a single-column surrogate primary key and descriptive rule attributes, so it behaves like a satellite attached to the notification message and item type hubs, with an additional link to the rule attributes child. Architects should treat the classification as guidance, not as a normative Data Vault designation.

Key Information Stored

The table contains ten documented columns. The surrogate primary key is RULE_ID, defined by the unique index WF_ROUTING_RULES_PK. No other unique index is documented, so RULE_ID is the sole business-key candidate identified in the ETRM metadata.

• RULE_ID — Surrogate primary key; uniquely identifies each routing rule row.
• ROLE — The role or user to which the notification is routed when the rule matches.
• ACTION — The action applied to the notification, such as routing, forwarding, or responding.
• ACTION_ARGUMENT — Parameter supplied to the action, for example the target role of a forwarding action.
• MESSAGE_TYPE — The workflow item type associated with the rule; part of the rule's matching context.
• MESSAGE_NAME — The notification message name within the item type; together with MESSAGE_TYPE it identifies the message the rule governs.
• BEGIN_DATE — The effective start date of the rule.
• END_DATE — The effective end date, after which the rule no longer applies.
• RULE_COMMENT — Free-text description of the rule's intent, useful for auditing and administration.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-organization security partitioning.

Common Use Cases and Queries

Administrators typically query this table to audit which rules are active for a given notification, to troubleshoot misrouted notifications, or to identify expired rules that remain enabled. A common pattern filters by message identity and current date:

• SELECT rule_id, role, action, action_argument, begin_date, end_date FROM wf_routing_rules WHERE message_type = :p_type AND message_name = :p_name AND SYSDATE BETWEEN NVL(begin_date, SYSDATE) AND NVL(end_date, SYSDATE + 1);
• Reporting on expired or future-dated rules: filter rows where END_DATE is less than SYSDATE or BEGIN_DATE is greater than SYSDATE.
• Joining to WF_ITEM_TYPES and WF_MESSAGES to resolve display names for message_type and message_name.
• Enumerating rules per security group when diagnosing visibility problems in a multi-org environment.

Related Objects

The documented foreign key relationships define the principal dependencies for this table.

• WF_ROUTING_RULE_ATTRIBUTES — Child table joined on RULE_ID; stores attribute-level conditions that further qualify a routing rule.
• WF_MESSAGES — Referenced through MESSAGE_TYPE and MESSAGE_NAME; supplies the message definition the rule targets.
• WF_ITEM_TYPES — Referenced through MESSAGE_TYPE; defines the workflow item type owning the message.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID; governs which security group the rule belongs to.
• WF_ROUTING_RULES_PK — The primary key index enforcing uniqueness of RULE_ID.

These relationships should be honored in any extraction or replication logic, since WF_ROUTING_RULE_ATTRIBUTES depends directly on the RULE_ID values maintained here.