Results for “notification_preference”

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

Overview

WF_PER_ROLE_ROLES is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the FND — Application Object Library product, and its documented status in ETRM is VALID. The view functions as an adapter or bridge between the Oracle Workflow (WF) role model and the Oracle HRMS person model: it presents person records from the PER schema in the column layout that Oracle Workflow expects for a role/principal source. In effect, it exposes each active employee as a Workflow role whose origin is derived from the person identifier.

Because the view conforms to the standard role-definition column list (name, display name, notification preference, e-mail address, origination system, status, and validity dates), it can be used by Workflow notification and directory components in the same manner as other WF role views. For reporting and integration purposes, WF_PER_ROLE_ROLES supplies a simple, join-free way to list active personnel as notification-capable principals.

Underlying Base Objects

The view is defined over a single documented base object: PER_ALL_PEOPLE_F, accessed through a synonym. The view text applies the INDEX_FFS hint against the PER_PEOPLE_F_PK index to encourage a fast full scan of the person table. The driving filter restricts output to rows where the current system date falls between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, so only currently effective person records are returned. The view therefore inherits the DateTrack (effective-dated) behaviour of PER_ALL_PEOPLE_F, meaning historical or future-dated versions of a person record are excluded.

No other base tables, joins, or PL/SQL functions are documented in the view definition. The relationship is therefore one-to-one between a currently effective PER_ALL_PEOPLE_F row and a row in WF_PER_ROLE_ROLES.

Key Columns

• NAME — Constructed as the literal prefix 'PER_ROLE:' concatenated with PER.PERSON_ID. This forms the unique role name used by Oracle Workflow.
• DISPLAY_NAME — Populated from PER.FULL_NAME; the human-readable label for the role.
• DESCRIPTION — Also populated from PER.FULL_NAME in the documented view text.
• NOTIFICATION_PREFERENCE — Hard-coded to 'MAILHTML', indicating HTML-formatted e-mail as the default notification channel.
• EMAIL_ADDRESS — Taken from PER.EMAIL_ADDRESS; the delivery address for notifications.
• ORIG_SYSTEM — Hard-coded to 'PER_ROLE', identifying the source system of the role.
• ORIG_SYSTEM_ID — Populated from PER.PERSON_ID, linking the role back to the person.
• START_DATE / EXPIRATION_DATE — Derived from the person record's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• STATUS — Hard-coded to 'ACTIVE'.
• LANGUAGE, TERRITORY, FAX, SECURITY_GROUP_ID, USER_FLAG, PARTITION_ID — Returned as NULL or fixed values, per the view text.

Common Use Cases and Queries

Typical uses include validating which employees are addressable as Workflow roles, troubleshooting notification routing, and reporting on active principals. A representative query lists active roles and their e-mail addresses:

SELECT name, display_name, email_address, status
FROM apps.wf_per_role_roles
WHERE email_address IS NOT NULL;

To resolve a specific person to their Workflow role name, filter on ORIG_SYSTEM_ID (the PERSON_ID):

SELECT name, display_name
FROM apps.wf_per_role_roles
WHERE orig_system_id = :person_id;

Because the view already restricts to currently effective records, no additional DateTrack predicate is normally required. Note the internal name format 'PER_ROLE:'||PERSON_ID when mapping these rows to Workflow notification recipients.