Search Results wf_adhoc_role_s

Overview

APPS.WF_DIRECTORY is the central runtime directory-resolution engine within the Oracle E-Business Suite Workflow (WF) schema. It provides the authoritative lookup services that translate between users, roles, and the hierarchical relationships that connect them, forming the backbone of the Oracle Workflow notification and routing infrastructure. The package answers questions such as which users belong to a role, which roles a user holds, what display name should be presented for a role, whether a particular user or role is currently active, and which origination system owns a given role. Because notification addressing, responsibility-based routing, and ad hoc role assignment all depend on accurate directory information, WF_DIRECTORY is invoked throughout the Workflow runtime, the Workflow Notification Mailer, and any application that must determine the recipients of a business event or approval process. The documented metadata classifies it as an OTHER API, and it is referenced by 309 other database objects, reflecting its role as a foundational service rather than an isolated utility. The package body is VALID in the APPS schema and is documented for Oracle EBS 12.2.2, with applicability to 12.1.1 environments on the same directory model.

Key Procedures and Functions

The package exposes forty-six documented procedures and functions. The principal resolution routines include:

• GETUSERROLES — returns the roles assigned to a given user, the inverse of role-to-user resolution.
• GETROLEUSERS — returns the users that belong to a specified role, supporting notification fan-out.
• GETUSERRELATION — establishes the relationship between a user and a role, used to confirm membership or reporting structures.
• GETROLEINFO, GETROLEINFO2, GETROLEINFOMAIL, GETROLEINFOMAIL2 — retrieve role attributes, with the Mail variants producing values formatted for the Notification Mailer.
• GETROLEORIGSYSINFO — returns the originating system information for a role, relevant in multi-directory and integrated environments.
• GETROLEPARTITIONINFO — returns partition information associated with a role, supporting partitioned directory lookups.
• GETROLENTFPREF — retrieves the notification preference associated with a role.
• GETUSERNAME, GETROLENAME, GETROLEDISPLAYNAME, GETROLEDISPLAYNAME2 — resolve internal identifiers into human-readable user and role names and display names.
• ISPERFORMER, CURRENTUSER, USERACTIVE, ROLEACTIVE — validation functions that determine whether a user or role is performing, active, or currently resolvable.
• SETADHOCUSERSTATUS, SETADHOCROLESTATUS — update the status of ad hoc users and roles created during runtime workflow activity.

Tables Accessed

WF_DIRECTORY reads and writes the core Workflow directory tables, primarily through APPS synonyms. WF_LOCAL_ROLES and its translation table WF_LOCAL_ROLES_TL supply role definitions and localized display names; WF_LOCAL_USER_ROLES and WF_USER_ROLE_ASSIGNMENTS (with the WF_USER_ROLE_ASSIGNMENTS_V view) hold the assignment relationships between users and roles. WF_ROLE_HIERARCHIES and WF_ROLE_HIERARCHY support hierarchical role traversal. WF_ADHOC_ROLE_S stores ad hoc roles created at runtime, and WF_DIRECTORY_PARTITIONS controls partitioned directory access. The package also references WF_USERS, WF_ROLES, WF_USER_ROLES, and WF_LANGUAGES for user and language resolution, WF_EVENT and WF_EVENT_T for event propagation, and WF_PARAMETER_LIST_T and WF_PARAMETER_T for parameter handling. PLITBLM and USER_VIEWS provide PL/SQL table and view metadata support, while FND_LOG and WF_LOG_PKG record diagnostic messages. Dependencies on WF_CORE, WF_MAINTENANCE, WFA_SEC, and STANDARD confirm its integration with the wider Workflow and Application Object Library runtime.

Usage Notes

WF_DIRECTORY is normally invoked indirectly. The Workflow Engine calls it during notification processing to expand roles into individual recipients, evaluate performer conditions, and validate that an address is active before dispatch. The Workflow Notification Mailer uses the GETROLEINFOMAIL family to render role names in outbound messages. Oracle Forms-based Workflow administration screens and the Notification System rely on the GETROLE* and GETUSER* routines for list-of-values and display purposes. Custom PL/SQL that builds approval hierarchies, addresses notifications, or replicates directory data should call these documented APIs rather than querying WF_LOCAL_ROLES directly, since the package encapsulates partition awareness and ad hoc role handling. Because WF_DIRECTORY is referenced by 309 objects and references critical runtime tables, modifications to its signatures should be avoided; extensions are best implemented in custom wrappers. The SETADHOC* routines should be used only by processes managing ad hoc role lifecycles.