Results for “irc_location_criteria_values”

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

Overview

The IRC_LOCATION_CRITERIA_VALUES table is a Human Resources (PER) module data object within the Oracle E-Business Suite iRecruitment product family. It stores the individual location values that a candidate has saved as part of a stored job search. When a candidate defines a job search and selects one or more preferred work locations, each selected location is persisted as a discrete row in this table, tied back to the parent search definition. The table therefore functions as the child detail store for location-specific search criteria, complementing the broader search definition record.

Mined from its foreign key structure, the table carries a heuristic Data Vault classification of standalone. This is a modeling suggestion: the table is neither a pure hub nor a pure link in the classical sense, though it does carry a foreign key to a parent search criteria record. In a Data Vault or dimensional model, IRC_LOCATION_CRITERIA_VALUES would most naturally be treated as a satellite or a child detail table hanging off the search criteria hub, capturing the multi-valued location selections associated with a single saved search. Its physical owner is the HR schema, and the object is reported as VALID under ETRM 12.2.2 metadata.

Key Information Stored

The table is documented with nine columns. The most consequential are the following:

• LOCATION_CRITERIA_VALUE_ID — The surrogate primary key. It uniquely identifies each location criteria value row and is the single column comprising the IRC_LOCATION_CRITERIA_PK primary key.
• SEARCH_CRITERIA_ID — The foreign key linking each location value to its parent record in IRC_SEARCH_CRITERIA. This is the primary business relationship column and the principal join key for reporting.
• DERIVED_LOCALE — Captures the locale context derived for the saved location criterion, supporting multilingual and regional display of search results.
• OBJECT_VERSION_NUMBER — The standard Oracle EBS optimistic locking column used to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when the row was last modified, by which user, and through which login session.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the original creation user and timestamp.

No unique index other than the primary key is documented, so LOCATION_CRITERIA_VALUE_ID remains the only documented surrogate key candidate; SEARCH_CRITERIA_ID is a foreign-key candidate rather than a unique business key.

Common Use Cases and Queries

Typical usage centers on retrieving, reporting, and analyzing the locations saved within candidate job searches. A common pattern joins the child values to their parent search:

• List all locations for a given saved search — Select LOCATION_CRITERIA_VALUE_ID and DERIVED_LOCALE from IRC_LOCATION_CRITERIA_VALUES where SEARCH_CRITERIA_ID equals a supplied value.
• Count locations per search — Aggregate row counts grouped by SEARCH_CRITERIA_ID to identify searches filtering on many locations.
• Candidate search reporting — Join to IRC_SEARCH_CRITERIA on SEARCH_CRITERIA_ID to associate location preferences with the owning candidate and search name.
• Data migration and cleanup — Identify orphaned rows where SEARCH_CRITERIA_ID no longer resolves to a parent record.

Because DERIVED_LOCALE is stored at the value level, locale-aware reporting can be produced directly without additional lookups. Audit columns support change-tracking and compliance reporting.

Related Objects

The most significant related object is the parent search definition, with which this table has a documented foreign key relationship:

• IRC_SEARCH_CRITERIA — Referenced by IRC_LOCATION_CRITERIA_VALUES.SEARCH_CRITERIA_ID. This is the parent object that defines each saved candidate job search; the location values represent its multi-valued location detail.

Beyond this documented relationship, the table participates in the broader iRecruitment and PER schema family. Reporting queries typically traverse from IRC_SEARCH_CRITERIA to the candidate and person records that own each search. The table depends on standard EBS audit and locale infrastructure but has no additional documented foreign keys of its own, consistent with its standalone Data Vault classification.