Search Results create_pending_data

Overview

IRC_PENDING_DATA_SWI is a server-side PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle iRecruitment application and functions as a supplemental Web API (SWI) that manages the staging table used to hold candidate information before it is validated and transferred into the core recruitment and HR tables. The package name, IRC_PENDING_DATA_SWI, follows the Oracle naming convention for iRecruitment (IRC) pending data, with the "SWI" suffix signifying that the package is designed for internal, controlled invocation rather than general public use.

The header comment in the package body ($Header: iripdswi.pkb 120.0 2005/07/26 ...$) confirms the package dates from the early iRecruitment releases and has been carried forward into EBS 12.1.1 and 12.2.2 without structural change. Its primary business purpose is to capture externally sourced candidate submissions — for example, resumes and applicant details arriving from a job board, a sourcing channel, or an imported data feed — and persist them into the pending data staging area until a downstream process converts them into formal candidate or applicant records. The package therefore plays an important integration role, decoupling the arrival of candidate data from the validation and processing that creates the corresponding person and recruitment entities.

Key Procedures and Functions

The package exposes three documented procedures, all of which operate on the pending data staging area:

• CREATE_PENDING_DATA — Inserts a new pending data record. This is the entry point used when candidate information first arrives from an external source. The procedure accepts a wide set of parameters covering the candidate's email address, name components, vacancy identifier, resume details (file name, description, MIME type), source and posting information, and an extensive set of person information attributes (per_information1 through per_information15) that map to descriptive flexfield segments. It also supports password and personal detail capture such as date of birth and sex, and includes a p_validate parameter defaulting to hr_api.g_false_num so callers can perform validation-only execution without committing a row.
• UPDATE_PENDING_DATA — Modifies an existing pending data record, allowing the staging row to be corrected or enriched after initial creation but before processing.
• DELETE_PENDING_DATA — Removes a pending data record, typically after it has been processed into the target recruitment tables or when the submission is rejected or purged.

These three procedures form a complete lifecycle management interface for staged candidate data: create, amend, and delete. No additional public functions are documented.

Tables Accessed

The ETRM metadata does not itemize specific base tables accessed through APPS synonyms, and no tables are explicitly listed. Based on the package's stated purpose and its parameter profile, the operations are directed at the iRecruitment pending data staging table that holds the candidate submission columns reflected in the CREATE_PENDING_DATA signature. The person information parameters map to HR descriptive flexfield columns, while the vacancy, posting content, and person identifiers link staged submissions to recruitment objects. Because the package is classified as "OTHER" rather than as a standard HR or public API, its table access is treated as an internal implementation detail of the iRecruitment processing model rather than a supported integration surface.

Usage Notes

IRC_PENDING_DATA_SWI is referenced by zero other packages in the documented metadata, which underscores its role as a leaf-level utility invoked by a narrow set of callers rather than a widely shared API. In practice it is called by the iRecruitment processing logic and by the mechanisms that ingest externally sourced candidate submissions — such as job board integration flows, resume parsing routines, and data import programs — before the pending records are promoted into live candidate and applicant data.

The p_validate parameter should be set appropriately: passing the default false-valued constant commits the change, whereas validation-only mode allows callers to test a submission without persisting it. Because the package is an internal "SWI" object and not a published public API, customizations should avoid calling it directly where a supported alternative exists; any direct invocation must account for the full parameter list, including the flexfield attributes, and should be regression-tested carefully during upgrade from 12.1.1 to 12.2.2 given the age and stability of the code.