Results for “per_role_roles_v”

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

Overview

PER_ROLE_ROLES_V is a VALID view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and is documented as being used for the Workflow Directory Service. The view exposes a directory-style role abstraction for every active person record, generating a synthetic role name of the form "PER_ROLE:" concatenated with the person identifier. In effect, it maps PER_ALL_PEOPLE_F rows into the column shape expected by the Oracle Workflow directory service, allowing Workflow notification addressing and role resolution to treat each employee as an addressable role. Because it is a view and not a table, it presents no independent storage; all values are derived at query time from the current effective person record, which makes it inherently self-maintaining with respect to person attribute changes such as name, e-mail address, and employment status.

Underlying Base Objects

The documented metadata lists two referenced base objects: the synonym PER_ALL_PEOPLE_F (resolving to the PER_ALL_PEOPLE_F table in the APPS schema) and the package WF_PREF. The view text selects exclusively from PER_ALL_PEOPLE_F, filtered by the clause TRUNC(SYSDATE) BETWEEN PER.EFFECTIVE_START_DATE AND PER.EFFECTIVE_END_DATE, so only currently effective person rows are exposed. Because PER_ALL_PEOPLE_F is a date-tracked (effective-dated) table, the view always reflects the person's current state. The display name derivation uses the HR_INFORMAL_NAME_FORMAT profile option, resolved through FND_PROFILE_OPTION_VALUES and FND_PROFILE_OPTIONS at level value 0 and level ID 10001 (site level); when that profile is null, the full name is returned unchanged. WF_PREF is the Workflow preference package referenced by the underlying directory service infrastructure rather than by the view text itself.

Key Columns

• NAME — The role identifier, built as 'PER_ROLE:'||PERSON_ID. This is the value Workflow uses to address the role.
• DISPLAY_NAME — The formatted person name, built by substituting tokens such as $FI, $MI, $LA, $PR, $SU, $TI, $FU, $KN, $IF, and $IM in the HR_INFORMAL_NAME_FORMAT profile value. Falls back to FULL_NAME when the profile is unset.
• DESCRIPTION — Populated with PER.FULL_NAME.
• EMAIL_ADDRESS — The person's e-mail address from PER_ALL_PEOPLE_F, used as the notification delivery address.
• NOTIFICATION_PREFERENCE — A literal 'MAILHTML', indicating HTML-formatted mail notification.
• ORIG_SYSTEM / ORIG_SYSTEM_ID — Literal 'PER_ROLE' and the PERSON_ID, identifying the source system of the directory entry.
• STATUS — A literal 'ACTIVE', since only current effective rows are returned.
• USER_FLAG — Literal 'N', indicating the entry is a role rather than an individual user.
• START_DATE, EXPIRATION_DATE, LANGUAGE, TERRITORY, FAX, SECURITY_GROUP_ID — Returned as NULL, present to satisfy the directory service column contract.
• PARTITION_ID — Literal 3.

Common Use Cases and Queries

Typical uses include resolving Workflow notification recipients, validating that a person is addressable as a PER_ROLE, and joining person attributes to Workflow directory data. A representative query retrieves current roles with their delivery addresses:

• SELECT name, display_name, email_address FROM apps.per_role_roles_v WHERE status = 'ACTIVE';
• SELECT orig_system_id, display_name FROM apps.per_role_roles_v WHERE email_address IS NOT NULL;
• SELECT r.name, r.display_name, p.employee_number FROM apps.per_role_roles_v r, apps.per_all_people_f p WHERE r.orig_system_id = p.person_id AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

Because the view is restricted to currently effective person rows, consumers should not rely on it for historical or future-dated role resolution. Name formatting behaviour depends entirely on the site-level HR_INFORMAL_NAME_FORMAT profile setting.