Search Results update_pending_data

Overview

APPS.IRC_PENDING_DATA_SWI is a self-service wrapper package within the Oracle E-Business Suite iRecruitment (IRC) module. Its role is to expose the underlying iRecruitment pending-data API to self-service and web-facing callers, most notably the candidate-facing recruitment pages delivered through Oracle Applications Framework (OAF) and related self-service flows. The package encapsulates the business logic of irc_pending_data_api and presents a stable, controlled interface for creating, maintaining, and removing staged recruitment records that have not yet been fully processed into the core HR and recruitment schema.

The _SWI suffix denotes a "self-service web interface" wrapper. Rather than permitting self-service code to invoke the base API directly, Oracle routes those calls through this wrapper so that validation, derivation of mandatory IN parameters, and standardized return-status handling occur in a single supported location. The package header confirms this design intent, stating that each procedure is the self-service wrapper to the corresponding irc_pending_data_api procedure and that all IN parameters are expected to have been appropriately derived before invocation. Access status is documented as "Internal Development use only," meaning the package is not intended as a public extension point.

Key Procedures and Functions

The package exposes three documented procedures, mirroring the create, update, and delete operations of the underlying pending-data API:

• CREATE_PENDING_DATA — Inserts a new pending-data record. In the iRecruitment context this supports the staging of candidate-supplied information such as an external applicant's e-mail address, name, vacancy reference, password, resume file metadata, source type, job post source, posting content identifier, and assorted person-information flexfield attributes. A validation mode flag allows the caller to exercise the logic without committing.
• UPDATE_PENDING_DATA — Modifies an existing pending-data row. This is the procedure most directly associated with the user search term update_pending_data. It is used when a candidate or self-service process revises staged information prior to that data being promoted into the permanent recruitment and person records.
• DELETE_PENDING_DATA — Removes a pending-data record, typically when a staged submission is abandoned, superseded, or rejected.

Each procedure returns a standard status indicator through an OUT parameter, signalling success or failure in the conventional EBS API manner. Individual parameter lists are not reproduced here; callers should consult the package specification and the corresponding irc_pending_data_api definitions.

Tables Accessed

The ETRM metadata for this object does not enumerate the tables touched through APPS synonyms. Functionally, the package operates against the iRecruitment pending-data table (commonly IRC_PENDING_DATA) and, through the base API, may read or validate against associated recruitment and person reference tables. Because table access is documented as indirect, implementers should treat the underlying API's table dependencies as authoritative and avoid assuming a fixed, minimal footprint.

Usage Notes

IRC_PENDING_DATA_SWI is invoked primarily from self-service recruitment pages and related OAF-based flows, where candidate-supplied data is staged before processing. It may also be called from custom code that requires the same staged-data behaviour, provided the calling context satisfies the prerequisite that all IN parameters are already derived. The package is referenced by no other documented packages, which reinforces its position as a leaf-level wrapper rather than a shared library. Because access is restricted to internal development use, customizations should prefer the documented API surface and should not rely on undocumented behaviour. When troubleshooting an update_pending_data operation, verify the status return value and confirm that the pending row exists and is in an updatable state before the call.