Search Results update_notifiers

Overview

APPS.HR_DYNAMIC_APPROVAL_WEB is a server-side PL/SQL package within the Oracle E-Business Suite Human Resources module that implements the dynamic approval routing framework used by the Oracle Approvals Management and Oracle Workflow-based notification processes. The package supports the configurable approval hierarchies that allow customers to dynamically determine one or more approvers and notifiers for HR-related transactions, such as absence requests, assignment changes, and other self-service business events. Its design cleanly separates the retrieval of workflow item metadata from the definition and validation of approval participants.

The package encapsulates the business logic required to derive approval levels, resolve default approvers, classify approvers and notifiers, validate approval configuration, and fire notifications. Several overloaded and context-aware subprograms are exposed to allow the calling Forms and workflow code to reuse the same approval engine across different item types and transaction categories. This package is bound to the Others API classification in ETRM, indicating it is not a public, externally-versioned API but a supporting library invoked by other EBS components.

Key Procedures and Functions

The package exposes twenty-five documented subprograms. The most relevant, particularly with respect to the searched term initialize_item_attributes, are listed below.

• GET_WF_ATTRIBUTES — Retrieves the dynamic approval mode and approval level attributes for a given workflow item type, item key, and activity.
• GET_DEFAULT_APPROVERS and GET_ALL_APPROVERS — Return the default and full set of approvers for an item, with flags indicating which are defaults.
• BUILD_DDL — Builds drop-down list data (label, code, index) for approval-related UI selections.
• ADD_APPROVER, DELETE_APPROVER, ADD_NOTIFIER, GET_ALL_NOTIFIERS, UPDATE_NOTIFIERS — Manage the set of approvers and notifiers attached to a transaction.
• CLEAN_INVALID_DATA — Removes stale or inconsistent approval records.
• GET_NEXT_APPROVER, CHECK_FINAL_APPROVER, SET_FIRST_ONAPPROVAL_PERSON, SET_FIRST_ONSUBMIT_PERSON — Drive the sequential routing of an approval chain, identifying the next approver and the persons to be notified at submit or approval time.
• CHECK_ONSUBMIT_NOTIFIER, CHECK_ONAPPROVAL_NOTIFIER, GET_ONSUBMIT_NOTIFIER, GET_ONAPPROVAL_NOTIFIER — Validate and retrieve notifier configuration for the two notification events.
• INITIALIZE_ITEM_ATTRIBUTES — This is the procedure associated with the user's search. It initializes the workflow item attributes used by the dynamic approval engine, ensuring that the item attribute values (such as approval mode, level, and participant details) are seeded and in a consistent state before approval routing begins. It is typically invoked early in the routing lifecycle, prior to GET_WF_ATTRIBUTES and the approver resolution calls.
• NOTIFY — Dispatches the actual notifications to the identified approvers and notifiers.

Tables Accessed

The package reads and writes data through APPS synonyms. The principal base tables include:

• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — Source of person names, person identifiers, and assignment context for approvers and notifiers.
• PER_JOBS — Provides job titles displayed alongside approver names.
• WF_ITEMS and WF_ITEM_ATTRIBUTE_VALUES — The core Workflow item and item attribute stores used to persist approval configuration and status.
• WF_ACTIVITY_ATTR_VALUES and WF_PROCESS_ACTIVITIES — Define activity-level attributes and the process activities that consume approval attributes.
• HR_API_TRANSACTIONS — Tracks the HR API transaction associated with the approval flow.
• HTF and PLITBLM — Utility objects used for HTML generation and PL/SQL table manipulation.

Usage Notes

HR_DYNAMIC_APPROVAL_WEB is not intended to be called directly by end users. It is invoked from Oracle Forms-based self-service pages, from Oracle Workflow function activities, and from other PL/SQL packages within the HR approval framework. One other documented package references it, confirming it functions as a shared library. Customizations should call the public entry points (such as INITIALIZE_ITEM_ATTRIBUTES and GET_WF_ATTRIBUTES) rather than the underlying tables, because direct DML on WF_ITEM_ATTRIBUTE_VALUES or the PER_* tables can bypass the routing logic and leave the approval chain inconsistent. When troubleshooting approval routing, INITIALIZE_ITEM_ATTRIBUTES is the appropriate starting point to verify that item attributes are populated before diagnosing downstream approver or notifier resolution.