Results for “per_role”

20 results




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

Overview

WF_ROLE_LOV_VL is an Oracle E-Business Suite view owned by the APPS schema and validated in releases 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product family and exists within the Oracle Workflow role model. The view presents a translatable, language-sensitive list of values (LOV) of workflow roles, drawing together the base role definition and its translated display attributes. Its defining characteristic is that it returns one consolidated row per role, matching the base role record to its translation in the session language where available, and falling back to the base record when no translation exists.

In reporting, the view functions as a convenient, ready-to-query source for role LOV lookups. In integration and workflow configuration, it serves the same purpose that the standard Workflow role LOV uses in the EBS forms: exposing only valid, non-expired, non-personal roles for selection and display.

Underlying Base Objects

The ETRM metadata records two referenced base objects, both exposed to APPS as synonyms:

  • WF_LOCAL_ROLES — the core role table, holding role names and their attributes.
  • WF_LOCAL_ROLES_TL — the translated (TL) companion table, holding the language-specific display name and description.

The view text defines two branches combined with UNION ALL. The first branch joins WF_LOCAL_ROLES (aliased WR) to WF_LOCAL_ROLES_TL (aliased WRT) on NAME, ORIG_SYSTEM, ORIG_SYSTEM_ID, and PARTITION_ID, filtered to the session language via USERENV('LANG'). The second branch selects from WF_LOCAL_ROLES alone where no matching translated row exists for the session language, guaranteeing that untranslated roles still appear. Both branches apply the following filters: PARTITION_ID <> 3 (which excludes the PER_ROLE partition, i.e., person-level roles), and NVL(EXPIRATION_DATE, SYSDATE+1) > SYSDATE, excluding expired roles.

Key Columns

  • NAME — the internal role name; a key used for joins and lookups.
  • DISPLAY_NAME — the translated, user-facing role name.
  • DESCRIPTION — the translated description of the role.
  • NOTIFICATION_PREFERENCE — the role's default notification channel.
  • LANGUAGE, TERRITORY — locale attributes associated with the role.
  • EMAIL_ADDRESS, FAX — contact attributes exposed for messaging.
  • ORIG_SYSTEM, ORIG_SYSTEM_ID — the source system and identifier of the role.
  • PARENT_ORIG_SYSTEM, PARENT_ORIG_SYSTEM_ID — the role's parent in the role hierarchy.
  • START_DATE, EXPIRATION_DATE, STATUS — role lifecycle and validity attributes.
  • OWNER_TAG, PARTITION_ID — ownership and partition classification of the role.

Common Use Cases and Queries

Typical scenarios include building custom LOVs, resolving a role's display name for a report, and validating that a role is active and non-personal before routing notifications. A representative query lists active roles with their translated names:

  • SELECT name, display_name, orig_system, status
  • FROM wf_role_lov_vl
  • WHERE status = 'ACTIVE'
  • ORDER BY display_name;

To resolve a specific role's display name, filter on NAME. Because the view already excludes PER_ROLE records (PARTITION_ID = 3) and expired roles, no additional expiration or partition predicates are strictly required, though adding them is harmless. Note that results are language-sensitive: DISPLAY_NAME and DESCRIPTION reflect the session language, so reporting clients should set the NLS environment appropriately to obtain consistent output.