Search Results per_analysis_criteria

Overview

The PER_ANALYSIS_CRITERIA table is a core data structure within the Oracle E-Business Suite Human Resources (PER) module, specifically for versions 12.1.1 and 12.2.2. It functions as the flexfield combination table for the Personal Analysis Key Flexfield (KFF). This design is fundamental to Oracle's flexfield architecture, where the table stores validated, unique combinations of segments defined for the descriptive flexfield. The table's primary role is to serve as a centralized reference and validation point for personal analysis codes, enabling the flexible categorization and analysis of individuals within the HR system without requiring custom table structures.

Key Information Stored

The table's central purpose is to store each unique combination of the Personal Analysis flexfield segments. The primary column is ANALYSIS_CRITERIA_ID, a system-generated unique identifier (Primary Key) that acts as a foreign key in various transactional tables. While the specific segment columns (e.g., SEGMENT1, SEGMENT2) are not detailed in the provided metadata, they are defined by the flexfield configuration and stored within this table. Additional standard columns typical of such flexfield tables include ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE for controlling valid combinations, and columns for tracking creation and last update details (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

The primary use case is the creation and maintenance of valid personal analysis codes, which are then assigned to persons or job requirements. Common operational activities include querying for active codes or validating a specific segment combination before assignment. For reporting, the table is frequently joined to transactional data to decode the ANALYSIS_CRITERIA_ID into meaningful segment descriptions.

• Retrieving all active personal analysis codes: SELECT ANALYSIS_CRITERIA_ID FROM PER_ANALYSIS_CRITERIA WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE+1) AND ENABLED_FLAG = 'Y';
• Joining to person assignments to report on analysis criteria: SELECT ppf.full_name, pac.analysis_criteria_id FROM per_all_people_f ppf, per_person_analyses ppa, per_analysis_criteria pac WHERE ppa.person_id = ppf.person_id AND ppa.analysis_criteria_id = pac.analysis_criteria_id;

Related Objects

As indicated by the foreign key relationships, PER_ANALYSIS_CRITERIA is referenced by several key transactional tables. PER_PERSON_ANALYSES links the analysis criteria to a specific person. PER_JOB_REQUIREMENTS and PQH_TXN_JOB_REQUIREMENTS use it to define analysis criteria needed for a job. The PER_MM_JOB_REQUIREMENTS table (related to mass maintenance) references it twice for both the original and new analysis criteria values. These relationships underscore the table's integral role in both person-centric analysis and position/job requirement management within the HR lifecycle.