Results for “per_job_definitions”

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

Overview

PER_JOB_DEFINITIONS is the HR schema table that stores Job key flexfield combinations within Oracle E-Business Suite 12.1.1 and 12.2.2. In the PER (Human Resources) module, jobs are defined through the Job key flexfield (KFF), and this table materializes the resulting combination of segment values that uniquely describe a job. As the description in the ETRM metadata states, PER_JOB_DEFINITIONS is the "Job key flexfield combinations table." It is owned by the HR schema and is marked VALID in the ETRM documentation set.

The table carries 45 documented columns in the 12.2.2 physical schema. Its primary key, PER_JOB_DEFINITIONS_PK, is defined on the single column JOB_DEFINITION_ID, which is the surrogate identifier for each job definition row. Based on the foreign-key structure, the heuristic Data Vault classification is hub-leaning. Interpreted as a modeling suggestion, this indicates that PER_JOB_DEFINITIONS functions primarily as a hub of business keys — each row representing a distinct job definition — with dependent attributes carried alongside rather than distributed across satellite structures.

Key Information Stored

The most significant column is JOB_DEFINITION_ID, the surrogate primary key and the value referenced by all dependent tables. The remaining columns fall into several functional groups among the 45 documented:

• Concurrent program tracking: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• Flexfield identity: ID_FLEX_NUM, which ties the combination to a specific key flexfield structure and instance.
• Definition status and dating: SUMMARY_FLAG, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE, establishing whether a job definition is a summary (parent) combination and when it is active.
• Flexfield segment values: SEGMENT1 through SEGMENT30. These store the actual concatenated segment values that form the job key flexfield combination. Because the KFF structure is configurable, the number of populated segments varies by implementation.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE.

The unique index PER_JOB_DEFINITIONS_PK on JOB_DEFINITION_ID is the documented business-key candidate. The segment columns collectively also constitute the natural business key of the flexfield combination, though no separate unique index on them is documented.

Common Use Cases and Queries

Typical use cases include resolving a job name or flexfield concatenation to its internal identifier, and validating which job definitions are active for a given date range. A representative lookup joins the flexfield segments to the standard jobs table:

• Resolve a job definition identifier: SELECT JOB_DEFINITION_ID, SEGMENT1, SEGMENT2, ENABLED_FLAG FROM PER_JOB_DEFINITIONS WHERE JOB_DEFINITION_ID = :p_id;
• List active job definitions by segment values: SELECT SEGMENT1, SEGMENT2, ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE FROM PER_JOB_DEFINITIONS WHERE ENABLED_FLAG = 'Y' AND TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Join to PER_JOBS to attach job names to definitions: SELECT pj.NAME, pjd.SEGMENT1, pjd.SEGMENT2 FROM PER_JOBS pj JOIN PER_JOB_DEFINITIONS pjd ON pj.JOB_DEFINITION_ID = pjd.JOB_DEFINITION_ID;
• Distinguish summary combinations used to build KFF hierarchy: filter on SUMMARY_FLAG = 'Y'.

Related Objects

The documented foreign-key relationships identify the following significant objects that depend on PER_JOB_DEFINITIONS:

• PER_JOBS — references PER_JOB_DEFINITIONS through the foreign key column PER_JOBS.JOB_DEFINITION_ID. This is the primary operational child object, linking each job to its flexfield combination.
• PER_EMPDIR_JOBS — references the table via JOB_DEFINITION_ID, supporting the employee directory jobs listing.
• EDW_HR_JOB_JOBS_LSTG — the Enterprise Data Warehouse staging table referencing JOB_DEFINITION_ID.
• EDW_HR_JOB_JOBS_LTC — the corresponding EDW change-capture table, also joining on JOB_DEFINITION_ID.

These relationships confirm the hub-leaning classification: PER_JOB_DEFINITIONS is the central referenced entity, while the four objects above act as consumers that resolve job definitions for operational and warehouse reporting purposes.