Search Results set_url1

Overview

HR_APPROVAL_WF is a PL/SQL package owned by the APPS schema that provides the workflow infrastructure underlying Oracle E-Business Suite Human Resources approval processes. It belongs to the Oracle HRMS family of workflow-enabled components and is responsible for creating and populating the item attributes that the Oracle Workflow engine (Workflow Builder / Workflow Engine) references when routing, notifying, and approving HR-related transactions. The package is declared AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, a design choice that allows the workflow callbacks to run under the security context of the session that initiated the approval.

The central purpose of HR_APPROVAL_WF is to translate HRMS business data into workflow item attributes. When an approval process begins, activities inside the workflow require information such as the approver's person identifier, username, display name, and a deep-link URL that opens the relevant transaction in the originating application. HR_APPROVAL_WF exposes procedures that compute and store these values against a given item type, item key, and activity, so that subsequent notification and function activities in the process can consume them.

Key Procedures and Functions

The documented API surface is dominated by three families of routines.

• CREATE_ITEM_ATTRIB_IF_NOTEXIST — Verifies whether a specific item attribute already exists for an item type, and creates it when absent. This safeguards the approval process against runtime failures caused by missing attribute definitions.
• INITIALIZE_ITEM_ATTRIBUTES — Creates all activity item attributes required by the approval process and initializes a subset of them. It is typically the first procedure invoked for a new item instance.
• SET_ROUTING_DETAILS1 through SET_ROUTING_DETAILS5 — Populate routing attributes such as APPROVAL_ROUTING_PERSON_ID, APPROVAL_ROUTING_USERNAME, and APPROVAL_ROUTING_DISPLAY_NAME for successive routing levels. These attributes determine the performer of notification activities. The numbering supports multi-level approval hierarchies. The base procedure delegates person resolution to HR_APPROVAL_CUSTOM.
• SET_URL1 through SET_URL13 — Construct and assign the deep-link URLs associated with each approval routing level. The set_url1 routine is the first in this series and is the specific procedure most likely surfaced when users search for it. These procedures enable notification recipients to navigate directly to the pending HR transaction from the Workflow notification.

Tables Accessed

The package interacts with three primary data sources.

• OTA_EVENTS — the Oracle Training Administration events table, referenced when the approval transaction concerns event-related HR data.
• PER_ALL_PEOPLE_F — the effective-dated people table, used to resolve person identifiers, usernames, and display names for routing and approver determination.
• WF_ITEM_ATTRIBUTE_VALUES — the Oracle Workflow attribute store, where the package reads and writes the item attribute values that the workflow engine later evaluates.

Usage Notes

HR_APPROVAL_WF is not intended for direct invocation by end users. It is called from Oracle Workflow function activities and from the notification callbacks defined in HRMS approval process definitions generated through Workflow Builder. Because the routing and URL procedures are sequenced (ROUTING_DETAILS1–5 and URL1–13), customizations that extend an approval hierarchy must supply matching attributes and ensure each level's URL and routing details are initialized. The package is referenced by fourteen other packages, confirming its role as a shared dependency across HRMS workflows. Custom code that calls these procedures should operate within an active workflow item context (item type and item key) and observe the AUTHID CURRENT_USER security semantics. Implementations upgrading between 12.1.1 and 12.2.2 should validate that customized process definitions reference attribute names consistently with this API.