Search Results per_person_analyses

Overview

The PER_PERSON_ANALYSES table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for storing "special information types" associated with a person. In the context of Oracle HRMS, this table is instrumental in managing flexible, user-defined data attributes that extend the standard person record. It enables organizations to capture and maintain supplementary analytical or demographic information about employees, applicants, or other person types that is not covered by the core HR tables. Its role is to provide a structured yet customizable framework for person-related data analysis and reporting.

Key Information Stored

The table's structure is designed to link a person with a specific type of analysis criterion and its corresponding value. The primary key, PERSON_ANALYSIS_ID, uniquely identifies each record. Two critical foreign key columns define the record's context: ANALYSIS_CRITERIA_ID, which links to the PER_ANALYSIS_CRITERIA table to identify the type of information being stored (e.g., language proficiency, membership details, or custom criteria), and BUSINESS_GROUP_ID, which links to HR_ALL_ORGANIZATION_UNITS to enforce data security and partitioning by business group. Other essential columns typically include PERSON_ID (linking to PER_ALL_PEOPLE_F), a value or ID column for the specific analysis data, effective start and end dates for tracking historical changes, and a segment for the associated organization or location if applicable.

Common Use Cases and Queries

A primary use case is generating reports on employee qualifications, memberships, or other supplemental data. For instance, an organization can query all employees with a specific certification or language skill. A common SQL pattern involves joining PER_PERSON_ANALYSES to person and analysis criteria tables to make the data meaningful.

• Sample Query: Retrieving active employee language proficiencies.
  SELECT ppf.full_name, pac.analysis_criteria_type, ppa.segment1
FROM per_person_analyses ppa,
per_all_people_f ppf,
per_analysis_criteria pac
WHERE ppa.person_id = ppf.person_id
AND ppa.analysis_criteria_id = pac.analysis_criteria_id
AND pac.analysis_criteria_type = 'LANGUAGE'
AND SYSDATE BETWEEN ppf.effective_start_date AND ppf.effective_end_date
AND SYSDATE BETWEEN ppa.effective_start_date AND ppa.effective_end_date;
• Another critical use case is data validation and integrity checks during data migrations or integrations, ensuring analysis records correspond to valid people and criteria within the correct business group.

Related Objects

PER_PERSON_ANALYSES has defined relationships with several key HR tables, as documented in the provided metadata. The primary and foreign keys establish critical data integrity links.

• Primary Key: PER_PERSON_ANALYSES_PK on PERSON_ANALYSIS_ID.
• Foreign Key Relationships:
  • HR_ALL_ORGANIZATION_UNITS: The BUSINESS_GROUP_ID column in PER_PERSON_ANALYSES references this table, tying each analysis record to a specific business group for security.
  • PER_ANALYSIS_CRITERIA: The ANALYSIS_CRITERIA_ID column in PER_PERSON_ANALYSES references this table, defining the type of special information being stored.
• Implied Key Relationships: While not listed in the provided excerpt, standard implementation implies a foreign key to PER_ALL_PEOPLE_F on PERSON_ID. The table is also central to various HR APIs and is commonly accessed through dedicated person analysis views for reporting purposes.