Search Results per_mm_job_requirements




Overview
Explore in AI Chat

Overview

The PER_MM_JOB_REQUIREMENTS table is a core transactional data object within the Oracle E-Business Suite Human Resources (HR) module, specifically for versions 12.1.1 and 12.2.2. As documented, its primary function is to hold data related to the transfer of position requirements to a newly created position. This table operates as a supporting entity in the context of mass move operations, which are large-scale organizational restructuring or position management activities. It serves as a critical junction table, linking the master mass move transaction record to the specific analysis criteria (job requirements) being transferred, thereby ensuring that competency, skill, and other position-specific prerequisites are accurately replicated during the creation of new positions.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships, which dictate the essential data it stores. The primary key is a composite of MASS_MOVE_ID and ANALYSIS_CRITERIA_ID, ensuring a unique record for each requirement being moved in a specific transaction. The key columns are:

  • MASS_MOVE_ID: References the master transaction in the PER_MASS_MOVES table, identifying the specific mass move operation.
  • ANALYSIS_CRITERIA_ID: References the original position requirement (analysis criteria) in the PER_ANALYSIS_CRITERIA table that is being transferred.
  • NEW_ANALYSIS_CRITERIA_ID: References the newly created analysis criteria record in the PER_ANALYSIS_CRITERIA table, which is the copy of the original requirement now associated with the new position.

This design allows the system to maintain a complete audit trail of the requirement transfer process.

Common Use Cases and Queries

The primary use case is reporting and auditing mass position creation activities. For instance, an HR analyst may need to verify all job requirements that were copied during a specific organizational restructuring event. A typical query would join PER_MM_JOB_REQUIREMENTS with PER_MASS_MOVES to get transaction details and with PER_ANALYSIS_CRITERIA twice (via aliases) to retrieve both the source and target requirement descriptions.

Sample SQL Pattern:
SELECT mmv.MOVE_NAME, ac_old.NAME AS OLD_REQUIREMENT, ac_new.NAME AS NEW_REQUIREMENT
FROM HR.PER_MM_JOB_REQUIREMENTS mmjr
JOIN HR.PER_MASS_MOVES mmv ON mmjr.MASS_MOVE_ID = mmv.MASS_MOVE_ID
JOIN HR.PER_ANALYSIS_CRITERIA ac_old ON mmjr.ANALYSIS_CRITERIA_ID = ac_old.ANALYSIS_CRITERIA_ID
JOIN HR.PER_ANALYSIS_CRITERIA ac_new ON mmjr.NEW_ANALYSIS_CRITERIA_ID = ac_new.ANALYSIS_CRITERIA_ID
WHERE mmv.MASS_MOVE_ID = :p_move_id;
This query provides a clear mapping of requirements transferred for a given mass move.

Related Objects

PER_MM_JOB_REQUIREMENTS is centrally connected to two other key HR tables via foreign key constraints, as documented in the ETRM metadata:

  • PER_MASS_MOVES: The parent table for all mass move transactions. The relationship is defined by PER_MM_JOB_REQUIREMENTS.MASS_MOVE_ID referencing PER_MASS_MOVES.MASS_MOVE_ID.
  • PER_ANALYSIS_CRITERIA: The master table for job analysis and position requirements. PER_MM_JOB_REQUIREMENTS has two distinct foreign keys to this table:
    • PER_MM_JOB_REQUIREMENTS.ANALYSIS_CRITERIA_ID references PER_ANALYSIS_CRITERIA.ANALYSIS_CRITERIA_ID (the source requirement).
    • PER_MM_JOB_REQUIREMENTS.NEW_ANALYSIS_CRITERIA_ID references PER_ANALYSIS_CRITERIA.ANALYSIS_CRITERIA_ID (the newly created requirement copy).

These relationships are fundamental to the integrity of the mass position requirement transfer process.