Search Results hr_api_hook_calls

Overview

The HR_API_HOOK_CALLS table is a configuration table within the Oracle E-Business Suite Human Resources (PER) module. Its primary role is to define and manage custom logic extensions, or "hooks," for the standard HRMS APIs. When a business process, such as hiring an employee or updating a salary, is executed via the HR API, the system checks this table to determine if any additional, customer-specific package procedures or formulas should be called at predefined hook points. This mechanism enables organizations to extend and customize core HR functionality without modifying Oracle's delivered code, ensuring upgrade safety and maintaining supportability in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the mapping between an API hook point and the custom code to be invoked. Key columns include API_HOOK_CALL_ID (the primary key surrogate identifier), APPLICATION_ID (identifying the owning application), and API_HOOK_ID (a foreign key to the HR_API_HOOKS table, defining the specific hook point). The LEGISLATION_CODE allows for country-specific customizations. Most critically, the CALL_PACKAGE and CALL_PROCEDURE columns specify the exact user-defined database package and procedure that contains the custom logic to be executed. This structure provides a flexible registry for attaching bespoke business rules to standard API events.

Common Use Cases and Queries

A primary use case is auditing or modifying the custom logic attached to APIs for troubleshooting or enhancement purposes. For example, to identify all custom package calls configured for a specific API hook, such as those related to person creation, an administrator might run a query joining to HR_API_HOOKS. The search term "call_package" directly relates to investigating which custom packages are invoked. A typical query pattern would be:

• SELECT hc.call_package, hc.call_procedure, h.hook_name, hc.legislation_code FROM hr_api_hook_calls hc, hr_api_hooks h WHERE hc.api_hook_id = h.api_hook_id ORDER BY h.hook_name;

This is essential for impact analysis before patching or upgrading, as it reveals dependencies on custom code.

Related Objects

The table has a defined foreign key relationship, making it a child of the HR_API_HOOKS table. This relationship is enforced on the API_HOOK_ID column. The HR_API_HOOKS table defines the available hook points within the HRMS APIs (e.g., before or after a specific API process). Therefore, to obtain a meaningful report from HR_API_HOOK_CALLS, a join to HR_API_HOOKS on API_HOOK_ID is almost always required to translate the identifier into a recognizable hook name and context. This relationship is fundamental to the hook configuration framework.