Results for “per_person_analyses”

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

Overview

PER_PERSON_ANALYSES is the Oracle E-Business Suite Human Resources (PER) table that stores special information types (SITs) recorded against a person. Each row represents a single analysis entry for an employee or contingent worker, qualified by an analysis criterion that defines what type of special information is being captured. The table is owned by the HR schema and resides in the PER product module, holding 40 documented columns in the ETRM 12.2.2 physical schema. It is a VALID object in both 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata heuristic classifies PER_PERSON_ANALYSES as a link. This is consistent with its structure: the table associates a person (via PERSON_ID and PARTY_ID) with an analysis criterion (via ANALYSIS_CRITERIA_ID), operating within a business group. Treat this classification as a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The most significant columns include:

• PERSON_ANALYSIS_ID — the surrogate primary key, enforced by PER_PERSON_ANALYSES_PK. This is the only unique index on a business column; no separate business-key unique index is documented, aside from the system-managed LOB index SYS_IL0000043521C00040$$.
• PERSON_ID / PARTY_ID — the person and party to whom the analysis record belongs.
• ANALYSIS_CRITERIA_ID — the special information type definition being recorded; foreign key to PER_ANALYSIS_CRITERIA.
• BUSINESS_GROUP_ID — the legislative or business group context; foreign key to HR_ALL_ORGANIZATION_UNITS.
• DATE_FROM / DATE_TO — the effective dating range for the analysis entry, supporting date-tracked history.
• ID_FLEX_NUM — the descriptive flexfield structure number for the SIT's context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and program audit columns identifying the batch process that created or last updated the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the descriptive flexfield segments capturing SIT-specific data for each analysis criterion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard WHO audit and optimistic-locking columns used across EBS.
• COMMENTS — free-text remarks associated with the analysis record.

Common Use Cases and Queries

Typical scenarios include reporting on employee special information such as qualifications, licenses, memberships, or health-related SITs, and joining analysis data to the analysis criteria to resolve the SIT name. A representative pattern:

• Join PER_PERSON_ANALYSES to PER_ANALYSIS_CRITERIA on ANALYSIS_CRITERIA_ID to retrieve the criterion name alongside each person's analysis entry.
• Filter by TRUNC(SYSDATE) BETWEEN DATE_FROM AND DATE_TO to obtain current active analyses.
• Join to PER_ALL_PEOPLE_F on PERSON_ID to resolve employee name and number.
• Use ATTRIBUTE_CATEGORY plus the relevant ATTRIBUTE1–ATTRIBUTE20 columns to pivot flexfield content for a specific special information type.
• Reconcile batch-loaded records using REQUEST_ID and PROGRAM_ID against concurrent program history.

Related Objects

The documented foreign keys and the surrounding PER data model establish these key relationships:

• PER_ANALYSIS_CRITERIA — parent defining each special information type, joined on ANALYSIS_CRITERIA_ID.
• HR_ALL_ORGANIZATION_UNITS — business group definition, joined on BUSINESS_GROUP_ID.
• PER_ALL_PEOPLE_F — the person master, joined on PERSON_ID.
• HZ_PARTIES — party record for the person, joined on PARTY_ID.
• FND_CONCURRENT_REQUESTS — concurrent request detail, joined on REQUEST_ID.
• FND_APPLICATION / FND_PROGRAM — resolve PROGRAM_APPLICATION_ID and PROGRAM_ID for batch auditing.
• PER_PERSON_ANALYSES_PK — the primary key constraint governing PERSON_ANALYSIS_ID.