Search Results wf_ntf_rule_maps




Overview
Explore in AI Chat

Overview

The WF_NTF_RULE_MAPS table is a repository object owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. It is present and valid in both the 12.1.1 and 12.2.2 environments, with the 12.2.2 edition introducing the Oracle EBS online-patching column ZD_EDITION_NAME. The table stores the mapping between workflow notification rule definitions and the individual attributes or columns upon which those rules operate, acting as the configuration bridge that tells the Workflow Notification Mailer which data elements a given notification rule should evaluate or display.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. This is consistent with the absence of documented foreign key relationships and reflects the fact that WF_NTF_RULE_MAPS functions as a self-contained configuration catalog rather than a transactional hub or link. Modelers should treat it as a reference or configuration satellite-style artifact rather than a fact-bearing entity.

Key Information Stored

The documented physical schema in 12.2.2 contains five columns. The table's primary key and business-key candidate are both captured by the WF_NTF_RULE_MAPS_PK unique index, which spans RULE_NAME, COLUMN_NAME, and (in 12.2.2) ZD_EDITION_NAME.

  • RULE_NAME — The name of the notification rule to which the mapping applies. This is the leading component of the composite primary key and identifies the rule context.
  • COLUMN_NAME — The database column (or message attribute column) referenced by the notification rule. It is the second component of the composite primary key.
  • ATTRIBUTE_NAME — The logical attribute name associated with the column, allowing the rule to address the underlying data by its workflow-visible attribute identifier.
  • CREATION_DATE — The timestamp at which the mapping row was created, useful for auditing configuration changes.
  • ZD_EDITION_NAME — The Oracle EBS editioning column introduced by the 12.2.2 online patching architecture. It participates in the unique index and supports the edition-based redefinition model.

The composite key (RULE_NAME, COLUMN_NAME, ZD_EDITION_NAME) is a business-key candidate rather than a generated surrogate; neither a sequence-based single-column surrogate nor an FK-derived link is documented.

Common Use Cases and Queries

Administrators and developers query this table when diagnosing notification delivery problems, validating that a rule maps to the correct underlying data, or documenting workflow configuration for audit and migration. A typical inspection query retrieves all mappings for a specific rule:

SELECT RULE_NAME, COLUMN_NAME, ATTRIBUTE_NAME, CREATION_DATE
FROM   APPLSYS.WF_NTF_RULE_MAPS
WHERE  RULE_NAME = :rule_name
ORDER BY COLUMN_NAME;

Because the table is edition-aware in 12.2.2, queries that run under online patching should account for the ZD_EDITION_NAME column, since the standard edition resolves through the editioning view. Reporting use cases include building a catalog of notification rules and their attributes, comparing mappings between environments, and tracing unexpected attribute rendering during notification troubleshooting.

Related Objects

The ETRM metadata classifies WF_NTF_RULE_MAPS as standalone, so no explicit foreign keys are documented. In practice it is consulted alongside the broader Workflow notification configuration set, including the notification rule and attribute definition tables in the APPLSYS schema (such as the WF_NTF_RULES family) that share the RULE_NAME key space. Its columns also align with workflow message attribute metadata, allowing joins on COLUMN_NAME or ATTRIBUTE_NAME where message definitions are catalogued. The primary key index WF_NTF_RULE_MAPS_PK is the principal access path for lookups by rule and column. Because referential enforcement is absent, integrators should validate RULE_NAME and ATTRIBUTE_NAME against their source definitions before relying on this table as an authoritative configuration record.