Search Results irc_offers_api




Overview
Explore in AI Chat

Overview

IRC_OFFERS_API is the public application programming interface for the Oracle iRecruitment offer management component within Oracle E-Business Suite. The package encapsulates the business logic that governs the creation, modification, lifecycle transition, and deletion of recruitment offers extended to applicants and candidates. It belongs to the APPS schema and is classified in ETRM as an API, meaning it is intended to be called by other Oracle modules, workflow processes, and customer extensions rather than being executed directly by end users through a user interface. The package acts as the authoritative gateway through which offer records in IRC_OFFERS are validated, persisted, and reconciled with assignment data held in the Oracle HRMS core tables.

In the EBS 12.1.1 and 12.2.2 releases, the package remains valid and is a dependency of the iRecruitment offer workflow notification and service components, confirming its central role in the hire-to-offer business flow.

Key Procedures and Functions

The documented API surface comprises eleven procedures and functions that cover the full offer lifecycle as well as offer-to-assignment linkage:

  • CREATE_OFFER — Inserts a new offer record, performing the validation required before an offer can be extended to a candidate.
  • UPDATE_OFFER — Modifies attributes of an existing offer, typically while it remains in an editable status.
  • DELETE_OFFER — Removes an offer record, subject to the status restrictions enforced by the package.
  • CLOSE_OFFER — Terminates an offer, moving it to a closed state and recording the status transition.
  • HOLD_OFFER — Places an active offer on hold, suspending further processing without closing it.
  • RELEASE_OFFER — Releases an offer previously placed on hold, restoring it to an active state.
  • CREATE_OFFER_ASSIGNMENT — Creates the association between an offer and the assignment data that will ultimately be used to hire the candidate.
  • UPDATE_OFFER_ASSIGNMENT — Amends an existing offer-assignment association.
  • DELETE_OFFER_ASSIGNMENT — Removes the offer-assignment association.
  • UPLOAD_OFFER_LETTER — Uploads or attaches the generated offer letter document to the offer record.
  • OTHER_EXTENDED_OFFERS_COUNT — A function that returns a count of other extended offers, supporting business rules that limit or track concurrent offers.

All procedures follow standard Oracle API conventions, raising exceptions on validation failure and normally being invoked with a rollback-on-error strategy from the calling layer.

Tables Accessed

The package operates against IRC_OFFERS and IRC_ASSIGNMENT_STATUSES as its primary transactional tables, with IRC_OFFER_STATUS_HISTORY recording the audit trail of status changes produced by CLOSE_OFFER, HOLD_OFFER, and RELEASE_OFFER. On the HRMS side, the API reads and writes PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, PER_ASSIGNMENT_STATUS_TYPES, PER_PAY_PROPOSALS, and PER_VAC_LINKED_ASSIGNMENTS in order to construct the assignment that results from an accepted offer, including payroll proposal and vacancy linkage information. HR_API_TRANSACTIONS and FND_USER support the HR API framework and user context respectively, while WF_NOTIFICATIONS is engaged so that workflow notifications are generated or updated as the offer progresses. PER_PAY_PROPOSALS and the assignment tables are typically touched through the CREATE_OFFER_ASSIGNMENT and UPDATE_OFFER_ASSIGNMENT routines.

Usage Notes

IRC_OFFERS_API is not intended for direct end-user execution. It is invoked indirectly whenever a recruiter or approver performs an offer action through the iRecruitment offer pages, and it is called by the offer service interface IRC_OFFERS_SWI, the notification package IRC_OFFER_NOTIFICATIONS_PKG, and by HRMS packages such as HR_APPLICANT_API, HR_ASSIGNMENT_API, HR_WORKFLOW_SERVICE, and HRHIRAPL. The ETRM dependency report confirms that the package is referenced by eight other packages in the APPS schema. Customizations that need to create or transition offers programmatically should call this API rather than issuing direct DML against IRC_OFFERS, because the package enforces the status model, maintains history records, and keeps the HRMS assignment and workflow data consistent. Because the interface signature dates from earlier releases and is documented as valid in both 12.1.1 and 12.2.2, existing integrations can generally be carried forward across upgrades without change. Developers should always invoke the API within a properly scoped transaction and handle the raised exceptions, since failures are surfaced through the standard HR_API error mechanism rather than by silent rollback.