Search Results wf_ntf_rules_pk

Overview

APPLSYS.WF_NTF_RULES is a core Oracle Workflow repository table that stores notification rule definitions used by the Oracle E-Business Suite notification mailer and Workflow Notification System. Each row represents a named notification rule that governs how Workflow delivers, routes, or suppresses notification messages generated by workflow processes, alerts, and business event subscriptions. Because notification rules are frequently customized or extended by implementers (for example, to override the default "Send Me Mail" behavior or to define routing rules for a responsibility or role), the table acts as a configuration control point rather than a purely transactional store.

From a Data Vault modeling perspective, the mined heuristic classifies this object as standalone. This suggests the table behaves as an independent reference or configuration hub in the surrounding model, with no documented foreign key dependencies to other tables. It can therefore be modeled as an isolated hub for the rule business key, with the descriptive attributes treated as satellite data. The absence of inbound or outbound FK relationships documented in the schema reflects the fact that notification rules are resolved at runtime by the Workflow engine rather than enforced through declarative constraints.

Key Information Stored

The primary key documented in the ETRM metadata is WF_NTF_RULES_PK, which is defined over RULE_NAME and, in the 12.2.2 schema, additionally over ZD_EDITION_NAME. The presence of ZD_EDITION_NAME in the unique index reflects the Oracle Online Patching / Editioning model introduced in EBS 12.2, which allows configuration data to be editioned during patching cycles. In 12.1.1 this column is absent, and RULE_NAME alone governs uniqueness.

• RULE_NAME — The business-key identifier of the notification rule; unique in 12.1.1 and part of the composite unique key in 12.2.2.
• ZD_EDITION_NAME — Editioning column used by Online Patching; part of the composite primary key in 12.2.2.
• OWNER_NAME — Name of the owner (user, role, or responsibility) to which the rule applies; 30 characters.
• OWNER_TAG — Categorizes the owner type (for example, user versus role versus responsibility), qualifying the OWNER_NAME value.
• CUSTOMIZATION_LEVEL — Indicates the customization tier of the rule (typically Core versus Extended), controlling whether user modifications persist through patching.
• PHASE — Numeric sequencing or processing phase indicator used by the notification engine when evaluating multiple rules.
• STATUS — Activation state of the rule, determining whether it is evaluated at runtime.
• CREATION_DATE — Timestamp of when the rule row was created, useful for auditing and configuration drift analysis.

Common Use Cases and Queries

Administrators and technical consultants query this table to audit notification routing configuration, diagnose why a user receives or fails to receive a Workflow notification, or compare seeded versus customized rules following an upgrade. A typical pattern retrieves all active rules for a specific owner:

• List all rules with their owners and customization levels: SELECT RULE_NAME, OWNER_NAME, OWNER_TAG, CUSTOMIZATION_LEVEL, STATUS, PHASE FROM APPLSYS.WF_NTF_RULES ORDER BY OWNER_NAME, PHASE;
• Identify customized or extended rules that may need re-validation after a patch: SELECT RULE_NAME, CREATION_DATE FROM APPLSYS.WF_NTF_RULES WHERE CUSTOMIZATION_LEVEL = 'U';
• Confirm the business key exists before updating: join or filter on RULE_NAME matching the unique index WF_NTF_RULES_PK.

In 12.2.2 environments, edition-aware queries should include ZD_EDITION_NAME or rely on the running-edition view to avoid returning obsolete edition rows.

Related Objects

The ETRM dependency metadata notes that WF_NTF_RULES does not reference any database object and is referenced only by the editioned variant WF_NTF_RULES#. Related objects that consult or complement this table include:

• APPLSYS.WF_NTF_RULES# — Editioning companion object in 12.2.2, resolved through the editioning view.
• WF_NOTIFICATIONS — The runtime notification records whose delivery behavior is influenced by rule evaluation.
• WF_NTF_PREFERENCES (and related preference objects) — User-level notification preferences applied alongside rules.
• WF_ROLES / WF_LOCAL_ROLES — Resolve OWNER_NAME values to workflow roles and users.
• FND_USER — Correlates OWNER_NAME with an application user account.
• WF_NOTIFICATION_ATTRIBUTES — Provides runtime attribute context consumed during rule evaluation.

Because the table is classified as standalone, no enforced joins are documented; the relationships above are logical, resolved by the Workflow Notification System at runtime rather than by foreign keys.