Search Results get_recruitment

Overview

APPS.PER_PERRPREQ_XMLP_PKG is the generated PL/SQL package body that supports the Oracle HRMS "Requisition Preparation Report" — an XML Publisher (BI Publisher) concurrent program report identified internally by the short name PERRPREQ. In Oracle EBS 12.1.1 and 12.2.2, XML Publisher concurrent programs are driven by an auto-generated package that contains a BeforeReport function, a set of user-defined data/group functions, and an AfterReport function. This package therefore acts as the report logic layer that resolves report parameters into display values and prepares the session context before the report's SQL query is executed.

The package belongs to the PER (Human Resources) product family and is classified as OTHER in the ETRM API classification, meaning it is not a public, callable API but an internal report-support package. It is owned by APPS and is not referenced by any other package (0 inbound references), confirming its role as a terminal report driver rather than a reusable library.

Key Procedures and Functions

The package exposes twelve documented procedures and functions. With the exception of the two standard report exit points and one global variable, all are value-lookup functions that translate numeric foreign-key parameters into descriptive names for the report layout.

• BEFOREREPORT — Standard XML Publisher pre-report trigger. It seeds a row into FND_SESSIONS for the current session (guarding against duplicates using USERENV('sessionid')), then resolves the business group parameter (P_BUSINESS_GROUP_ID) into its business group name and assigns it to the global C_BUSINESS_GROUP. Returns TRUE to allow the report to proceed.
• GET_ORGANIZATION — Returns the organization name for a supplied organization ID from HR_ORGANIZATION_UNITS, or NULL when the parameter is not populated.
• GET_JOB — Returns the job name for a supplied job ID from PER_JOBS_VL.
• GET_POSITION — Returns the position name for a supplied position ID from PER_POSITIONS.
• GET_GRADE — Returns the grade name for a supplied grade ID from PER_GRADES_VL.
• GET_LOCATION — Returns the location code for a supplied location ID from HR_LOCATIONS.
• GET_RECRUITMENT — Resolves a recruitment activity ID into its descriptive name from PER_RECRUITMENT_ACTIVITIES.
• GET_REQUISITION — Resolves a requisition ID into its descriptive value from PER_REQUISITIONS.
• GET_APPS_STATUS — This is the function matched by the user's search term "get_apps_status". It resolves an applicant/assignment application status code into a displayable status name, sourcing from PER_ASSIGNMENT_STATUS_TYPES.
• GET_VAC_STATUS — Returns the vacancy status description used in the requisition/vacancy section of the report.
• AFTERREPORT — Standard post-report trigger, returning TRUE.
• C_BUSINESS_GROUP_P — The package-level global (referenced alongside C_BUSINESS_GROUP) that stores the resolved business group name for reuse by the report query and layout.

Tables Accessed

• FND_SESSIONS — Read and inserted into during BeforeReport to register the reporting session and its effective date.
• PER_BUSINESS_GROUPS — Read to translate the business group parameter into a name.
• HR_ORGANIZATION_UNITS, PER_JOBS / PER_JOBS_VL, PER_POSITIONS, PER_GRADES_VL, HR_LOCATIONS — Read by the lookup functions to return organization, job, position, grade, and location descriptions.
• PER_RECRUITMENT_ACTIVITIES, PER_REQUISITIONS — Read to supply recruitment activity and requisition descriptions.
• PER_ASSIGNMENT_STATUS_TYPES — Read by GET_APPS_STATUS to resolve application status types.
• DUAL — Used by the FND_SESSIONS insert/verify statement in BeforeReport.

Usage Notes

This package is invoked exclusively as part of the PERRPREQ XML Publisher concurrent program executed from the HRMS responsibility. It is not intended for direct calls from forms or custom code. Because the functions rely on report parameters and the USERENV('sessionid') context, they must run within the concurrent manager session. Customizing this package body (for example, extending GET_APPS_STATUS lookups) should be done through a copy or an approved patch, as the header shows it is a NOSHIP-generated artifact maintained by Oracle. Any change requires recompilation under APPS and careful validation against the XML Publisher data template.