Search Results per_job_definitions_pk




Overview
Explore in AI Chat

Overview

The PER_JOB_DEFINITIONS table is a core data object within the Oracle E-Business Suite Human Resources (HR) module. It functions as the master repository for all valid combinations of the Job Key Flexfield (KFF). In Oracle EBS, a job is a critical classification structure used to categorize and manage positions and employees. The flexfield allows for the definition of a job's structure using multiple segments (e.g., Job Family, Function, Level). This table stores every unique, active combination of these segment values that has been created, thereby enforcing data integrity and providing a centralized reference for job definitions used across the HR and related modules in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary purpose is to store flexfield combinations, with its structure centered around a unique identifier for each job definition. The most critical columns include:

  • JOB_DEFINITION_ID: The primary key (PER_JOB_DEFINITIONS_PK) and unique surrogate identifier for a specific job combination.
  • SEGMENT1, SEGMENT2, ... SEGMENT: These columns store the actual values for each segment of the Job Key Flexfield as configured in the application. The number of active segments is defined by the flexfield setup.
  • ENABLED_FLAG: Typically indicates whether the job definition combination is available for use (e.g., 'Y' or 'N').
  • Additional columns for tracking, such as START_DATE_ACTIVE and END_DATE_ACTIVE, control the effective date range of the job definition, and LAST_UPDATE_DATE for auditing.

Common Use Cases and Queries

This table is fundamental for HR data validation, reporting, and integration. A primary use case is validating job assignments on employee records (PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F) against the master list of defined jobs. For reporting, it is frequently joined to translate the JOB_DEFINITION_ID into meaningful segment descriptions. A common query pattern involves joining to the descriptive flexfield views (e.g., FND_FLEX_VALUES_VL) to get the meaning of the stored segment codes. For instance, to list all active job definitions with their segment descriptions, a query would select from PER_JOB_DEFINITIONS where ENABLED_FLAG = 'Y' and SYSDATE between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, SYSDATE+1). Another critical use is during data migration or interfaces, where this table must be referenced to ensure any job information being loaded corresponds to a valid, existing JOB_DEFINITION_ID.

Related Objects

As indicated by the provided metadata, PER_JOB_DEFINITIONS has a direct and essential relationship with the PER_JOBS table, which stores specific job instances and references PER_JOB_DEFINITIONS via the foreign key column PER_JOBS.JOB_DEFINITION_ID. It is also intrinsically linked to the flexfield infrastructure tables, such as FND_FLEX_VALUE_SETS and FND_FLEX_VALUES. Key HRMS APIs, particularly those related to creating and maintaining jobs and assignments, will validate input against this table. For reporting and application logic, derived views may exist that join this table with descriptive flexfield tables to present a user-friendly description of the job combination.