Search Results check_evaluation_dates




Overview

APPS.PER_JOBS_PKG is a server-side PL/SQL package within the Oracle E-Business Suite Human Resources (HRMS) module. It encapsulates the business logic required to validate, maintain, and enforce the integrity of job definitions stored in the PER_JOBS entity and its related child tables. Jobs form a foundational component of the HR data model, defining the roles to which employees and assignments are linked, and they carry effective-dated attributes including validation grades, evaluation records, and requirement mappings.

The package serves primarily as a validation and maintenance layer invoked during the creation, update, and end-dating of job records. It also handles sequence generation and flexfield structure resolution for the job key flexfield. By centralising these rules, the package ensures that any interface — whether a standard Oracle Forms screen, a concurrent program, or custom code — applies identical business constraints before committing changes to the underlying tables. The source header (pejbd01t.pkh) indicates the package has been stable since at least 2005 and is classified as a non-shipped internal API, meaning it is intended for internal HRMS use rather than as a public integration interface.

Key Procedures and Functions

  • GET_NEXT_SEQUENCE — Returns the next available job identifier, used when inserting a new job record.
  • CHECK_UNIQUE_NAME — Validates that a proposed job name is not duplicated within the same business group, preventing ambiguous job descriptions.
  • CHECK_DATE_FROM — Verifies that the specified start date for a job is valid against existing effective-dated data.
  • GET_JOB_FLEX_STRUCTURE — Resolves and returns the key flexfield structure definition associated with a given job group, supporting the descriptive flexfield configuration of jobs.
  • CHECK_ALTERED_END_DATE — Evaluates changes to a job's end date, returning flags that indicate whether the altered date affects the prior effective period's start or end boundaries.
  • UPDATE_VALID_GRADES — Propagates the new effective end date to all valid grade records associated with the job, keeping the grade-to-job relationship consistent with the job's date range.
  • DELETE_VALID_GRADES — Removes valid grade associations when a job is end-dated or deleted for the affected period.
  • CHECK_DELETE_RECORD — Determines whether a job record may be safely deleted, blocking removal where dependent data exists.
  • CHECK_EVALUATION_DATES — Validates that no job evaluation records fall outside the effective period when a user end-dates a job. The procedure requires a valid job to exist and accepts the job identifier, the job's from-date, and its to-date. If any evaluation exists beyond the proposed effective end date, the user is prevented from completing the end-dating action and a message is surfaced.

Tables Accessed

The package reads and writes PER_JOBS and its date-tracked shadow table PER_JOBS_S, the core job definition store. Validation of grades relies on PER_VALID_GRADES and PER_GRADES, while evaluation checks reference PER_JOB_EVALUATIONS. Job requirements and career path relationships are held in PER_JOB_REQUIREMENTS and PER_CAREER_PATH_ELEMENTS respectively. Assignment dependencies are verified against PER_ALL_ASSIGNMENTS_F, and position links through HR_ALL_POSITIONS_F. Budget and payroll integration is supported via PER_BUDGET_ELEMENTS and PAY_ELEMENT_LINKS_F. Role references use PER_ROLES, and dynamic SQL construction (notably for flexfield lookups) uses the DBMS_SQL built-in package.

Usage Notes

PER_JOBS_PKG is most commonly invoked indirectly through the standard HRMS Forms interface, particularly the Job form and the Job Evaluation form, which call these procedures during validation triggers. It is referenced by zero other documented packages, indicating its role is primarily as a terminal validation layer rather than a shared utility. Customisations that insert or end-date job records should replicate these validation checks — especially CHECK_EVALUATION_DATES and CHECK_UNIQUE_NAME — to avoid orphaned evaluations or duplicate job names within a business group.