Search Results p_location_id

Overview

HR_LOCATION_BK3 is a generated Oracle HRMS API hook pre-processor package body owned by the APPS schema. Its name follows the Oracle E-Business Suite hook naming convention, in which a "BK" (before) package exposes entry points that the HRMS Business Process API (BPAPI) framework invokes at specific points in the processing of a base API such as HR_LOCATION_API. The package is automatically produced by the Oracle HRMS API Hook Pre-processor, as indicated by the header comment Code generated by the Oracle HRMS API Hook Pre-processor, and is regenerated whenever the underlying hook definitions are compiled. In Oracle EBS 12.1.1 and 12.2.2, this layer allows Oracle and customer extensions to inject logic, validations, and downstream integration calls before the core location business logic executes, without modifying Oracle-owned base APIs. Functionally, HR_LOCATION_BK3 supports the deletion of HR location records, coordinating pre-delete user hooks for warehouse management before delegating to the underlying "BE" business entity package.

Key Procedures and Functions

The package body contains two documented procedures, both of which serve as hook entry points for the location delete operation:

• DELETE_LOCATION_A — The primary before-delete hook. It calls WSH_MAP_LOCATION_REGION_PKG.Location_User_Hook_API to give the Warehouse Management (WSH) module an opportunity to react to the deletion of a location, then invokes hr_location_be3.DELETE_LOCATION_A to continue the base API processing chain. It captures the current commit unit via hr_api.return_commit_unit and validates it against the 'DELETE_LOCATION' entity using the 'AP' prefix before exiting.
• DELETE_LOCATION_B — A companion validation hook. It invokes WSH_MAP_LOCATION_REGION_PKG.PREDEL_LOC_VALIDATION to perform pre-delete validation of the location within the Warehouse Management context. It likewise preserves the commit unit using hr_api.return_commit_unit and validates it with the 'BP' prefix.

Both procedures are gated by the hr_api.call_app_hooks flag, ensuring that hook logic executes only when the Business Process API framework is running in a context that permits application hooks. Parameter lists are intentionally not reproduced here as they are not part of the documented metadata.

Tables Accessed

The ETRM metadata documents no direct table references via APPS synonyms for this package. This is consistent with the role of a "BK" hook package: it does not itself manipulate HR_LOCATION or related base tables. Instead, it delegates all transactional work to the base business entity package hr_location_be3 and to the WSH hook package WSH_MAP_LOCATION_REGION_PKG, which in turn access their own underlying tables. Any table access therefore occurs indirectly through those called packages rather than within HR_LOCATION_BK3 itself.

Usage Notes

HR_LOCATION_BK3 is not intended to be called directly by application code. It is invoked by the Oracle HRMS Business Process API framework when the location delete business process executes, provided that application hooks are enabled. The framework calls DELETE_LOCATION_A and DELETE_LOCATION_B at the appropriate initiation points of the business process, allowing the WSH location user hook and pre-delete validation to run in the correct sequence.

Typical invocation scenarios include:

• Execution of the base location delete API from any caller, including the Location form, concurrent programs, or other PL/SQL code, when the Business Process API is active.
• Cross-module integration where Oracle Warehouse Management needs to synchronise location master data following HR location changes.

Because the package is auto-generated, any modification by hand is unsupported and will be overwritten on regeneration. The documented metadata notes that HR_LOCATION_BK3 is referenced by one other package, confirming it participates in a broader API hook chain. Administrators and developers should review the WSH hook logic and any custom hook packages registered against the location business process when troubleshooting deletion behaviour or extending location processing in Oracle EBS 12.1.1 or 12.2.2.