Search Results is_run_benmgle_for_irec_reqd




Overview

APPS.IRC_OFFERS_SWI is a public API package body within the Oracle E-Business Suite iRecruitment (IRC) module. Its header comment line, $Header: iriofswi.pkb 120.24.12010000.3 2009/01/07, identifies it as a fully supported API wrapper (the "_SWI" suffix denotes a "Server Web Interface" style API) shipped in release 12.1.1 and unchanged in 12.2.2. The package encapsulates the business logic required to create, maintain, and finalize job offers extended to applicants, and to coordinate those offers with Oracle Advanced Benefits (BEN) and Oracle Human Resources (PER). It shields callers from direct data manipulation against the underlying tables, validating all inputs and writing an API transaction record so that downstream HR and Benefits processes remain synchronized. The package owner is APPS and its ETRM classification is OTHER, reflecting that it is an integration-level rather than a self-service API.

Key Procedures and Functions

The twenty documented routines fall into four functional groups.

  • Offer life-cycle procedures: CREATE_OFFER and UPDATE_OFFER accept the complete offer attribute set—status, discretionary job title, offer extended method, respondent, expiry and proposed start dates, letter tracking code and postal service details, applicant and offer assignment identifiers, address and template identifiers, letter file metadata, and fifteen descriptive flexfield attribute columns. DELETE_OFFER removes an offer, while CLOSE_OFFER, HOLD_OFFER, and RELEASE_OFFER implement the status transitions that govern an active offer.
  • Assignment handling: CREATE_OFFER_ASSIGNMENT, UPDATE_OFFER_ASSIGNMENT, and DELETE_OFFER_ASSIGNMENT maintain the link between an offer and the applicant assignment created for it.
  • Offer letter processing: UPLOAD_OFFER_LETTER stores the generated letter document and its file type and name against the offer.
  • Benefits and HR integration: RUN_BENMGLE_FOR_IREC and the function IS_RUN_BENMGLE_FOR_IREC_REQD determine whether and how the Benefits "Manage Life Events" (BENMGLE) process must be executed for an iRecruitment hire. PROCESS_OFFERS_API and PROCESS_ASG_API drive bulk processing of offers and assignments; FINALIZE_TRANSACTION and VOID_BEN_RECORDS commit or reverse Benefits records; HANDLEATTACHMENTSWHENCOMMIT, HANDLEATTACHMENTSWHENREJECTED, and HANDLEATTACHMENTSWHENEDIT route offer-letter attachments according to the transaction outcome; and CLEAR_GLOBAL_DATA resets the package's session-level global variables.

Tables Accessed

The package reads and writes IRC_OFFERS, the primary store of offer records, and IRC_OFFER_STATUS_HISTORY, which captures each status change for audit purposes. It interacts with PER_ALL_ASSIGNMENTS_F to create or validate the applicant assignment, with PER_PAY_PROPOSALS for salary proposal data associated with the offer, and with BEN_PIL_ASSIGNMENT to enroll the assignment in Benefits. HR_API_TRANSACTIONS is used to register each API call in the standard HR transaction framework. XMLDOM and XMLPARSER are referenced for parsing and generating the XML payloads used by the offer-letter and Benefits integration routines.

Usage Notes

IRC_OFFERS_SWI is invoked primarily by the iRecruitment Manager and Recruiter self-service flows and by the offer-related concurrent programs that process offers and assignments in bulk. Because the ETRM record shows zero referencing packages, it is not embedded within another delivered PL/SQL API; it is instead called from the iRecruitment Java/Forms tier and is available for custom extensions. Developers integrating with this package should invoke IS_RUN_BENMGLE_FOR_IREC_REQD before calling RUN_BENMGLE_FOR_IREC, and should always conclude a logical unit of work with FINALIZE_TRANSACTION so that Benefits records are committed or voided consistently. All validation and date-effectivity handling is performed internally, so direct DML against IRC_OFFERS and its related tables should be avoided in favor of these entry points.