Search Results analysis_criteria_id




Overview
Explore in AI Chat

Overview

The HR.PER_ANALYSIS_CRITERIA table is a key flexfield combinations table within the Oracle E-Business Suite Human Resources (HRMS) module. Its primary role is to store the unique combinations of segment values that define the Personal Analysis Flexfield (also known as the Special Information Flexfield). This flexfield is a critical configuration tool used to capture structured, user-defined information for two main purposes: defining job and position requirements, and recording special information about a person. The table is central to the flexfield architecture, enabling the storage and validation of these custom data structures. Its design and relationships are consistent across both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table's structure follows the standard pattern for a key flexfield combinations table. The most critical column is the system-generated primary key, ANALYSIS_CRITERIA_ID, which uniquely identifies each flexfield combination and is the primary reference point for all related data. The flexfield structure is defined by the ID_FLEX_NUM column, which links to the specific flexfield definition. The actual user-defined data is stored in the segment columns (SEGMENT1, SEGMENT2, etc., up to SEGMENT20 as per standard flexfield design). Administrative flags control the combination's lifecycle: ENABLED_FLAG indicates if the combination is active, while START_DATE_ACTIVE and END_DATE_ACTIVE define its valid date range. The table also includes standard Oracle "Who" columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) for tracking changes and concurrent program interactions.

Common Use Cases and Queries

This table is primarily queried in two contexts: reporting on job/position requirements and retrieving person-specific special information. A common reporting use case involves joining to related transactional tables to list all valid analysis criteria for a specific job or person. For example, to find all active special information entries for a person, one would join PER_PERSON_ANALYSES to PER_ANALYSIS_CRITERIA. A typical validation or lookup query would be:

  • SELECT segment1, segment2, segment3 FROM hr.per_analysis_criteria WHERE analysis_criteria_id = :p_id AND enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Technical consultants often query this table to understand the specific values stored in the flexfield segments for a given ID, especially when debugging data issues or building custom integrations that consume this flexfield data.

Related Objects

The HR.PER_ANALYSIS_CRITERIA table is referenced as a parent table by several key transactional tables via foreign key relationships, as documented in the ETRM metadata. These relationships demonstrate its core functional usage:

  • PER_JOB_REQUIREMENTS.ANALYSIS_CRITERIA_ID: Links analysis criteria to specific job requirements.
  • PER_MM_JOB_REQUIREMENTS.NEW_ANALYSIS_CRITERIA_ID and PER_MM_JOB_REQUIREMENTS.ANALYSIS_CRITERIA_ID: Used in mass maintenance operations for job requirements.
  • PER_PERSON_ANALYSES.ANALYSIS_CRITERIA_ID: The primary link for storing a person's special information flexfield data.
  • PQH_TXN_JOB_REQUIREMENTS.ANALYSIS_CRITERIA_ID: Used within the Position Management (PQH) processes for transactional job requirements.

All these relationships join on the ANALYSIS_CRITERIA_ID column, reinforcing its role as the unique identifier for a flexfield combination. The primary key constraint PER_ANALYSIS_CRITERIA_PK enforces this uniqueness.