Search Results wf_ntf_rule_maps_pk

Overview

APPLSYS.WF_NTF_RULE_MAPS is an Oracle E-Business Suite configuration table that defines the column-to-attribute mapping used by the Workflow Notification Mailer when constructing and parsing notification messages. It sits alongside WF_NTF_RULES within the Workflow notification subsystem, providing the metadata that instructs the notification engine which notification attribute (such as TO, FROM, SUBJECT, or BODY) is populated from which underlying data column in the notification rule definition. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the APPLSYS schema, carries the FND design data reference FND.WF_NTF_RULE_MAPS, holds VALID status, and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Under the heuristic Data Vault classification derived from its foreign key structure, the object is modeled as a standalone reference or lookup table rather than a hub, link, or satellite; it holds descriptive mapping detail rather than representing a business entity or a transactional relationship.

Key Information Stored

The table is narrow, and its meaning is concentrated in a small number of columns:

• RULE_NAME (VARCHAR2(30)) — the notification rule to which the mapping belongs. This column participates in the composite primary key and is also the foreign key that ties each row to WF_NTF_RULES.RULE_NAME.
• COLUMN_NAME (VARCHAR2(30)) — the data column on the source record from which the notification value is drawn. Together with RULE_NAME it forms the second component of the composite primary key.
• ATTRIBUTE_NAME (VARCHAR2(30)) — the notification attribute that the column populates, for example a recipient, subject, or message body field. It is the payload of the mapping and is not part of the key.
• CREATION_DATE (DATE) — the audit timestamp recording when the mapping row was inserted, useful for change tracking and support diagnostics.
• ZD_EDITION_NAME — the editioning column introduced in the 12.2 online patching architecture, which allows mapping definitions to be maintained in an editioned fashion across patching cycles.

The documented surrogate primary key is WF_NTF_RULE_MAPS_PK over (RULE_NAME, COLUMN_NAME). In the 12.2.2 physical schema the unique index is reported as (RULE_NAME, COLUMN_NAME, ZD_EDITION_NAME), so the edition discriminator is part of the uniqueness guarantee in that release even though the logical business-key candidates remain RULE_NAME and COLUMN_NAME.

Common Use Cases and Queries

The primary operational use case is troubleshooting notification mailer behavior: when a notification is delivered with an incorrect recipient, subject, or body, the mapping rows reveal which source column feeds the affected attribute. A simple diagnostic query follows:

• SELECT RULE_NAME, COLUMN_NAME, ATTRIBUTE_NAME, CREATION_DATE FROM APPLSYS.WF_NTF_RULE_MAPS WHERE RULE_NAME = :rule ORDER BY ATTRIBUTE_NAME;
• Join the mapping to the rule header to review rule and mapping together: SELECT m.RULE_NAME, m.COLUMN_NAME, m.ATTRIBUTE_NAME FROM APPLSYS.WF_NTF_RULE_MAPS m, APPLSYS.WF_NTF_RULES r WHERE m.RULE_NAME = r.RULE_NAME;
• Identify rules whose attributes are unmapped or duplicated by grouping on RULE_NAME and ATTRIBUTE_NAME.
• Audit recent configuration changes using CREATION_DATE to isolate recently added or modified mappings during a support window.

Reporting against this table is typically limited to configuration audits, notification design documentation, and migration verification when rules are promoted between environments.

Related Objects

The direct parent of this table is WF_NTF_RULES, joined on RULE_NAME; every mapping row must reference an existing rule, and the Workflow Notification Mailer APIs that evaluate rules consume both objects together. The companion rule definition tables, including WF_NTF_RULE_ATTRIBUTES and the broader WF_NTF_* notification configuration family, are frequently reviewed alongside these mappings during notification design and review. Because the table is classified as standalone in the Data Vault heuristic, it references no objects beyond WF_NTF_RULES and is referenced by no child tables; the APPS synonym WF_NTF_RULE_MAPS is the standard access path used by application code and reports rather than querying APPLSYS directly.