Search Results p_requisition_id

Overview

APPS.PER_REQUISITIONS_BK3 is a PL/SQL package body that forms part of the Oracle Human Resources (HRMS) API Hook architecture within Oracle E-Business Suite. Its role is to implement the "B" (Before) hook layer for the Requisition business object, one of three generated hook tiers—BK (before), BE (business entity), and the corresponding validation packages—that the HRMS API Hook Pre-processor produces for every registered business object. The header comment confirms the package was auto-generated by the "Oracle HRMS API Hook Pre-processor," meaning it is not intended for direct modification by developers.

The package exposes the standard HRMS hook entry points through which customer extensions and product logic can intercept the deletion of a requisition record before the core business logic executes. The p_requisition_id parameter, surfaced in the user's search, identifies the specific requisition (PER_REQUISITIONS row) targeted for deletion, while p_object_version_number provides optimistic locking control.

Key Procedures and Functions

The package contains two documented procedures, both concerned with requisition deletion:

• DELETE_REQUISITION_A — The primary active hook procedure. It receives P_REQUISITION_ID and P_OBJECT_VERSION_NUMBER as input parameters. It captures the current commit unit via hr_api.return_commit_unit, conditionally invokes the customer/entity hook per_requisitions_be3.DELETE_REQUISITION_A when hr_api.call_app_hooks is true, ends the validation set through hr_multi_message.end_validation_set, and finally validates the commit unit with the label 'DELETE_REQUISITION' and application prefix 'AP'. This procedure is the customization point where users register logic to run before deletion.
• DELETE_REQUISITION_B — A transitional stub procedure that declares the same P_REQUISITION_ID and P_OBJECT_VERSION_NUMBER parameters but contains only location tracing calls, performing no substantive processing. Such empty procedures are typical artifacts of the generator's prefix naming (for example, "_B" for a backup or alternate numbering slot).

Tables Accessed

The metadata documents no direct table references from within this package body. This is expected: BK-tier hook packages are thin wrappers that delegate all persistence work to the corresponding business-entity layer (PER_REQUISITIONS_BE3) and to the HRMS API infrastructure packages such as HR_API, HR_UTILITY, and HR_MULTI_MESSAGE. The actual DELETE against the PER_REQUISITIONS table is executed downstream, after the hooks in this package complete. Direct DML from customizations placed in these hooks is strongly discouraged.

Usage Notes

PER_REQUISITIONS_BK3 is not invoked by end users directly. It is called by the HRMS API framework whenever a requisition deletion is requested through supported channels—most commonly the People/Requisition maintenance forms or a PL/SQL call to the corresponding HRMS API. Developers implementing business rules around requisition deletion subscribe to these hooks by registering a custom package through the HRMS API Hook mechanism; the framework then substitutes the customer hook for the empty BE3 call. Because the package is regenerated during patching and upgrades, all customizations must reside in separate customer-owned packages, never inside PER_REQUISITIONS_BK3 itself. The ETRM metadata indicates this package is referenced by one other package, reflecting its position in the generated call chain.