Search Results preference_name




Overview
Explore in AI Chat

Overview

APPS.WF_FND_USR_ROLES is an Oracle E-Business Suite view that consolidates workflow-relevant role and user information from the Oracle Workflow directory service together with FND user account data. It presents a unified list of notification recipients — both FND application users and Oracle Workflow "PER" roles originating from HR/permissions data — along with their mail type, language, and territory preferences. In Oracle EBS 12.1.1 and 12.2.2, this view is primarily consumed by the Workflow Notification Mailer and related workflow components to resolve how and to whom a notification should be delivered, including formatting (MAILHTML), language, and territory settings. Because it joins FND_USER with WF_LOCAL_ROLES (the PER_ROLE partition) and preference records, it serves as a bridge between the FND user model and the Workflow role model used in routing and addressing of workflow notifications. Reporters and integrators can query it to enumerate active users and roles, their e-mail addresses, and their effective workflow preferences.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms in APPS: FND_USER, FND_USER_PREFERENCES, and WF_LOCAL_ROLES. The core structure is a UNION ALL of two branches:

  • PER branch — Joins FND_USER to the WF_LOCAL_ROLES PER_ROLE partition (aliased PER), where PER.ORIG_SYSTEM_ID equals USR.EMPLOYEE_ID, restricting rows to roles that are currently valid via SYSDATE BETWEEN NVL(PER.START_DATE, SYSDATE) AND NVL(PER.EXPIRATION_DATE, SYSDATE+1). Three outer joins to FND_USER_PREFERENCES (aliased fup1, fup2, fup3) supply MAILTYPE, LANGUAGE, and TERRITORY preferences for module_name 'WF', each falling back to the '-WF_DEFAULT-' user preference when no user-specific value exists.
  • FND_USR branch — Selects FND_USER rows where EMPLOYEE_ID IS NULL, assigning fixed defaults (MAILHTML, AMERICA, AMERICAN) and the 'FND_USR' role designation.

This design explains why the user's search term "module_name" is significant: the view filters FND_USER_PREFERENCES on module_name = 'WF' for each preference lookup.

Key Columns

  • USER_NAME — The FND user login name (from FND_USER) in the PER branch; the PER branch uses the user name, while the FND_USR branch returns USR.USER_NAME in both name columns.
  • DISPLAY_NAME — From WF_LOCAL_ROLES.DISPLAY_NAME in the PER branch; falls back to USER_NAME in the FND_USR branch.
  • DESCRIPTION — Role/user description.
  • MAILTYPE, LANGUAGE, TERRITORY — Derived preference values (with '-WF_DEFAULT-' fallbacks of MAILHTML, AMERICAN, AMERICA). Note ordering in the select list: MAILTYPE, LANGUAGE, TERRITORY.
  • EMAIL_ADDRESS, FAX — Contact attributes from FND_USER.
  • Role source indicator — 'PER' or 'FND_USR', distinguishing HR-derived roles from pure FND users.
  • ORIG_SYSTEM_ID / USER_ID — PER.ORIG_SYSTEM_ID in the PER branch; USR.USER_ID in the FND_USR branch.
  • START_DATE, END_DATE — Validity window; a computed status column returns 'INACTIVE' when the remaining duration begins with '-', otherwise 'ACTIVE'.

Common Use Cases and Queries

Typical uses include auditing notification recipients, verifying preference resolution, and troubleshooting missing or defaulted delivery settings.

  • List active workflow recipients with delivery preferences:
    SELECT user_name, display_name, mailtype, language, territory, email_address FROM apps.wf_fnd_usr_roles WHERE status = 'ACTIVE';
  • Find users defaulting to workflow-level preferences:
    SELECT user_name, mailtype FROM apps.wf_fnd_usr_roles WHERE mailtype = 'MAILHTML';
  • Distinguish role source populations:
    SELECT user_name FROM apps.wf_fnd_usr_roles WHERE role_source = 'FND_USR';

Because preference resolution depends on module_name = 'WF' rows in FND_USER_PREFERENCES, the view is also useful when diagnosing why a given user receives notifications in a particular language or format.