Results for “min_qual_level”

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

Overview

IRC_SEARCH_CRITERIA is a core recruitment configuration table owned by the HR schema and delivered under the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the job matching preferences and saved advanced search criteria that drive the iRecruitment candidate-to-requisition matching engine. Each row represents a distinct saved search — either a reusable matching profile used by the matching process, or a persisted advanced search that a recruiter or manager has named and retained for repeated use. Because the table carries both the selection parameters and the qualification thresholds used to score candidates, it sits at the center of the matching configuration model rather than acting as a transactional or audit entity.

Under the heuristic Data Vault classification mined from the foreign-key structure, the object is modeled as a link. This suggests the table functions primarily as an associative construct, binding search criteria to qualification definitions through the MIN_QUAL_LEVEL and MAX_QUAL_LEVEL references, and extending that association outward through child criteria-value tables. This classification is a modeling suggestion only; the physical object remains a conventional relational table with 100 columns and a single-column surrogate primary key.

Key Information Stored

The surrogate primary key is SEARCH_CRITERIA_ID, enforced by the unique index IRC_SEARCH_CRITERIA_PK. This column is the definitive identifier referenced by all dependent criteria-value tables. Three additional unique indexes of the form SYS_IL0000202641C00026$$ through C00107$$ exist on the table; these correspond to Oracle-managed LOB or index-organized segments rather than business-key candidates. No separate natural business key is documented — SEARCH_NAME and OBJECT_ID together constitute the practical business identifier used when locating a stored search.

• SEARCH_CRITERIA_ID — surrogate primary key and the join column for all child criteria tables.
• OBJECT_ID / OBJECT_TYPE — identifies the owning entity and its type, typically a requisition, vacancy, or recruiter context.
• SEARCH_NAME / SEARCH_TYPE — the user-visible name of the saved search and the classification that distinguishes matching profiles from ad hoc advanced searches.
• MIN_QUAL_LEVEL / MAX_QUAL_LEVEL — foreign keys to PER_QUALIFICATION_TYPES that bound the acceptable qualification range.
• MIN_SALARY / MAX_SALARY / SALARY_CURRENCY / SALARY_PERIOD — the compensation window applied during matching.
• MATCH_COMPETENCE / MATCH_QUALIFICATION — flags controlling whether competencies and qualifications participate in scoring.
• USE_FOR_MATCHING — the operational switch that designates a saved profile as active for automated candidate matching.
• LOCATION_ID / LOCATION / DISTANCE_TO_LOCATION / GEOCODE_LOCATION / GEOCODE_COUNTRY — geographic filters and geocoded search boundaries.
• KEYWORDS, JOB_TITLE, DEPARTMENT, PROFESSIONAL_AREA, EMPLOYMENT_CATEGORY, WORK_AT_HOME, TRAVEL_PERCENTAGE — descriptive filters narrowing the candidate pool.
• EMPLOYEE / CONTRACTOR — flags restricting the search by workforce type.
• DATE_POSTED — recency filter applied to requisition posting dates.
• ATTRIBUTE1–30 and ISC_INFORMATION1–30 — DFF and descriptive flexfield segments for client-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard WHO columns and optimistic locking support.

Common Use Cases and Queries

The most frequent requirement is enumerating the active matching profiles configured for a business group, then inspecting the qualification band applied to each. The following pattern joins the search criterion to its qualification ceiling and floor:

• SELECT sc.SEARCH_CRITERIA_ID, sc.SEARCH_NAME, sc.USE_FOR_MATCHING, q1.NAME min_qual, q2.NAME max_qual FROM irc_search_criteria sc, per_qualification_types q1, per_qualification_types q2 WHERE sc.MIN_QUAL_LEVEL = q1.QUALIFICATION_TYPE_ID(+) AND sc.MAX_QUAL_LEVEL = q2.QUALIFICATION_TYPE_ID(+) AND sc.USE_FOR_MATCHING = 'Y';
• Reporting on saved advanced searches by owner, using OBJECT_ID and SEARCH_TYPE to group recruiter activity.
• Auditing salary-range configuration (MIN_SALARY, MAX_SALARY, SALARY_CURRENCY, SALARY_PERIOD) against organisational compensation policy.
• Identifying geocoded searches using GEOCODE_LOCATION and GEOMETRY for distance-based candidate sourcing analysis.

Because the table uses WHO audit columns, incremental extracts can be driven from LAST_UPDATE_DATE, which is the recommended approach for integration and data-warehouse loads.

Related Objects

The relationship model is defined by two foreign keys outbound to PER_QUALIFICATION_TYPES and two inbound references from criteria-value detail tables. The most significant related objects are:

• PER_QUALIFICATION_TYPES — referenced twice, via IRC_SEARCH_CRITERIA.MIN_QUAL_LEVEL and IRC_SEARCH_CRITERIA.MAX_QUAL_LEVEL, providing the qualification level definitions for the search band.
• IRC_LOCATION_CRITERIA_VALUES — child table joined on SEARCH_CRITERIA_ID, holding the individual locations included in a saved search.
• IRC_PROF_AREA_CRITERIA_VALUES — child table joined on SEARCH_CRITERIA_ID, holding the professional areas included in a saved search.
• PER_ALL_PEOPLE_F — indirectly related through the recruiter and candidate contexts established by OBJECT_ID and the WHO columns.
• IRC_REQUISITIONS / IRC_VACANCIES — the recruitment entities whose matching behaviour is governed by rows where USE_FOR_MATCHING is enabled.

When building extensions or reports, always resolve the parent through SEARCH_CRITERIA_ID rather than SEARCH_NAME, since names are not guaranteed unique across business groups.