Results for “irc_assignment_details_f”

50+ results




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

Overview

The IRC_ASSIGNMENT_DETAILS_F table resides in the HR schema and belongs to the PER (Human Resources) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores iRecruitment-specific additional assignment details, extending the standard assignment record with recruitment-driven attributes. In practice, the table captures the linkage between an assignment (the recruiting requisition or applicant assignment) and the recruitment attempt that produced qualification and consideration outcomes. Because it carries effective-dated, versioned rows tied to a single parent assignment, it functions as a date-tracked satellite of the assignment entity rather than a hub or link. The heuristic Data Vault classification provided in the metadata is standalone, indicating that the table is modeled without strong parent-child dependency chains and is best treated as an independent detail store. Its status is VALID, confirming it is a supported, queryable object in the documented release.

Key Information Stored

The table contains 15 documented columns. The surrogate primary key is ASSIGNMENT_DETAILS_ID, enforced through the IRC_ASSIGNMENT_DETAILS_F_PK unique index. Business-key candidates are captured by the unique index IRC_ASSIGNMENT_DETAILS_F_U1, which spans ASSIGNMENT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and DETAILS_VERSION. This composite key establishes the effective-dated, versioned nature of each row.

  • ASSIGNMENT_ID — the parent assignment this detail row qualifies.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date range during which the detail version is valid.
  • DETAILS_VERSION — the version number distinguishing successive detail revisions for the same assignment.
  • LATEST_DETAILS — flag identifying the current, most recent detail row.
  • ATTEMPT_ID — foreign key referencing OTA_ATTEMPTS, linking the assignment detail to a recruitment or training attempt.
  • QUALIFIED — indicates whether the candidate/assignment met qualification criteria.
  • CONSIDERED — indicates whether the candidate/assignment was considered in the recruitment process.
  • OBJECT_VERSION_NUMBER — optimistic locking version for concurrent update control.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns tracking row provenance.

Common Use Cases and Queries

Reporting on iRecruitment outcomes typically requires filtering to the latest effective detail row. A representative query retrieving current, qualified assignments joined to their attempts is:

  • SELECT a.ASSIGNMENT_ID, a.QUALIFIED, a.CONSIDERED, a.ATTEMPT_ID
  • FROM IRC_ASSIGNMENT_DETAILS_F a
  • WHERE a.LATEST_DETAILS = 'Y' AND a.QUALIFIED = 'Y';

Point-in-time analysis uses the effective dates and version columns: filtering on SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE yields the detail version active at a given moment. Auditing changes relies on DETAILS_VERSION ordered descending per ASSIGNMENT_ID. Determining whether an attempt produced a considered or qualified assignment is a common recruitment funnel report, joining this table to OTA_ATTEMPTS on ATTEMPT_ID.

Related Objects

The primary documented relationship is the foreign key from ATTEMPT_ID to OTA_ATTEMPTS, which anchors each detail row to its originating attempt. Because ASSIGNMENT_ID is a business-key component, it logically references the core assignment entity (PER_ALL_ASSIGNMENTS_F), the master assignment store in the HR schema. Recruitment requisition and applicant data flow through iRecruitment views that query this table. The IRC_ASSIGNMENT_DETAILS_F_PK and IRC_ASSIGNMENT_DETAILS_F_U1 unique indexes are the principal access paths. The WHO columns align with the standard audit infrastructure used across HR tables, and OBJECT_VERSION_NUMBER supports the Oracle Applications framework's concurrency model. Together these objects position IRC_ASSIGNMENT_DETAILS_F as the recruitment-specific extension of the assignment record within iRecruitment.