Results for “irc_job_basket_items_pk”

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

Overview

The IRC_JOB_BASKET_ITEMS table is a Human Resources (PER) module object in the Oracle E-Business Suite, owned by the HR schema. It stores the jobs that an applicant has placed in their personal job basket within the iRecruitment application. When candidates browse open vacancies and elect to save or bookmark them for later review, a record is written to this table capturing the association between the applicant and the specific recruitment activity (job posting).

Because the table is structured around a surrogate primary key with attribute columns describing the applicant-to-posting association, the ETRM metadata suggests a satellite-leaning Data Vault classification. In practice, this table behaves as a dependent child of the recruiting activity and person records rather than as an independent hub; its rows describe the state and context of a saved job selection.

Key Information Stored

Ten columns are documented in the 12.2.2 physical schema. The most significant include:

• JOB_BASKET_ITEM_ID — the surrogate primary key defined by the IRC_JOB_BASKET_ITEMS_PK unique index. This is the only documented business-key candidate and uniquely identifies each basket entry.
• RECRUITMENT_ACTIVITY_ID — foreign key to PER_RECRUITMENT_ACTIVITIES, identifying the specific job posting or recruitment activity the applicant has saved.
• PERSON_ID — identifies the person (applicant) associated with the basket item.
• PARTY_ID — the TCA party reference for the applicant, linking the row to the trading community model.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework (OAF) to manage concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing row-level change history.

Common Use Cases and Queries

Reporting on job-basket activity is common in recruiting analytics, for example identifying which postings are most frequently saved by applicants. A typical query joins the basket to the recruitment activity table:

• Applicant basket listing: SELECT jbi.job_basket_item_id, jbi.person_id, jbi.recruitment_activity_id FROM irc_job_basket_items jbi WHERE jbi.person_id = :person_id;
• Posting popularity: SELECT recruitment_activity_id, COUNT(*) FROM irc_job_basket_items GROUP BY recruitment_activity_id ORDER BY 2 DESC;
• Audit reconciliation: filter on last_update_date to detect changes within a review window for data-quality checks.

These queries support recruiter dashboards, applicant self-service verification, and purge routines that clear stale basket entries.

Related Objects

The principal documented relationship is the foreign key from IRC_JOB_BASKET_ITEMS.RECRUITMENT_ACTIVITY_ID to PER_RECRUITMENT_ACTIVITIES. Additional significant related objects include:

• PER_RECRUITMENT_ACTIVITIES — parent table holding job postings; joined on RECRUITMENT_ACTIVITY_ID.
• PER_PEOPLE_F / PER_ALL_PEOPLE_F — applicant identity via PERSON_ID.
• HZ_PARTIES — party-level demographic reference via PARTY_ID.
• IRC_APPLICANTS — applicant profile linked through PERSON_ID or PARTY_ID.
• IRC_JOB_BASKET_ITEMS_PK — the unique index enforcing the surrogate primary key.

These relationships enable the iRecruitment pages and concurrent programs to render, validate, and maintain job-basket functionality.