Search Results per_job_extra_info




Overview
Explore in AI Chat

Overview

PER_JOB_EXTRA_INFO is a Human Resources (PER) module table in the HR schema that stores descriptive flexfield (DFF) and extra information associated with a job definition in Oracle E-Business Suite. It functions as the child of PER_JOBS and captures the extended, user-defined attributes configured against a job through the Job Extra Information flexfield framework, rather than the core descriptive columns (name, code, dates) held on the parent job row. Each row represents one "information type" instance for a specific job, allowing multiple extra-information records per job, differentiated by INFORMATION_TYPE.

In Oracle EBS 12.1.1 and 12.2.2 the table is present with an identical documented structure of 65 columns and is maintained under the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER for optimistic locking introduced by the OAF-based HTML user interface. From a Data Vault modeling perspective, the metadata supports classifying this object as a link, since its primary value is the association between a job (PER_JOBS) and an extra-information type (PER_JOB_INFO_TYPES), enriched by context attributes.

Key Information Stored

The only documented unique index is the primary key on JOB_EXTRA_INFO_ID; no separate business-key unique index (for example on JOB_ID plus INFORMATION_TYPE) is recorded in the metadata, though the pairing of those columns is the practical determinant of a job's extra-information instance.

Common Use Cases and Queries

Typical usage resolves the DFF values stored against a job for reporting, integration extracts, and validation of flexfield setup. A representative join follows:

  • Listing all extra information for a job: SELECT j.JOB_ID, j.NAME, e.INFORMATION_TYPE, e.JEI_INFORMATION_CATEGORY, e.JEI_INFORMATION1 FROM PER_JOBS j, PER_JOB_EXTRA_INFO e WHERE j.JOB_ID = e.JOB_ID;
  • Resolving the information-type definition: join INFORMATION_TYPE to PER_JOB_INFO_TYPES to obtain the type's name and context.
  • Auditing flexfield population: query rows where JEI_INFORMATION_CATEGORY is null or where specific numbered segments are populated, to detect incomplete or misconfigured data.
  • Integration extraction: select on LAST_UPDATE_DATE and PROGRAM_UPDATE_DATE to drive incremental feeds of job extra information into downstream warehouses.
  • Concurrency diagnostics: inspect OBJECT_VERSION_NUMBER when OAF self-service job maintenance reports stale-record conflicts.

Reporting tools such as Oracle BI Publisher and the HRMS Extract can consume these columns directly; because the payload is generic, segment meanings must always be resolved against the flexfield configuration for the relevant information type.

Related Objects

  • PER_JOBS — parent entity; joined via PER_JOB_EXTRA_INFO.JOB_ID = PER_JOBS.JOB_ID.
  • PER_JOB_INFO_TYPES — defines each information type; joined via PER_JOB_EXTRA_INFO.INFORMATION_TYPE = PER_JOB_INFO_TYPES.INFORMATION_TYPE.
  • PER_JOB_EXTRA_INFO_PK — the primary key constraint over JOB_EXTRA_INFO_ID controlling uniqueness.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — supply the valid values referenced by the JEI_INFORMATION and JEI_ATTRIBUTE flexfield segments.
  • FND_DESCR_FLEX_COLUMN_USAGES — configuration source describing which segments are enabled for the Job Extra Information flexfield.
  • FND_CONCURRENT_REQUESTS — correlates REQUEST_ID and PROGRAM_ID audit columns to the concurrent request that modified the row.