Search Results wf_ntf_rules




Overview
Explore in AI Chat

Overview

WF_NTF_RULES is a configuration table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND – Application Object Library product. It stores the notification rule definitions used by the Oracle Workflow Notification System (WFNTF) to control how notifications are generated, delivered, and customized during workflow-driven business processes. In EBS 12.1.1 and 12.2.2, this table acts as the repository for rule metadata that governs notification behavior such as defaulting, escalation, and delivery attributes propagated to runtime notification mailers and the Notification Worklist.

The ETRM relationship metadata classifies WF_NTF_RULES as standalone based on mining of its foreign-key structure. In Data Vault modeling terms, this suggests treating the object as a hub-like reference table: the natural business key is the rule name, and the surrounding attributes (owner, phase, status, customization level) behave as descriptive satellite attributes. Because no FK dependencies were mined, no link tables are proposed by the ETRM heuristic, and any associative relationships to notification runtime tables must be inferred from application semantics rather than enforced referential integrity.

Key Information Stored

The documented physical schema for ETRM 12.2.2 records eight columns in APPLSYS.WF_NTF_RULES. The most significant are:

  • RULE_NAME – The business-key candidate and part of the primary key WF_NTF_RULES_PK. Identifies the notification rule uniquely within an edition.
  • ZD_EDITION_NAME – The edition discriminator used by EBS Edition-Based Redefinition (EBR). It completes the unique index WF_NTF_RULES_PK (RULE_NAME, ZD_EDITION_NAME), meaning the true business key is rule name combined with edition.
  • OWNER_TAG – Tag identifying the owning entity (for example, a workflow item type) to which the rule is scoped.
  • OWNER_NAME – The internal name of the owning object or component.
  • CREATION_DATE – Timestamp recording when the rule row was created, used for audit and change tracking.
  • CUSTOMIZATION_LEVEL – Indicates the customization tier of the rule (for example, core versus customer-level), influencing upgrade and patching behavior.
  • PHASE – Denotes the lifecycle or processing phase in which the rule applies.
  • STATUS – The active/inactive state of the rule, controlling whether it is evaluated at runtime.

The surrogate primary key is WF_NTF_RULES_PK; because EBR is enabled, the unique constraint spans RULE_NAME and ZD_EDITION_NAME. No non-key surrogate identifier column is documented beyond these.

Common Use Cases and Queries

Typical uses include auditing active notification rules, reviewing customization levels prior to patching or upgrading, and troubleshooting notifications that fail to fire. A representative query lists active rules for a given owner:

  • SELECT rule_name, owner_name, phase, status, customization_level FROM applsys.wf_ntf_rules WHERE owner_name = :owner AND status = 'ACTIVE';
  • Reporting rules by creation date to identify recently introduced configurations: SELECT rule_name, creation_date FROM applsys.wf_ntf_rules ORDER BY creation_date DESC;
  • Filtering by edition when analyzing EBR-aware environments: SELECT rule_name, zd_edition_name FROM applsys.wf_ntf_rules WHERE zd_edition_name = :edition;

Because the table is standalone from an FK perspective, joins to runtime notification tables are performed on business columns (typically RULE_NAME or OWNER_NAME) rather than enforced keys, and DBAs should validate such joins against application logic.

Related Objects

The ETRM metadata documents no outbound FK relationships for WF_NTF_RULES. The following objects are commonly referenced alongside it in Oracle Workflow and Notification configuration:

  • WF_NOTIFICATIONS – Runtime notification instances generated under the rules defined here.
  • WF_NOTIFICATION_ATTRIBUTES – Attribute values applied to notifications, often driven by rule defaults.
  • WF_ITEM_TYPES (joined via OWNER_NAME where the owner is a workflow item type).
  • WF_MESSAGES – Message definitions referenced during notification creation.
  • WF_ROLES and WF_LOCAL_ROLES – Recipient resolution tables used when rules determine delivery targets.
  • FND_LOOKUPS – Frequently used to resolve STATUS, PHASE, and CUSTOMIZATION_LEVEL values.
  • WF_NTF_RULES_PK – The primary key constraint enforcing RULE_NAME plus ZD_EDITION_NAME uniqueness.

When integrating or extending notification behavior, administrators should treat WF_NTF_RULES as the authoritative definition repository and confirm that any custom rules align with EBR editioning and customization-level rules before promotion to production.