Search Results index_ffs

Overview

APPS.WF_PER_ROLE_ROLES is an Oracle Workflow dictionary view that exposes Oracle HRMS person records as workflow roles. It is one of the role-generating views used by the Workflow Notification System to resolve addressable roles when notifications are dispatched. In Oracle EBS 12.1.1 and 12.2.2, this view is referenced by role-hierarchy and notification routing processes, and it is commonly queried during diagnostics of approval workflows, vacation rules, and notification mailers where a person must be treated as a routable recipient.

The view is owned by APPS and is not a base table; it is a runtime projection over HR person data. Rather than exposing a physical role definition, it dynamically generates a role string of the form PER_ROLE:<PERSON_ID> for every currently effective person, allowing Workflow to address any employee as a role without requiring a pre-registered role row.

Underlying Base Objects

The view is defined over a single documented base object: PER_ALL_PEOPLE_F, referenced in the ETRM metadata as a synonym. This is the datetracked, effective-dated HR table that holds person records in Oracle Human Resources.

The driving predicate is TRUNC(SYSDATE) BETWEEN PER.EFFECTIVE_START_DATE AND PER.EFFECTIVE_END_DATE, which restricts output to persons whose record is current as of the system date. The view text carries the hint /*+ INDEX_FFS(PER, PER_PEOPLE_F_PK) */, an index fast full scan on PER_PEOPLE_F_PK. Because only the current slice of each person's datetracked record is selected, the view returns one role row per active person rather than one row per datetracked version. Organizations that purge or end-date person records will see those persons disappear from role resolution automatically.

Key Columns

• 'PER_ROLE:'||PER.PERSON_ID — The generated role name, presented as the role identifier that Workflow consumes.
• PER.FULL_NAME — Person display name, projected twice (name and display-name positions in the Workflow role definition).
• 'MAILHTML' — The notification preference/format indicator returned for the role.
• PER.EMAIL_ADDRESS — The person's primary email address, used to route email notifications.
• 'PER_ROLE' — The role type literal, marking the row as a person-based role.
• PER.PERSON_ID — The numeric person identifier, exposed both inside the role string and as a discrete column.
• PER.EFFECTIVE_START_DATE / PER.EFFECTIVE_END_DATE — Datetrack effective bounds for the current person record.
• 'ACTIVE' — Role status literal returned for every row.
• 'N' and 3 — Notification/role attribute literals forming part of the Workflow role definition.

Common Use Cases and Queries

The view is typically used to confirm that a person resolves as a Workflow role, to reproduce the address that Workflow would use, or to enumerate valid PER_ROLE recipients.

SELECT role_name, display_name, email_address
FROM   apps.wf_per_role_roles
WHERE  role_name = 'PER_ROLE:' || :person_id;

For bulk validation of role availability across an organization:

SELECT role_name, display_name, email_address
FROM   apps.wf_per_role_roles
WHERE  email_address IS NOT NULL
ORDER  BY display_name;

Because the view derives entirely from the current datetracked slice of PER_ALL_PEOPLE_F, results are always evaluated as of SYSDATE. Troubleshooting a missing PER_ROLE should therefore begin by checking the person's EFFECTIVE_START_DATE/EFFECTIVE_END_DATE range in PER_ALL_PEOPLE_F.