Search Results get_vacancy

Overview

APPS.PER_APPLICANT_PKG is a PL/SQL package in the Oracle E-Business Suite Applications layer that centralizes the business logic governing job applicants, vacancies, applications, and the resulting assignment-level attributes generated during recruitment-to-hire processing. Although the object name references "applicant," the documented procedures demonstrate a broader scope: the package supports applicant records, vacancy validation, recruitment activity handling, default budget derivation, letter-request checks, and the derivation of working conditions for newly created assignments. In releases 12.1.1 and 12.2.2 the package is owned by APPS, is classified as an "OTHER" API, and exposes twenty-two documented procedures and functions. It is referenced by nine other packages, which confirms its role as a shared recruitment utility invoked by higher-level Oracle HRMS recruitment flows rather than a standalone entry point. The header comment in the package body (peper02t.pkb 120.1) and the presence of the private procedure get_working_conditions illustrate that the package combines public validation/defaulting logic with internal helpers that resolve working hours, frequency, start and finish times, and probation attributes by inspecting position, organization, and business group levels in that precedence order.

Key Procedures and Functions

The documented entry points address several functional clusters:

• Record maintenance: INSERT_ROW, LOCK_ROW, UPDATE_GROUP, and PRE_UPDATE manage DML lifecycle activities for the package's central entity, including concurrency locking and pre-update processing.
• Vacancy handling: VACANCY_IN_ACTIVITY, UNIQ_VAC_FOR_REC_ACT, GET_VACANCY_DETAILS, and SET_VAC_FROM_REC_ACT support the relationship between vacancies and recruitment activities, including uniqueness checks and population of vacancy data from activity context.
• Applicant and combination validation: CHECK_APL_NUM_UNIQUE enforces uniqueness of the applicant number; CHK_JOB_ORG_POS_COMB validates the job, organization, and position combination; EXISTS_VAL_GRD_FOR_POS_AND_JOB verifies that a valid grade exists for a given position and job.
• Deletion and letters: CHECK_DELETE_ALLOWED determines whether a record may be removed; CHECK_FOR_LETTER_REQUESTS determines whether letter requests exist for the entity.
• Defaults and reference data: GET_DB_DEFAULT_VALUES, CREATE_DEFAULT_BUDGET_VALUES, GET_LOCATION_CODE, GET_TERRITORY_SHORT_NAME, and GET_STYLE_NAME supply defaulting and descriptive reference values used during applicant and vacancy entry.

The private procedure get_working_conditions resolves assignment working conditions using an in/out parameter design so that callers may pre-populate and test values; it queries position-level data first, then organization-level, then business group-level defaults.

Tables Accessed

The package reads and writes recruitment, people, and reference tables through APPS synonyms. PER_ALL_VACANCIES and PER_APPLICATIONS hold the core vacancy and application records. PER_ALL_PEOPLE_F and PER_ADDRESSES provide person and address data for applicants. HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL supply organization and translated organization attributes used in defaulting and working-condition derivation, while PAY_PEOPLE_GROUPS and PER_BUSINESS_GROUP context feed business group-level defaults. Budget-related procedures (CREATE_DEFAULT_BUDGET_VALUES) operate against PER_ASSIGNMENT_BUDGET_VALUES_F and PER_ASSIGNMENT_BUDGET_VALUES_S. Assignment status validation draws on PER_ASSIGNMENT_STATUS_TYPES, PER_ASSIGNMENT_STATUS_TYPES_TL, PER_ASS_STATUS_TYPE_AMENDS, and PER_ASS_STATUS_TYPE_AMENDS_TL. Letter processing uses PER_LETTER_REQUESTS and PER_LETTER_GEN_STATUSES.

Usage Notes

PER_APPLICANT_PKG is typically invoked indirectly by Oracle HRMS recruitment forms, applicant and vacancy entry screens, and by other PL/SQL packages in the recruitment and assignment creation stack (nine documented referencing packages). Customizations should call the documented public procedures rather than relying on private helpers such as get_working_conditions, whose signature may change between patch levels. Because the package performs validation, uniqueness checks, and defaulting as well as DML, custom code should invoke the appropriate validation procedures before insert or update, and should respect row locking via LOCK_ROW to avoid concurrency conflicts. The "$Header" revision string indicates the package body has been stable since 2005 apart from incremental fixes, so behavior is consistent across 12.1.1 and 12.2.2.