Results for “decline_reason”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IRC_OFFER_STATUS_HISTORY is a transactional history table in the Oracle E-Business Suite Human Resources (PER) product family. It is owned by the HR schema and maintains the audit trail of offer status transitions recorded against recruiting offers. Every time an offer moves through its lifecycle — for example from draft to extended, or from extended to accepted or declined — a new row is inserted into this table capturing the new status, the moment the change occurred, and the parties responsible for the change. The table therefore preserves a complete chronological record that would otherwise be lost if only the current status on IRC_OFFERS were retained.

From a dimensional modeling perspective, the metadata suggests a satellite-leaning Data Vault classification. This heuristic is based on the foreign key structure: the table carries a single parent reference to IRC_OFFERS and holds descriptive, time-stamped attributes that describe the changing state of that parent. In Data Vault terms, IRC_OFFERS functions as the hub or parent entity, while IRC_OFFER_STATUS_HISTORY behaves as a satellite capturing the effectivity-dated status attributes for each offer.

Key Information Stored

The table contains twelve documented columns. The most significant are:

The documented unique index is only on OFFER_STATUS_HISTORY_ID, which is a surrogate key rather than a composite business key. The business meaning of a record is derived from the combination of OFFER_ID, OFFER_STATUS, and STATUS_CHANGE_DATE.

Common Use Cases and Queries

Typical uses include offer pipeline reporting, time-to-hire analysis, and audit investigations. A common pattern reconstructs the full status timeline for an offer:

  • SELECT offer_status, status_change_date FROM irc_offer_status_history WHERE offer_id = :offer_id ORDER BY status_change_date;
  • SELECT * FROM irc_offer_status_history WHERE decline_reason IS NOT NULL;

Reporting queries frequently join to IRC_OFFERS to obtain requisition, candidate, and organization context, then filter on STATUS_CHANGE_DATE to measure cycle times between successive statuses. Audit scenarios filter on CREATED_BY or LAST_UPDATED_BY to attribute changes to specific recruiters. Because decline reasons are stored here, this table also supports loss-analysis dashboards.

Related Objects

The principal relationships documented are:

  • IRC_OFFERS — joined via IRC_OFFER_STATUS_HISTORY.OFFER_ID = IRC_OFFERS.OFFER_ID; the parent offer record.
  • IRC_NOTES — references this table through IRC_NOTES.OFFER_STATUS_HISTORY_ID, allowing notes to be attached to a specific status change.

Additional related objects commonly used in the same reporting context include IRC_CANDIDATES, IRC_REQUISITIONS, and PER_ALL_PEOPLE_F for candidate and recruiter attribution. The Oracle TCA/HR APIs that manage offers should be used for inserting status transitions rather than direct DML, ensuring the history and object version columns remain consistent.