Results for “irc_prof_area_criteria_values”

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

Overview

The IRC_PROF_AREA_CRITERIA_VALUES table is a Human Resources (PER) module object in the Oracle E-Business Suite, owned by the HR schema. It stores the professional area values that a candidate has saved as part of a job search. Within the Oracle iRecruitment and recruitment functionality, this table acts as the persistence layer that captures the specific professional-area selections a candidate associates with a saved search criterion, enabling the system to match candidates against requisitions and job opportunities aligned to their stated area of professional interest.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone, which suggests it functions as a hub-like or independent reference table rather than a pure satellite or link. The table carries its own surrogate primary key and does not appear as the child in multiple foreign-key relationships, reinforcing its role as an independent value store referenced by the search criteria construct.

Key Information Stored

The table is documented with nine physical columns in ETRM 12.2.2. The most significant columns and their contents are:

• PROF_AREA_CRITERIA_VALUE_ID — The surrogate primary key, defined by the IRC_PROF_AREA_CRITERIA_PK unique index. This is the system-generated identifier that uniquely distinguishes each saved professional-area value record.
• SEARCH_CRITERIA_ID — The foreign key linking each professional-area value back to its parent search criterion in IRC_SEARCH_CRITERIA. This is the principal business-linkage column connecting the saved search to the values it contains.
• PROFESSIONAL_AREA — The descriptive content of the saved professional area. This holds the actual professional-area selection captured on behalf of the candidate.
• LAST_UPDATE_DATE — The timestamp of the most recent modification to the row.
• LAST_UPDATED_BY — The user identifier responsible for the most recent update.
• LAST_UPDATE_LOGIN — The login context associated with the last update, used for audit traceability.
• CREATED_BY — The user identifier who created the row.
• CREATION_DATE — The timestamp when the row was first inserted.
• OBJECT_VERSION_NUMBER — The optimistic locking version column, used by the Oracle Application Framework (OAF/ADF) to detect concurrent modification conflicts during update transactions.

The surrogate primary key (PROF_AREA_CRITERIA_VALUE_ID) is distinct from any business-key candidate; the documented unique index maps only to this surrogate, and no separate natural key is defined. The five WHO-style audit columns confirm that this is a standard EBS transactional/reference table with full row-level audit and concurrency control.

Common Use Cases and Queries

This table is typically accessed when reconstructing, reporting on, or troubleshooting a candidate's saved job-search preferences. Reporting scenarios include enumerating all professional areas attached to a saved search, auditing when a candidate last changed their selections, and feeding recruitment matching engines.

A representative query joining the value rows to their parent search criterion is:

• SELECT v.PROF_AREA_CRITERIA_VALUE_ID, v.SEARCH_CRITERIA_ID, v.PROFESSIONAL_AREA, v.CREATION_DATE, v.LAST_UPDATE_DATE
• FROM HR.IRC_PROF_AREA_CRITERIA_VALUES v
• WHERE v.SEARCH_CRITERIA_ID = :p_search_criteria_id
• ORDER BY v.PROFESSIONAL_AREA;

Administrators commonly query by CREATED_BY or LAST_UPDATED_BY to attribute changes to specific users, and filter on LAST_UPDATE_DATE for incremental or changed-since reporting. Because the table is standalone with a single documented FK, joins are straightforward and typically anchored through IRC_SEARCH_CRITERIA.

Related Objects

The documented FK relationship and the recruitment context identify the following significant related objects:

• IRC_SEARCH_CRITERIA — The parent table referenced through SEARCH_CRITERIA_ID → IRC_SEARCH_CRITERIA; the primary relationship defining this table's role.
• IRC_PROF_AREA_CRITERIA_PK — The unique index/constraint enforcing the PROF_AREA_CRITERIA_VALUE_ID primary key.
• PER / HR recruitment objects — Surrounding PER module tables that consume candidate job-search data for matching and requisition alignment.
• Oracle iRecruitment application pages — OAF-based UI constructs that read and write these rows through the OBJECT_VERSION_NUMBER optimistic locking mechanism.

Because the table is classified as standalone, it does not serve as a parent hub to numerous dependent children; its principal integration point is the search criteria parent, making IRC_SEARCH_CRITERIA the dominant join target for any query, report, or data-extraction task involving this object.