Results for “wf_ntf_rules_tl”

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

Overview

WF_NTF_RULES_TL is a translated (TL) table in the APPLSYS schema of Oracle E-Business Suite, owned by the FND — Application Object Library product. It stores language-specific, translatable attributes for notification rules defined within the Oracle Workflow notification subsystem. In Oracle EBS, notification rules govern how workflow notifications are routed, attributed, and formatted, and the "_TL" designation indicates that this table holds the multilingual descriptions and translated user-facing names associated with the base rule definitions. This separation of base and translated content is a standard EBS globalization pattern, allowing seeded and custom notifications to present localised text without duplicating the underlying rule logic per language.

From a modeling perspective, the metadata heuristically classifies this object as a standalone Data Vault candidate — that is, it does not participate in FK-driven relationships with other documented tables and can be treated as an independent satellite of rule-level descriptive attributes keyed by rule name and language, rather than as a hub or link. This classification is a suggestion only, derived from the absence of mined foreign-key dependencies.

Key Information Stored

The table contains eight documented columns, of which the following are most significant:

• RULE_NAME — The internal identifier of the notification rule. This forms part of both the primary key and the unique business-key index.
• LANGUAGE — The language code for the translated row, also part of the primary key and unique index.
• USER_RULE_NAME — The translatable, user-facing name of the notification rule as displayed to end users in the selected language.
• DESCRIPTION — The translated long description explaining the purpose or behaviour of the notification rule.
• SOURCE_LANG — The source language from which the translation was derived, used in EBS translation workflows to track original language content.
• OWNER_TAG — Identifies the owning context or application tag for the rule, distinguishing seeded product rules from customer-defined rules.
• CREATION_DATE — Standard audit column capturing when the translated row was created.
• ZD_EDITION_NAME — The editioning column used in the EBS 12.2 online patching (adop) architecture to support edition-based redefinition. It appears in the unique index WF_NTF_RULES_TL_PK (RULE_NAME, LANGUAGE, ZD_EDITION_NAME).

The surrogate primary key WF_NTF_RULES_TL_PK spans RULE_NAME and LANGUAGE, with ZD_EDITION_NAME added to the unique index under editioning. There is no independently generated surrogate sequence key; identification is entirely by the natural business key of rule name plus language.

Common Use Cases and Queries

Typical usage involves resolving the appropriate translated text for a given notification rule at run time, or reporting on the descriptions of rules present in the system. A common pattern joins this table to its base table by rule name and language and filters on the current session language:

• Retrieving the user-facing name and description for a specific rule: SELECT USER_RULE_NAME, DESCRIPTION FROM WF_NTF_RULES_TL WHERE RULE_NAME = :p_rule_name AND LANGUAGE = USERENV('LANG');
• Auditing rules that lack a translation in a target language by comparing against a language list.
• Reporting on custom versus seeded rules using OWNER_TAG to isolate customer-defined notifications.
• Migration and export scripts that reconstruct a rule's presentation text for a given locale.

When querying, restrict by ZD_EDITION_NAME (or rely on the editioning view exposing the run edition) to avoid returning rows from multiple editions during an online patching cycle in 12.2.x.

Related Objects

The base (non-translated) notification rule definition table supplies the language-independent rule metadata and is the principal partner to this object; the join is on RULE_NAME. Also relevant are the supporting FND language and territory tables used to resolve LANGUAGE codes, the Oracle Workflow notification mailer configuration views that consume rule text, and the ETRM-documented WF notification rule base objects appearing alongside WF_NTF_RULES_TL in the APPLSYS schema. Because the metadata classifies this table as standalone, no hard foreign-key relationships to other documented tables were mined, and joins are therefore maintained logically through RULE_NAME rather than through enforced referential constraints.