Search Results chk_dt_to_in_req_dates

Overview

APPS.PER_VACANCIES_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Applications schema (APPS) that encapsulates the core business logic for creating, validating, and maintaining vacancy records within Oracle Human Resources. Vacancies represent approved, unfilled positions or headcount that an enterprise intends to recruit against, and they form the link between requisitions, recruitment activities, budgets, and actual assignments. The package is classified in the ETRM repository as an OTHER API, meaning it is an internal implementation package rather than a formally published public interface, although its procedures are callable from forms and custom code. It operates principally against the PER_VACANCIES entity and its secured synonym PER_ALL_VACANCIES, and it is validated and status VALID in both 12.1.1 and 12.2.2. In the ETRM dependency listing the package references APPS.PER_VACANCIES, SYS.STANDARD, and the APPS schema itself, and it is referenced by one other package, confirming a moderate but contained dependency footprint.

Key Procedures and Functions

The ETRM metadata documents twenty-eight procedures and functions. The validation routines form the largest group and guard the integrity of vacancy data entered through the Maintain Vacancies form. CHECK_REFERENCES verifies that dependent records exist before a vacancy is deleted or altered. CHECK_UNIQUE_NAME enforces uniqueness of the vacancy name. CHK_APPL_EXISTS confirms the existence of applicants associated with a vacancy. CHECK_IN_REQ_DATES and CHK_DT_TO_IN_REQ_DATES validate that vacancy date ranges fall within the corresponding requisition dates, while DATE_FROM_UPD_VALIDATION checks the date-from value on update. A family of row-level update checks — D_FROM_UPDT_REC_ACT_CHK, D_FROM_UPDT_ORG_CHK, D_FROM_UPDT_POS_CHK, D_FROM_UPDT_GRP_CHK, D_FROM_UPDT_JOB_CHK, D_FROM_UPDT_GRD_CHK, D_FROM_UPDT_LOC_CHK, and D_FROM_UPDT_PERSON — validates date-from changes against recruitment activity, organization, position, people group, job, grade, location, and person respectively. Together these enforce that a vacancy's effective dates cannot precede the reference data they depend upon.

Tables Accessed

The package reads and writes PER_ALL_VACANCIES and PER_VACANCIES_S, the base and secured views of the vacancy entity, alongside HR_ALL_POSITIONS_F for position definitions, PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F for person and assignment context, and PER_ASSIGNMENT_STATUS_TYPES and PER_ASSIGNMENT_BUDGET_VALUES_F for assignment status and budget value validation. Grade, location, and shared lookup validation draws on PER_GRADES and PER_SHARED_TYPES. Recruitment-specific validation depends on PER_REQUISITIONS, PER_RECRUITMENT_ACTIVITIES, and PER_RECRUITMENT_ACTIVITY_FOR. GET_PEOPLE_GROUP reads PAY_PEOPLE_GROUPS to resolve security group context. PER_TIME_PERIODS supplies date validation against payroll periods, and PQH_BUDGETS supports budget linkage for vacancy funding. INSERT_ROW and LOCK_ROW perform the physical insert and pessimistic row locking on the vacancy table, while B_COUNTER and FOLDER_HIRES and FOLDER_CURRENT support folder-based form navigation and hire counting.

Usage Notes

PER_VACANCIES_PKG is invoked primarily by the Maintain Vacancies and Recruitment Activity forms in Oracle HRMS, where it supplies field-level validation, folder behavior, and row locking. Because it is classified as OTHER rather than a published API, Oracle does not guarantee backward compatibility for custom callers, and direct invocation should be reserved for controlled extensions where no supported alternative exists. When integrating with vacancy data programmatically, the recommended surface remains the documented public APIs (for example PER_VACANCIES_API where available), with this package treated as internal form logic. Custom code that does call INSERT_ROW or the validation routines must supply a valid people group and session context, since GET_PEOPLE_GROUP and D_FROM_UPDT_GRP_CHK depend on it. The row-level D_FROM_UPDT checks fire on effective-date changes and can raise validation errors, so callers should handle them explicitly rather than assuming silent success.