Results for “per_analysis_criteria”

50+ results




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

Overview

PER_ANALYSIS_CRITERIA is the flexfield combination table for the Personal Analysis key flexfield (KFF) within the Oracle E-Business Suite Human Resources (PER) module. The table resides in the HR schema and is validated in both Oracle EBS 12.1.1 and 12.2.2. It stores the valid, compiled combinations of the Personal Analysis key flexfield, which is the mechanism Oracle HRMS uses to define the competency and qualification profile structure attached to jobs, positions, and people. Every meaningful criterion used to evaluate whether a person meets the requirements of a job or position ultimately resolves to a row in this table.

Because each combination is uniquely identified by its surrogate primary key, ANALYSIS_CRITERIA_ID, and is referenced by many dependent transactional and definitional tables through foreign keys, the heuristic Data Vault classification for this object is hub-leaning. Analysts modeling this data for a warehouse should consider treating ANALYSIS_CRITERIA_ID as a hub business key, with the segment values and descriptive attributes carried in a satellite.

Key Information Stored

The table holds 46 documented columns. The most significant are:

Common Use Cases and Queries

Typical uses include reporting the complete set of valid analysis criteria, validating which criteria are currently enabled, and resolving the foreign-key references held by job requirements, person analyses, and transaction staging rows. A common pattern joins the flexfield combination to its descriptive context:

  • Listing enabled combinations within an effective range: SELECT analysis_criteria_id, segment1, segment2, start_date_active, end_date_active FROM per_analysis_criteria WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Resolving job requirements against criteria: join PER_JOB_REQUIREMENTS to PER_ANALYSIS_CRITERIA on ANALYSIS_CRITERIA_ID to display the criterion text attached to each job.
  • Reconciling person-level analyses: join PER_PERSON_ANALYSES on ANALYSIS_CRITERIA_ID to report which criteria have been evaluated for an employee.
  • Auditing concurrent load activity by filtering on REQUEST_ID or PROGRAM_ID.

Because the personal analysis KFF is resolved by Oracle HRMS flexfield APIs rather than direct inserts, reporting should treat this table as read-only reference data.

Related Objects

The documented foreign keys identify the principal dependent objects:

  • PER_JOB_REQUIREMENTS (ANALYSIS_CRITERIA_ID) — criteria required for a job.
  • PQH_TXN_JOB_REQUIREMENTS (ANALYSIS_CRITERIA_ID) — the transaction-layer staging copy used by the HRMS workflow and position-management processes; this is the object most closely associated with the user's search term.
  • PQH_TJR_SHADOW (ANALYSIS_CRITERIA_ID) — the shadow table paired with PQH_TXN_JOB_REQUIREMENTS.
  • PER_MM_JOB_REQUIREMENTS (ANALYSIS_CRITERIA_ID and NEW_ANALYSIS_CRITERIA_ID) — supporting the HRMS mass-update/merge processing of job requirements.
  • PER_PERSON_ANALYSES (ANALYSIS_CRITERIA_ID) — person-level analysis records.
  • OTA_SKILL_PROVISIONS (ANALYSIS_CRITERIA_ID) — links learning-management skill provisioning to HR analysis criteria.

Taken together, these references confirm PER_ANALYSIS_CRITERIA as the central reference table for job-requirement and competency analysis across the PER and PQH schemas.