Search Results job_basket_item_id

Overview

The IRC_JOB_BASKET_ITEMS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically supporting the iRecruitment functionality. As defined in the ETRM, its primary role is to store the jobs that an applicant has placed in their job basket. This table acts as the transactional backbone for the candidate's job search and application initiation process, enabling users to save and manage positions of interest before formally applying. Its existence is critical for tracking candidate engagement and sourcing pipeline metrics within the recruitment lifecycle.

Key Information Stored

The table's primary key is the JOB_BASKET_ITEM_ID, a unique identifier for each saved job record. The most significant foreign key relationship, as documented, is the RECRUITMENT_ACTIVITY_ID column, which links to the PER_RECRUITMENT_ACTIVITIES table. This connection associates each saved job item with a specific recruitment activity or job posting. While the provided metadata does not list all columns, typical data stored would include identifiers for the candidate (person or party ID), the job posting or vacancy, the date the item was added to the basket, and potentially status flags indicating if the item has been viewed or converted into an application.

Common Use Cases and Queries

This table is central to reporting and process flows related to candidate behavior. Common use cases include analyzing the popularity of specific job postings based on basket saves, identifying candidates with high engagement who have not yet applied, and generating reminders for candidates with items in their basket. A typical reporting query would join IRC_JOB_BASKET_ITEMS with PER_RECRUITMENT_ACTIVITIES to list saved jobs by title and candidate.

SELECT pra.NAME AS job_posting,
       COUNT(ijbi.job_basket_item_id) AS basket_saves
FROM hr.irc_job_basket_items ijbi
JOIN hr.per_recruitment_activities pra ON ijbi.recruitment_activity_id = pra.recruitment_activity_id
GROUP BY p ra.NAME;

Another common pattern is to identify candidates who have saved a job but not submitted an application, which would involve a NOT EXISTS subquery against the application tables.

Related Objects

The table maintains a direct and documented foreign key relationship, which is essential for data integrity and query joins.

• PER_RECRUITMENT_ACTIVITIES: This is the primary related table. The foreign key column IRC_JOB_BASKET_ITEMS.RECRUITMENT_ACTIVITY_ID references PER_RECRUITMENT_ACTIVITIES. This join retrieves details about the specific job posting, vacancy, or recruitment campaign that the candidate has saved.

While not listed in the provided excerpt, this table would also be logically related to candidate/person tables (e.g., PER_ALL_PEOPLE_F) and the main iRecruitment application table (IRC_APPLICATIONS), forming the complete data model for the candidate journey from discovery to application.