Search Results wf_local_roles

Overview

The WF_LOCAL_ROLES table is a core data object within the Oracle E-Business Suite (EBS) Application Object Library, owned by the APPLSYS schema. It serves as the central repository for all local roles defined within the Oracle Workflow security model. A local role represents a group of users or other roles, functioning as a principal for assigning workflow notifications, routing tasks, and enforcing access control within business processes. Its existence is fundamental to the operation of Oracle Workflow, enabling the abstraction of responsibility from individual users to logical groups, thereby providing flexibility and maintainability in process design and security administration.

Key Information Stored

The table's primary purpose is to store the definition and key attributes of each local role. As indicated by the primary key constraint WF_LOCAL_ROLES_PK on the column NAME, the role's unique identifier is its name. While the provided ETRM excerpt does not list all columns, based on standard Oracle Workflow implementation, this table typically contains critical columns such as:

• NAME: The unique internal name of the role (e.g., 'PO_BUYER_ROLE').
• DISPLAY_NAME: The user-friendly name presented in the Workflow notification web pages and administrative interfaces.
• DESCRIPTION: A textual description of the role's purpose.
• STATUS: Indicates whether the role is 'ACTIVE' or 'INACTIVE'.
• EXPIRATION_DATE: An optional date after which the role is no longer valid.
• EMAIL_ADDRESS: An optional email address associated with the role for notifications.
• NOTIFICATION_PREFERENCE: Defines how notifications are sent (e.g., MAILTEXT, MAILHTML, SUMMARY).
• LANGUAGE: The language for notifications sent to this role.
• TERRITORY: The territory setting for the role.

Common Use Cases and Queries

This table is primarily accessed for administrative reporting, auditing, and troubleshooting within the Workflow security framework. Common scenarios include identifying all active roles, finding roles assigned to specific users, or diagnosing notification routing issues. A fundamental query retrieves a list of all defined roles:

SELECT name, display_name, status, expiration_date FROM apps.wf_local_roles WHERE status = 'ACTIVE' ORDER BY name;

To investigate role membership, this table is joined with related objects like WF_USER_ROLES. For instance, to find all users directly assigned to a specific role:

SELECT wur.user_name FROM apps.wf_user_roles wur, apps.wf_local_roles wlr WHERE wlr.name = wur.role_name AND wlr.name = '&ROLE_NAME';

Administrators may also query this table to validate role configurations before deploying new workflow processes or to generate a master role inventory report.

Related Objects

The WF_LOCAL_ROLES table is integral to the Workflow security schema and has key relationships with several other APPLSYS objects. The WF_USER_ROLES table maps users and other roles as members of a local role. The WF_ROLE_HIERARCHIES table defines hierarchical relationships between roles. Key APIs that interact with this table include the PL/SQL package WF_DIRECTORY, which provides procedures for creating, updating, and querying roles (e.g., WF_DIRECTORY.CreateAdHocRole, WF_DIRECTORY.GetRoleInfo). Furthermore, role information from this table is often surfaced in workflow administration forms and the Notification Details web page (WFNOTH).