Search Results vacancy_in_activity

Overview

PER_APPLICANT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a general-purpose (OTHER) API rather than a formally published public API. Its principal responsibility is to encapsulate the business logic associated with applicants and their relationship to vacancies, recruitment activities, and subsequent assignment records within Oracle Human Resources (Oracle HRMS). The package forms a bridging layer between the recruiter-facing applications data model and the downstream assignment, budget, and letter-generation subsystems.

Because it is vendor-internal, PER_APPLICANT_PKG is not intended for direct invocation by customer extensions. It is consumed by higher-level public APIs and internal packages, most notably HR_APPLICANT_API, HR_ASSIGNMENT_API, HR_ASSIGNMENT_INTERNAL, PER_APP_ASG_PKG, PER_HR_ASG_PKG, PER_PEOPLE9_PKG, PER_PEOPLE_V3, PER_BULK_APP_ASG_CHANGE_PKG, and PER_VACANCIES_PKG. In total, the package is referenced by nine other packages and depends only on the SYS STANDARD package at the schema level.

Key Procedures and Functions

The documented interface comprises twenty-two procedures and functions covering row maintenance, validation, vacancy handling, and defaulting logic:

• INSERT_ROW and LOCK_ROW — maintain the persistent applicant record and provide row-level locking for concurrent updates.
• PRE_UPDATE and UPDATE_GROUP — support the update path, including column group processing.
• GET_DB_DEFAULT_VALUES, CREATE_DEFAULT_BUDGET_VALUES, and GET_LOCATION_CODE — return defaulted column values from the database, including budget value defaults and location derivation.
• GET_VACANCY_DETAILS and SET_VAC_FROM_REC_ACT — retrieve vacancy attributes and derive the vacancy from a recruitment activity.
• VACANCY_IN_ACTIVITY and UNIQ_VAC_FOR_REC_ACT — validate that a vacancy belongs to a recruitment activity and enforce uniqueness of the vacancy-to-activity relationship.
• CHK_JOB_ORG_POS_COMB — validate the job, organization, and position combination.
• CHECK_APL_NUM_UNIQUE — enforce uniqueness of the applicant number.
• CHECK_DELETE_ALLOWED — determine whether deletion of the applicant record is permissible.
• EXISTS_VAL_GRD_FOR_POS_AND_JOB — test for a valid grade applicable to the position and job.
• CHECK_FOR_LETTER_REQUESTS — verify outstanding letter requests associated with the applicant.
• GET_TERRITORY_SHORT_NAME and GET_STYLE_NAME — resolve descriptive name attributes used in recruitment display logic.

Tables Accessed

The package reads and writes through APPS synonyms. Applicant and person data is handled via PER_APPLICATIONS, PER_ADDRESSES, and PER_ALL_PEOPLE_F; vacancy and recruitment data through PER_ALL_VACANCIES. Assignment-related budget and status processing uses PER_ASSIGNMENT_BUDGET_VALUES_F, PER_ASSIGNMENT_BUDGET_VALUES_S, PER_ASSIGNMENT_STATUS_TYPES with its _TL translation table, PER_ASS_STATUS_TYPE_AMENDS and PER_ASS_STATUS_TYPE_AMENDS_TL. Organization and group context is supplied by HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL together with PAY_PEOPLE_GROUPS. Letter workflow checks draw on PER_LETTER_GEN_STATUSES and PER_LETTER_REQUESTS.

Usage Notes

PER_APPLICANT_PKG is invoked indirectly. Candidate entry and vacancy screens in Oracle HRMS, and concurrent processes that transform applicants into assignments, call the referencing public APIs, which in turn execute this package's validation and defaulting routines. Custom code should never call PER_APPLICANT_PKG directly; the supported integration points are HR_APPLICANT_API and the assignment APIs. Because the package performs row locking and uniqueness checks, callers must supply validated applicant numbers and must respect the locking order established by the parent APIs to avoid contention on PER_APPLICATIONS and PER_ALL_VACANCIES.