Search Results allow_requestor_approval

Overview

HR_WORKFLOW_SS is a shared-service PL/SQL package in the APPS schema that centralizes the server-side logic underpinning Oracle HRMS workflow integrations. In Oracle EBS 12.1.1 and 12.2.2, its primary business function is to bridge Oracle Human Resources business objects — assignments, people, payroll actions, appraisals, and approvals — with the Oracle Workflow engine. Rather than duplicating workflow routing, notification, and approver-resolution logic across individual products, HRMS modules call HR_WORKFLOW_SS to determine approval levels, resolve next and final approvers, read and write activity attributes, and manage the lifecycle state of workflow items.

The package is classified as OTHER in the ETRM repository, reflecting the fact that it is an internal utility rather than a public, documented business API. Its metadata status is VALID, and it is referenced by five other packages, confirming its role as a shared dependency. Direct dependencies include HR_API_TRANSACTIONS and WF_RUNNABLE_PROCESSES_V, indicating that the package both drives the Oracle HRMS API transaction framework and interrogates workflow process definitions at runtime.

Key Procedures and Functions

The documented interface exposes 34 procedures and functions. The core retrieval functions include GET_ITEM_TYPE, GET_ITEM_KEY, and GET_PROCESS_NAME, which resolve the Workflow identity and runnable process associated with an HR transaction. GET_EFFECTIVE_DATE and GET_ASSIGNMENT_ID return the date and assignment context for a workflow-driven action, while GET_APPROVAL_LEVEL and GET_FINAL_APPROVER establish where an approval currently sits and who ultimately must authorize it. GET_NEXT_APPROVER determines the subsequent approver in the routing chain — the central mechanism behind dynamic HR approvals.

• BRANCH_ON_APPROVAL_FLAG — evaluates the approval indicator to direct workflow branch selection.
• ALLOW_REQUESTOR_APPROVAL — determines whether the originating requestor may act as approver.
• UPDATE_APPROVAL_STATUS — persists the current approval state back to the transaction.
• CHECK_MID_PAY_PERIOD_CHANGE — validates changes occurring mid-pay-period, protecting payroll integrity.
• SET_REJECTED_BY_PAYROLL and COPY_PAYROLL_COMMENT — mark payroll rejections and propagate payroll commentary.
• GETACTIVITYATTRTEXT, GETACTIVITYATTRNUMBER, GETACTIVITYATTRDATE — typed accessors for Workflow activity attribute values.
• GETPAGEDETAILS — returns page/context detail for notification rendering.
• APPS_INITIALIZE and DEFER_COMMIT — standard APPS session initialization and commit-deferral utilities.

Tables Accessed

Access is performed through APPS synonyms. The package reads and writes HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS, the tables that record HRMS API calls and their step-level progress, and joins to PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F for current assignment and person data. PER_APPRAISALS and PER_TIME_PERIODS supply appraisal and pay-period context, while FND_USER resolves application user identities for notifications. The Workflow side is read and updated through WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTE_VALUES, WF_ACTIVITIES, WF_ACTIVITY_ATTRIBUTES, WF_ACTIVITY_ATTR_VALUES, WF_NOTIFICATIONS, and WF_NOTIFICATION_ATTRIBUTES, and process definitions are validated against WF_RUNNABLE_PROCESSES_V.

Usage Notes

HR_WORKFLOW_SS is invoked indirectly rather than called by end users. Oracle HRMS forms such as dynamic approval pages, the HR approval shared service (HR_APPROVAL_SS), appraisal workflow (HR_APPRAISAL_WORKFLOW_SS), and person deployment workflows (HR_PERSON_DEPLOYMENT_SWI, HR_SFLUTIL_SS) drive it during approval routing and notification processing. Because it is a shared internal package, customizations should prefer the documented public HRMS APIs; where direct calls are unavoidable, developers must preserve the APPS_INITIALIZE call and respect the package's commit-deferral model to avoid inconsistent Workflow and HRMS transaction state.