Results for “pju_attribute_category”

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

Overview

The PER_PREVIOUS_JOB_USAGES_V view is a seeded, VALID database object in the APPS schema within Oracle E-Business Suite, owned by the PER (Human Resources) product module. It is a validation view defined over the PER_PREVIOUS_JOB_USAGES table and presents prior employment history for a person, enriching the raw previous-job usage records with effective-dated assignment and security context. The view resolves the previous employer, the descriptive job name, and the assignment number, and it constrains results to the effective date range relevant to the current user session through FND_SESSIONS and USERENV('SESSIONID'). Because it joins to PER_ASSIGNMENTS_F and filters by the session effective date, the view functions as a security-aware reporting and integration surface rather than a simple pass-through of the base table. It is commonly consumed by forms, concurrent programs, and custom reporting that need a person's previous job history as of a given effective date.

Underlying Base Objects

The documented base objects underlying this view are FND_SESSIONS (SYNONYM), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), PER_ASSIGNMENTS_F (VIEW), PER_PREVIOUS_EMPLOYERS (SYNONYM), PER_PREVIOUS_JOBS (SYNONYM), and PER_PREVIOUS_JOB_USAGES (SYNONYM). In the view text, PER_PREVIOUS_JOB_USAGES (PJU) is the driving table. PER_PREVIOUS_EMPLOYERS (PEM) is joined on PREVIOUS_EMPLOYER_ID, and PER_PREVIOUS_JOBS (PJO) is an outer-joined ((+)) lookup providing the descriptive JOB_NAME. PER_ASSIGNMENTS_F (ASG) supplies the effective-dated assignment and, critically, the person-to-assignment linkage. FND_SESSIONS (SES) restricts rows to those where the session effective date falls between the assignment's effective start and end dates, applying session-level date context. The HR_GENERAL and HR_SECURITY packages support HR security and effective-date resolution referenced by the underlying objects.

Key Columns

• PREVIOUS_JOB_USAGE_ID — Primary identifier of the previous job usage record.
• ASSIGNMENT_ID — The assignment to which the previous job usage is attached.
• PREVIOUS_JOB_ID — Link to the previous job definition.
• PREVIOUS_EMPLOYER_ID — Resolved via NVL(PJO.PREVIOUS_EMPLOYER_ID, PJU.PREVIOUS_EMPLOYER_ID), preferring the job's employer when available.
• D_JOB — Descriptive job name (PJO.JOB_NAME).
• START_DATE / END_DATE — Prior employment period boundaries.
• PERIOD_YEARS / PERIOD_MONTHS / PERIOD_DAYS — Computed or stored duration components of the prior employment.
• PJU_INFORMATION_CATEGORY and PJU_INFORMATION1–PJU_INFORMATION20 — Descriptive flexfield (DFF) context and segment columns; PJU_INFORMATION1 is the first DFF segment.
• PJU_ATTRIBUTE_CATEGORY and PJU_ATTRIBUTE1–PJU_ATTRIBUTE20 — Additional descriptive attribute columns.
• ASSIGNMENT_NUMBER — Exposed from PER_ASSIGNMENTS_F.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.

Common Use Cases and Queries

This view is typically used to report prior employment history for a person, resolve DFF values stored in PJU_INFORMATION1, and join previous-job data to current assignments in a security-aware manner. Because it filters on the session effective date, it is best queried from within an EBS session or by supplying a controlled effective date.

• Listing a person's previous job usages with job name and employer.
• Extracting flexfield segment values such as PJU_INFORMATION1 for integrations.
• Computing total prior service duration from period year/month/day columns.

Representative query:

SELECT assignment_id, assignment_number, d_job, previous_employer_id, start_date, end_date, period_years, period_months, period_days, pju_information_category, pju_information1 FROM apps.per_previous_job_usages_v WHERE assignment_id = :p_assignment_id;

To target the flexfield segment referenced in the search, filter on PJU_INFORMATION1 or restrict by PJU_INFORMATION_CATEGORY to isolate the relevant DFF context.