Search Results delete_default_posting

Overview

IRC_DEFAULT_POSTING_BK3 is a generated PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle iRecruitment product family, as indicated by the IRC prefix, and specifically supports the DEFAULT_POSTING business entity. The package is an Oracle HRMS API Hook Pre-processor artifact, automatically created by the HRMS API Hook Pre-processor, as evidenced by the header comment referencing "iridpapi.pkb" and the generation date of 2008/11/06. Its classification in the ETRM repository is OTHER.

The business function of this package is to provide the "Before" processing hook layer for delete operations against the default posting entity. The HRMS API Hook architecture separates business logic into distinct layers: the Before (BK) layer, the Entity (BE) layer, and the After (AA) layer. This package represents the Before layer, whose role is to execute pre-processing validations and hook calls prior to the core delete logic being executed by the entity-level package. The package is the counterpart to irc_default_posting_be3, which contains the actual entity-level delete implementation.

The package is referenced by exactly one other package, consistent with its role as a subordinate hook layer invoked by the API framework during the delete transaction lifecycle.Key Procedures and Functions

The package exposes two documented procedures, both accepting a single default posting identifier parameter that is defined at the package specification level:

• DELETE_DEFAULT_POSTING_A — The primary pre-processing procedure. It begins by recording its execution location via hr_utility.set_location for diagnostic tracing, then captures the current commit unit number using hr_api.return_commit_unit. It evaluates hr_api.call_app_hooks to determine whether application-level hooks should be invoked, and if so, delegates to irc_default_posting_be3.DELETE_DEFAULT_POSTING_A, passing the default posting identifier forward. Following hook execution, it terminates the validation message set through hr_multi_message.end_validation_set and validates the commit unit against the 'DELETE_DEFAULT_POSTING' operation with the 'AP' context via hr_api.validate_commit_unit. The procedure then logs its exit location and completes.
• DELETE_DEFAULT_POSTING_B — A stub procedure that contains only entry and exit location markers written through hr_utility.set_location. It performs no business logic, validations, or hook invocations. This empty implementation is typical of generated hook packages, where unused hook points are preserved as no-op procedures to satisfy the API hook interface contract while allowing the actual work to remain concentrated in the primary procedure.

No additional parameters are documented for either procedure beyond the default posting identifier. Their parameter lists should not be inferred or extended.

Tables Accessed

The ETRM metadata records no direct table references through APPS synonyms for this package body. This absence is consistent with its architectural role: as a Before-layer hook package, it does not perform direct DML. Any table interaction, including the physical deletion of default posting records, is encapsulated within the entity-layer package irc_default_posting_be3, which this package invokes. The commit unit management routines from hr_api and the validation routines from hr_multi_message operate against the HRMS transaction and validation infrastructure rather than application tables directly.

Usage Notes

This package is not intended for direct invocation by end users, forms, or custom concurrent programs. It is called internally by the HRMS API Hook framework during the execution of a delete operation on a default posting record. The framework orchestrates the sequence of Before, Entity, and After hook layers, and application code that intends to delete a default posting should call the corresponding public entity API, not this package.

Developers performing troubleshooting or extension work related to default posting deletion may encounter this package in call stacks or trace files. The hr_utility.set_location calls with location codes 10 and 20 provide traceability for entry and exit points. The condition hr_api.call_app_hooks determines whether the entity-layer hook is executed, meaning behavior can be affected by the hook mode configured in the runtime environment. The package carries an Oracle Proprietary, Confidential Information designation, and any modification is discouraged because the code is regenerated by the HRMS API Hook Pre-processor, which would overwrite manual customizations. As the package is dated 2005/07/26 in its source header, it has remained stable across the 12.1.1 and 12.2.2 releases.