Search Results delete_pending_data

Overview

The APPS.IRC_PENDING_DATA_BK3 package body is a generated Oracle HRMS API Hook pre-processor artifact associated with the Oracle iRecruitment (IRC) module of Oracle E-Business Suite. Its header comments indicate that the source file, iripdapi.pkb (version 120.15, dated 2008/01/21), was processed by the Oracle HRMS API Hook Pre-processor and generated as a "BK3" wrapper package on 2008/11/06. Within the ETRM classification this object is registered as an API of type OTHER under the APPS schema.

The business function served by this package is to act as an intermediate hook layer for the deletion of iRecruitment pending data records. In the HRMS API architecture, "BK" packages are reserved for business knowledge or hook processing and are automatically generated to provide consistent pre-processing and post-processing behavior around the underlying business entity (BE) package, in this case IRC_PENDING_DATA_BE3. This wrapper ensures that legislation-specific logic, application hooks, multi-message validation, and commit unit validation are applied uniformly whenever pending data records are deleted.

Key Procedures and Functions

Two documented procedures are exposed by the package body:

• DELETE_PENDING_DATA_A — The primary pre-process hook procedure. It records its entry point via hr_utility.set_location, captures the current commit unit using hr_api.return_commit_unit, and, when application hooks are enabled, delegates execution to irc_pending_data_be3.DELETE_PENDING_DATA_A. It then closes the validation set through hr_multi_message.end_validation_set and validates the commit unit with the reference 'DELETE_PENDING_DATA' and application identifier 'AP'. This procedure carries the substantive delete logic chain for pending data.
• DELETE_PENDING_DATA_B — The corresponding secondary hook procedure. It marks entry and exit points using hr_utility.set_location but contains no additional executable logic in the documented source. This is standard for generated hook stubs, where the "B" variant is created to satisfy the API framework's expected interface and may be populated by extension code or remain empty.

No parameter lists are invented here; the documented signature for DELETE_PENDING_DATA_A accepts P_PENDING_DATA_ID as a NUMBER, and the "B" procedure mirrors that input.

Tables Accessed

The ETRM metadata records no tables referenced directly via APPS synonyms within this package body. Its data access occurs indirectly through the delegated call to irc_pending_data_be3.DELETE_PENDING_DATA_A, which performs the physical delete against the iRecruitment pending data entity. The absence of direct table references confirms that IRC_PENDING_DATA_BK3 functions purely as a hook wrapper rather than as a data-manipulation layer.

Usage Notes

This package is not intended for direct invocation by end users or custom developers. It is invoked automatically by the Oracle HRMS/iRecruitment API framework when a pending data record is deleted through supported APIs. The commit unit validation at line 19 ensures transactional consistency across a single logical business transaction, while the application hook check lets customers attach legislation-specific logic without modifying seeded code. Because it is referenced by one other package (per the ETRM metadata) and generated by the pre-processor, any customization should target the hook points rather than this body, and regeneration of the API will overwrite manual changes. Developers searching for delete_pending_data should treat this package as part of the iRecruitment pending data deletion chain introduced in EBS 12.1.1 and preserved through 12.2.2.