Search Results release_offer

Overview

APPS.IRC_OFFERS_SWI is a self-service wrapper package within the Oracle E-Business Suite iRecruitment module. It exposes the underlying recruitment offer API, primarily irc_offers_api, to self-service callers and to internal Oracle components that must create, modify, and manage employment offers made to applicants. The package is defined with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the definer, which is characteristic of Oracle's self-service wrapper convention. In EBS 12.1.1 and 12.2.2, the package sits at the boundary between the iRecruitment offer user interface and the HR foundation tables that record assignments, proposals, and benefits enrolments.

The primary business function is to manage the lifecycle of an offer extended to a candidate: creation, update, deletion, hold and release, closure, assignment linkage, offer letter handling, and final transaction processing. The package also coordinates benefits processing and attachment handling, reflecting the tight coupling between recruitment offers and downstream HR and Benefits operations. The bundled header comment of version 120.15 (2011/02/03) confirms its long-standing role as the wrapper to irc_offers_api.create_offer and notes an "Internal Development use only" access status.

Key Procedures and Functions

The package exposes twenty documented procedures and functions grouped by functional area.

• Offer lifecycle: CREATE_OFFER, UPDATE_OFFER, DELETE_OFFER, CLOSE_OFFER, HOLD_OFFER, and RELEASE_OFFER manage the offer record itself. RELEASE_OFFER is the entry point most relevant to the user's release_offer search; it lifts a hold previously placed on an offer, returning it to an active state.
• Assignment management: CREATE_OFFER_ASSIGNMENT, UPDATE_OFFER_ASSIGNMENT, and DELETE_OFFER_ASSIGNMENT maintain the association between an offer and the applicant or offer assignment identifiers.
• Offer letters: UPLOAD_OFFER_LETTER accepts and stores the generated offer letter, while HANDLEATTACHMENTSWHENCOMMIT, HANDLEATTACHMENTSWHENREJECTED, and HANDLEATTACHMENTSWHENEDIT manage attachment state across transaction commit, rejection, and edit scenarios.
• Benefits processing: RUN_BENMGLE_FOR_IREC, IS_RUN_BENMGLE_FOR_IREC_REQD, and VOID_BEN_RECORDS control whether and how Benefits benefit-management logic runs for iRecruitment activity, including voiding benefit records.
• Transaction processing: PROCESS_OFFERS_API, PROCESS_ASG_API, and FINALIZE_TRANSACTION drive the API-level and transaction finalisation steps.
• Housekeeping: CLEAR_GLOBAL_DATA resets package-level global state, typically invoked at the end of a processing cycle.

Tables Accessed

Through APPS synonyms the package reads and writes: IRC_OFFERS, which stores the offer header, status, and dates; IRC_OFFER_STATUS_HISTORY, which archives transitions such as hold and release; PER_ALL_ASSIGNMENTS_F, which holds the applicant and offer assignments; PER_PAY_PROPOSALS for salary proposal data linked to the offer; BEN_PIL_ASSIGNMENT for benefits participation; and HR_API_TRANSACTIONS for date-tracked API transaction records. XMLDOM and XMLPARSER are referenced to support XML-based data (for example, offer letter and attachment payloads).

Usage Notes

IRC_OFFERS_SWI is normally invoked indirectly: iRecruitment self-service pages and concurrent programs call the wrapper, which in turn calls irc_offers_api. Customisations and integrations should call the underlying API rather than this wrapper, consistent with its "Internal Development use only" designation. The package is not referenced by other documented packages, so it is a leaf-level entry point. Because it runs AUTHID CURRENT_USER, ensure the calling schema has appropriate grants on the IRC, PER, BEN, and HR tables it touches, and always inspect the returned p_return_status values to detect success or failure.