Results for “hr_approval_custom”

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

Overview

APPS.HR_APPROVAL_CUSTOM is a PL/SQL package that supports Oracle E-Business Suite's Oracle Approvals Management (AME) and HR notification workflow within the Human Resources module. Its central role is to provide the AME / Workflow engine with routing decisions — principally the identity of the person who should receive an approval or notification — and to supply formatted URL links that are embedded in those notifications. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking schema rather than the package owner, a convention used throughout the APPS toolset to preserve session context.

The package is classified in the ETRM repository as an "OTHER" API, indicating that it is not a documented public business API but rather a utility/workflow-support package. Its header dates from Release 12.0.1 ($Header: hrapcuwf.pkh 120.1 2005/06/15), and it remains present and documented in 12.2.2. It is referenced by ten other packages, which confirms its role as a shared routing utility rather than a standalone entry point.

Key Procedures and Functions

The package exposes 29 documented procedures and functions. The documented members fall into two functional groups:

• Routing resolution functions (GET_ROUTING_DETAILS1 through GET_ROUTING_DETAILS5) — Each returns a PERSON_ID value derived from an input person identifier, and each is documented as returning "the Id of a person, used for routing of notifications within the approval process." The numbered variants allow the approval process to resolve different routing targets (for example, supervisor, final approver, or HR representative) through distinct function names.
• GET_NEXT_APPROVER — Resolves the next approver in the approval chain.
• CHECK_FINAL_APPROVER — Evaluates whether a given approver or approval step represents the final level of approval, allowing the workflow to terminate notification chains.
• GET_NEXT_PAYROLL_NOTIFIER — Determines the next recipient in a payroll-related notification sequence.
• URL generation functions (GET_URL1 through GET_URL12) — Produce URL strings that are inserted into workflow notification bodies so the recipient can navigate directly to the relevant EBS page. The multiplicity of functions reflects the range of HR and approval contexts that require distinct link targets.

Package-level globals g_itemtype and g_itemkey are declared, holding the Workflow item type and item key for the transaction currently being routed.

Tables Accessed

Per the ETRM metadata, the package reads three core HR tables through APPS synonyms:

• PER_ALL_PEOPLE_F — The primary person record, providing PERSON_ID resolution for the GET_ROUTING_DETAILS and GET_NEXT_APPROVER calls.
• PER_ALL_ASSIGNMENTS_F — Assignment data used to establish supervisory and organizational relationships that drive routing decisions.
• PER_ASSIGNMENT_STATUS_TYPES — Assignment status values, allowing the package to restrict routing to employees in active or otherwise eligible statuses.

These are datetracked (date-effective) tables, so lookups must be performed against the effective date of the transaction being routed.

Usage Notes

HR_APPROVAL_CUSTOM is invoked indirectly by the Oracle HRMS approval workflow rather than directly by end users. Typical invocation paths include:

• AME and HRMS workflow processes that need to determine the recipient of an approval or informational notification.
• Workflow notification definitions that call the GET_URL functions to build deep links into the EBS application.
• Other packages — the ten documented referencing packages — which call the routing functions as shared services.
• Custom code and RICE extensions that must replicate Oracle's routing behavior, since the package is visible in the APPS schema.

Because the package is classified as OTHER and not as a certified public API, Oracle does not guarantee its signature across releases. Any customer copy (signalled by the "_CUSTOM" suffix pattern common to HRMS workflow customization points) should be validated after upgrades to 12.1.1 or 12.2.2, and direct dependencies on these functions should be documented as customizations rather than supported integrations.