Results for “wf_role_hierarchy”

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

Overview

APPS.WF_ROLE_HIERARCHY is a PL/SQL package body in the Oracle E-Business Suite Workflow (WF) schema that governs the role hierarchy used by the Oracle Workflow directory service. In EBS 12.1.1 and 12.2.2, the workflow engine resolves approvers, notifications, and access by traversing role relationships stored in the WF_ROLE_HIERARCHIES table. This package provides the programmatic interface for creating, expiring, querying, and propagating those role relationships, and for computing the effective dates and denormalized structures that make hierarchy traversal performant at runtime.

The package is classified as an "OTHER" API in ETRM rather than a formal public API, which reflects that it is primarily intended for internal consumption by Oracle Workflow and related EBS components. Nevertheless, it is referenced by four other database objects and itself depends on core Workflow infrastructure including WF_CORE, WF_DIRECTORY, WF_EVENT, WF_LOCAL_ROLES, WF_LOCAL_SYNCH, and WFA_SEC. The presence of the WF_ROLE_HIERARCHY package body in a valid state confirms active use in the environment.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions:

• HIERARCHYENABLED — Determines whether role hierarchy functionality is enabled for the current context, gating other operations.
• CALCULATE_EFFECTIVE_DATES — Computes the start and end dates that govern the validity of a role relationship, accounting for cascade and expiry semantics.
• ADDRELATIONSHIP — Establishes a new parent-child relationship between two roles in the hierarchy.
• EXPIRERELATIONSHIP — Ends an existing role relationship, typically by setting its end date so the link becomes inactive.
• CASCADE_RF — Applies cascade logic to role relationships, likely propagating changes through dependent hierarchy entries.
• PROPAGATE_RF — Propagates role relationship changes, supporting the Rebuild and Refresh semantics used by Workflow admin utilities.
• PROPAGATE — General propagation routine for hierarchy updates.
• PROPAGATE_CP — Concurrency-program-oriented propagation entry point invoked by submitted Workflow jobs.
• AGGREGATE_USER_ROLES_RF — Aggregates user-to-role assignments derived from the hierarchy.
• GETRELATIONSHIPS — Returns role relationships for a given role.
• GETALLRELATIONSHIPS — Returns the complete set of role relationships, used for bulk operations.
• DENORMALIZE_USER_ROLE_RF — Populates denormalized user-role structures to speed runtime resolution.
• VALIDATESESSION — Validates a Workflow session context before hierarchy work proceeds.
• CREATESESSION — Creates the session context used during hierarchy maintenance.
• REMOVERELATIONSHIP — Physically removes a role relationship record.

Tables Accessed

The package reads and writes through APPS synonyms. WF_ROLE_HIERARCHIES and its sequence WF_ROLE_HIERARCHIES_S are the primary data structures storing parent-child role links and their identifiers. WF_USER_ROLE_ASSIGNMENTS and the view WF_USER_ROLE_ASSIGNMENTS_V supply user-to-role assignments. WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES hold denormalized role and assignment data used by Workflow Directory Services. WF_DIRECTORY_PARTITIONS supports partitioned directory lookups, while WF_RESOURCES and WF_PARAMETER_LIST_T supply configuration and parameter passing. WF_EVENT_T and WF_DIRECTORY support event raising and directory resolution, and DUAL and PLITBLM provide standard PL/SQL utilities.

Usage Notes

WF_ROLE_HIERARCHY is invoked principally by Oracle Workflow administrative functions, such as the "Workflow Directory Services" configuration screens and the concurrent programs that rebuild and refresh role hierarchies. Because it is not exposed as a formal public API, custom code should generally avoid calling it directly; integrations requiring role relationship maintenance are expected to use the documented Workflow Directory Services APIs. Where direct calls are necessary, they should run within a valid session created via CREATESESSION, and propagation routines such as PROPAGATE_CP should be executed through the appropriate concurrent program rather than ad hoc. The package's dependence on WFA_SEC indicates that security checks are applied during relationship changes.