Search Results per_previous_jobs




Overview

PER_PREVIOUS_JOBS is a core Human Resources table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, owned by the HR schema and delivered under the PER (Human Resources) product. As its description states, the table is used to store previous jobs — the employment history that a worker records prior to joining the enterprise. Each row represents a single prior-job record and captures the employer, the period of employment, the job title, and a large set of descriptive flexfield and information flexfield attributes used to persist customer-specific data.

The table functions as a dependent detail object under a worker or applicant record. Its foreign key to PER_PREVIOUS_EMPLOYERS through PREVIOUS_EMPLOYER_ID confirms that employer data is normalized separately, so a single employer can be referenced by multiple previous-job rows. From a heuristic Data Vault perspective, the mined FK structure classifies this table as hub-leaning: the surrogate key PREVIOUS_JOB_ID acts as a stable hub identity for the previous-job entity, while the remaining descriptive columns behave in a satellite-like fashion. This classification is a modeling suggestion rather than a documented Oracle design statement.

Key Information Stored

The physical schema documented for 12.2.2 contains 79 columns. The most significant are:

Common Use Cases and Queries

The table is typically queried during hiring, applicant screening, and employee data verification. Because it stores a full external employment history, it supports candidate evaluation reports, tenure analysis, and background-verification extracts.

  • Retrieving all previous jobs for a given employer: SELECT pj.previous_job_id, pj.job_name, pj.start_date, pj.end_date FROM per_previous_jobs pj WHERE pj.previous_employer_id = :employer_id.
  • Duration reporting using the stored period measures: SELECT job_name, period_years, period_months FROM per_previous_jobs WHERE period_years > 5.
  • Joining to employer detail for consolidated history: SELECT pe.employer_name, pj.job_name, pj.start_date FROM per_previous_jobs pj, per_previous_employers pe WHERE pj.previous_employer_id = pe.previous_employer_id.
  • Extracting flexfield data via PJO_ATTRIBUTE_CATEGORY and the PJO_INFORMATION segments for localized or legislative reporting.

Reporting layers frequently expose this table for HR analytics on external experience, and interfaces use it when loading applicant or new-hire data from external sources.

Related Objects

  • PER_PREVIOUS_EMPLOYERS — parent reference table; joined via PER_PREVIOUS_JOBS.PREVIOUS_EMPLOYER_ID = PER_PREVIOUS_EMPLOYERS.PREVIOUS_EMPLOYER_ID.
  • PER_PREV_JOB_EXTRA_INFO — dependent child table referencing PREVIOUS_JOB_ID, holding supplementary job details.
  • PER_PREVIOUS_JOB_USAGES — dependent table also referencing PREVIOUS_JOB_ID, tracking how previous-job records are used.
  • Human Resources application forms and APIs that maintain prior employment data during hire and applicant flows, which read and write this table through the PER business logic layer.
  • HR reporting and analytics views built on the HR schema that surface previous-job history alongside person and assignment data.

All references above are grounded in the documented FK relationships and physical schema; additional dependent objects may exist beyond the excerpted ETRM metadata.