Search Results send_onhold_notification

Overview

IRC_OFFER_NOTIFICATIONS_PKG is an Oracle EBS Applications (APPS) schema PL/SQL package belonging to the iRecruitment module. Its documented purpose is to manage the generation and delivery of notifications tied to the offer lifecycle within iRecruitment. When a recruiting administrator or manager extends an offer to an applicant, the system must communicate that event, track the applicant's response, and handle downstream circumstances such as an offer expiring, being placed on hold, being withdrawn, or being accepted or declined. This package centralizes that notification logic, insulating calling forms and workflows from the mechanics of building notification content and dispatching Workflow (WF) events.

The package is classified as an OTHER API within the ETRM metadata, meaning it is not a formal public interface but an internal implementation package invoked by iRecruitment's own forms, workflow processes, and concurrent logic. It is ETRM-validated and depends only on SYS.STANDARD and the SYS schema at the declared dependency level, with all business object access occurring through APPS synonyms.

Key Procedures and Functions

The package exposes ten documented procedures and functions, organized around URL generation and notification dispatch:

• GET_VIEW_OFFER_URL — Builds the URL used by an applicant to view an offer through the iRecruitment self-service interface.
• GET_MANAGER_VIEW_OFFER_URL — Builds the corresponding manager-facing URL for reviewing an offer.
• GET_EXTEND_OFFER_DURATION_URL — Produces the URL that supports extending the duration of an active offer.
• SEND_RCVD_WF_NOTIFICATION — Sends the Workflow notification acknowledging that an offer has been received or recorded.
• SEND_EXPIRY_NOTIFICATION — Issues the advance warning notification before an offer's expiry date is reached.
• SEND_EXPIRED_NOTIFICATION — Issues the notification raised once an offer has actually lapsed past its expiry.
• SEND_APPLICANT_RESPONSE — Communicates the applicant's response (acceptance or decline) to the appropriate recipients.
• SEND_ONHOLD_NOTIFICATION — Notifies recipients when an offer is placed on hold.
• SEND_WITHDRAWAL_NOTIFICATION — Notifies recipients when an offer is withdrawn.
• SEND_DCLN_ACPTD_OFFER_NOTIF — Handles the notification associated with a declined or accepted offer outcome.

Tables Accessed

The package reads and writes the core iRecruitment and Oracle Human Resources entities needed to resolve recipients and render offer content:

• IRC_OFFERS, IRC_OFFER_STATUS_HISTORY, IRC_NOTES, IRC_REFERRAL_INFO — offer records, status transitions, free-text notes, and referral context that supply the substance of each notification.
• PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ALL_VACANCIES, PER_VAC_LINKED_ASSIGNMENTS — applicant and manager identity, assignment context, vacancy details, and vacancy-to-assignment linkage used to determine who is notified and what offer is referenced.
• FND_USER, FND_RESPONSIBILITY, FND_APPLICATION, FND_FORM_FUNCTIONS, FND_PROFILE_OPTION_VALUES — EBS foundation data used to resolve user accounts, responsibility-based access, application context, form function security, and profile option settings such as notification preferences or URLs.
• WF_EVENT_T — the Workflow event structure used to queue and raise notifications.
• DBMS_LOB — Oracle-supplied LOB package, indicating notification bodies may be assembled or manipulated as large objects.

Usage Notes

IRC_OFFER_NOTIFICATIONS_PKG is not intended for direct customer invocation; no other package references it, and it is not documented as a supported public API. It is invoked internally by iRecruitment offer management forms and by Workflow processes that fire at offer lifecycle milestones—extension, response, expiry, hold, withdrawal, and acceptance or decline. The URL-generating functions are typically called when constructing notification bodies so recipients can navigate directly to the relevant offer page. Customizations should avoid calling these procedures directly; instead, customers should subscribe to the underlying Workflow events or extend behavior through supported iRecruitment configuration. Because the package depends on FND profile options and responsibility data, output can vary with the runtime environment and the profile settings of the recipient's context.