Search Results per_job_requirements




Overview
Explore in AI Chat

Overview

The PER_JOB_REQUIREMENTS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module. It serves as the central repository for defining and storing the specific requirements associated with jobs or positions within an organization. These requirements are essential for talent management processes, enabling the systematic definition of the necessary skills, qualifications, experience, and training needed for a particular role. The table's primary role is to establish a structured link between a job or position and the competency criteria required to perform it, forming a foundational element for recruitment, succession planning, and competency gap analysis.

Key Information Stored

The table's structure is designed to capture the relationship between a requirement and the organizational role it defines. The primary key is JOB_REQUIREMENT_ID, a unique system-generated identifier for each requirement record. The table links to other critical HR entities via foreign keys: JOB_ID references PER_JOBS, and POSITION_ID references PER_ALL_POSITIONS, allowing requirements to be attached to either a generic job or a specific position. The BUSINESS_GROUP_ID column links to HR_ALL_ORGANIZATION_UNITS, securing data by the organization's business group. The most significant column is ANALYSIS_CRITERIA_ID, which references PER_ANALYSIS_CRITERIA. This foreign key establishes the link to the specific competency, skill, qualification, or other predefined analysis criterion that constitutes the requirement for the job or position.

Common Use Cases and Queries

A primary use case is generating reports to analyze the competency profile of a job for recruitment or development purposes. For example, a query might list all requirements for a specific job to create a job description or advertisement. Another critical use is in gap analysis, where the requirements stored in PER_JOB_REQUIREMENTS are compared against an employee's held competencies (often in PER_PERSON_ANALYSES) to identify development needs. A common reporting pattern involves joining to the PER_JOBS and PER_ANALYSIS_CRITERIA tables to present meaningful descriptions.

  • Sample Query: SELECT pj.NAME AS job_name, pac.NAME AS requirement_name FROM hr.per_job_requirements pjr JOIN hr.per_jobs pj ON pjr.job_id = pj.job_id JOIN hr.per_analysis_criteria pac ON pjr.analysis_criteria_id = pac.analysis_criteria_id WHERE pj.job_id = 123;

Related Objects

PER_JOB_REQUIREMENTS is a central table with several key dependencies. It is primarily referenced by the transaction table PQH_TXN_JOB_REQUIREMENTS, which likely tracks changes or approvals to these requirements. Its integrity is defined by foreign key relationships to major HR master tables: PER_JOBS (for jobs), PER_ALL_POSITIONS (for positions), HR_ALL_ORGANIZATION_UNITS (for business group security), and most importantly, PER_ANALYSIS_CRITERIA (for the actual competency definition). For reporting and application logic, it is typically accessed via public APIs or views rather than directly, to maintain data integrity and leverage business logic within the HRMS product.