Results for “date_evaluated”

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

Overview

PER_JOB_EVALUATIONS is an Oracle E-Business Suite table owned by the HR schema within the PER (Human Resources) product family. It stores the results of formal job evaluation exercises, capturing the outcome of scoring a job or a position against an evaluation system or methodology. Each row represents one evaluation event recorded against a specific job, a specific position, or both, together with the date on which the evaluation was performed, the measurement scale applied, and the overall score awarded. The table therefore acts as the historical record of how jobs and positions have been rated over time, rather than as a definitional table for the jobs and positions themselves.

Applying Data Vault modeling heuristics to the documented foreign-key structure, PER_JOB_EVALUATIONS is best characterized as a link entity. It resolves relationships between a business group (HR_ALL_ORGANIZATION_UNITS), a job (PER_JOBS), and a position (PER_ALL_POSITIONS), while its descriptive measurements — date evaluated, score, and system — behave as link-level attributes or as the payload of an associated satellite. This classification is a modeling suggestion derived from the FK topology; in the operational EBS schema the table functions as a standard transactional child of the HR job and position entities.

Key Information Stored

The table is documented in ETRM 12.2.2 as having 39 columns. The most significant columns are as follows.

• JOB_EVALUATION_ID — the surrogate primary key, enforced by the unique index PER_JOB_EVALUATIONS_PK. It is the single documented business-key candidate and the join key for downstream references.
• BUSINESS_GROUP_ID — the enterprise or business group that owns the evaluation record; a foreign key to HR_ALL_ORGANIZATION_UNITS and the primary partitioning dimension in multi-organization HR implementations.
• JOB_ID — the evaluated job, foreign key to PER_JOBS.
• POSITION_ID — the evaluated position, foreign key to PER_ALL_POSITIONS. A given row may reference a job, a position, or both, depending on the granularity of the evaluation.
• DATE_EVALUATED — the effective date of the evaluation, supporting point-in-time comparison of scores.
• OVERALL_SCORE — the aggregate rating produced by the evaluation, used for grading, banding, or pay-equity analysis.
• MEASURED_IN — the unit or scale in which the score is expressed.
• SYSTEM — identifies the evaluation system or methodology applied (for example, point-factor or factor-comparison approaches).
• COMMENTS — free-text notes describing the evaluation outcome or methodology rationale.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and request context, indicating whether the row was created or refreshed by a batch process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns identifying the user and timestamp of creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — the standard EBS descriptive flexfield columns, available for customer-defined extensions.

Common Use Cases and Queries

The primary reporting requirement is to retrieve the latest evaluation for a job or position, typically filtering on the most recent DATE_EVALUATED within a business group. A representative pattern joins the evaluation table to PER_JOBS and PER_ALL_POSITIONS:

• Job grading and salary-structure review: correlate OVERALL_SCORE with grade and pay range definitions to validate internal equity across a business group.
• Position audit: identify positions evaluated under a given SYSTEM, or positions with no evaluation record within a defined period, using an outer join to PER_ALL_POSITIONS.
• Historical trending: compare successive evaluations for the same JOB_ID ordered by DATE_EVALUATED to track re-scoring following restructuring.
• Interface reconciliation: use REQUEST_ID and PROGRAM_ID to confirm which concurrent program populated a set of evaluation rows.
• Flexfield reporting: extract ATTRIBUTE_CATEGORY and ATTRIBUTE1-N for any customer-defined evaluation criteria.

Because scoring conventions vary by organization, queries should always scope on BUSINESS_GROUP_ID and restrict by DATE_EVALUATED to avoid mixing incompatible evaluation systems.

Related Objects

• PER_JOBS — joined via PER_JOB_EVALUATIONS.JOB_ID; the parent definition of the evaluated job.
• PER_ALL_POSITIONS — joined via PER_JOB_EVALUATIONS.POSITION_ID; the parent definition of the evaluated position.
• HR_ALL_ORGANIZATION_UNITS — joined via PER_JOB_EVALUATIONS.BUSINESS_GROUP_ID; supplies the owning enterprise context.
• PER_JOB_EVALUATIONS_PK — the unique index on JOB_EVALUATION_ID that enforces row identity and supports child references.
• PER_JOBS_K / PER_JOBS_F and the PER_JOBS API surface — the standard interfaces through which job metadata referenced by these evaluations is maintained.
• FND_CONCURRENT_REQUESTS — related via REQUEST_ID for traceability of batch-created evaluation records.
• Downstream compensation and grade structures that consume OVERALL_SCORE for banding decisions are dependent reporting consumers rather than enforced foreign-key children.