Results for “wf_directory”

50+ results




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

Overview

WF_DIRECTORY (APPS.WF_DIRECTORY) is the Workflow Directory Services package within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes a public PL/SQL API through which application programs and Workflow functions retrieve information about existing users and roles and manage ad hoc (local) users and roles in the directory service. Its header identifies the owning product as OWF (Oracle Workflow) and classifies the package lifecycle as active with a compatibility rating of S. The package is central to Oracle Workflow's notification infrastructure: whenever a workflow activity must determine who a performer is, resolve a role to its member users, or verify whether a user or role remains active, WF_DIRECTORY supplies the answer. It is one of the most heavily consumed APIs in the EBS technology stack, referenced by 309 other packages, which reflects its role as the canonical access layer for directory data. The API classification in ETRM is recorded as OTHER rather than as a business-entity-specific API, but the underlying business entity category documented in the package header is WF_USER.

Key Procedures and Functions

The package publishes 46 documented procedures and functions, organized around user lookup, role lookup, role membership, role attributes, and ad hoc maintenance.

  • User resolution: CURRENTUSER returns the currently connected directory user; GETUSERNAME resolves a user identifier to a user name; USERACTIVE tests whether a user is active; ISPERFORMER evaluates whether a user or role satisfies a performer specification.
  • Role resolution: GETROLENAME, GETROLEDISPLAYNAME, and GETROLEDISPLAYNAME2 return a role identifier's name and display name; ROLEACTIVE tests role status; GETROLEORIGSYSINFO and GETROLEPARTITIONINFO return originating-system and partitioning attributes for a role.
  • Role attributes: GETROLEINFO and GETROLEINFO2 return role detail records; GETROLEINFOMAIL and GETROLEINFOMAIL2 return mail-related attributes for a role; GETROLENTFPREF returns the notification preference for a role.
  • Membership and relationships: GETROLEUSERS returns the users assigned to a role; GETUSERROLES returns the roles to which a user belongs; GETUSERRELATION resolves hierarchical relationships between users and roles.
  • Ad hoc directory maintenance: SETADHOCUSERSTATUS and SETADHOCROLESTATUS change the status of locally defined ad hoc users and roles.
  • PL/SQL collection types: the package declares UserTable, RoleTable, OrigSysTable, and wf_local_roles_rec_type, the latter mirroring the attribute set of WF_LOCAL_ROLES for bulk retrieval.

Tables Accessed

Directory data is read and written through APPS synonyms. WF_LOCAL_ROLES and WF_LOCAL_ROLES_TL hold the base and translated role definitions central to all lookup calls. WF_LOCAL_USER_ROLES and WF_USER_ROLE_ASSIGNMENTS store user-to-role and role-to-role grants used by GETROLEUSERS, GETUSERROLES, and GETUSERRELATION. WF_ROLE_HIERARCHIES supports role hierarchy traversal. WF_ADHOC_ROLE_S sequences ad hoc role identifiers created by the package. WF_DIRECTORY_PARTITIONS records directory partitioning metadata. WF_EVENT_T and WF_PARAMETER_LIST_T carry Workflow event and parameter structures used by notification-related calls. PLITBLM provides the PL/SQL table-to-index-by binary integer conversion utility, and USER_VIEWS supplies view metadata.

Usage Notes

WF_DIRECTORY is invoked at runtime by Workflow Notification Mailer processing, by workflow function activities during performer resolution, and by Oracle Application forms that display or validate users and roles. Because the API contract spans 309 dependent packages, direct calls from custom code should follow the documented signatures and be exercised within a controlled test environment. Administrators clearing or reconciling stale directory entries may call the ad hoc status procedures, but such changes should be staged carefully, since ad hoc records are local to the directory rather than sourced from an external originating system. The package's 2008 header revision (120.12.12010000.3) remains the shipping version across the 12.1.1 and 12.2.2 code lines.