Search Results p_req_start_date

Overview

APPS.PER_PERRPREQ_XMLP_PKG is an Oracle E-Business Suite PL/SQL package that supports the Oracle HRMS "Requisition and Vacancy Status Report" XML Publisher (BI Publisher) concurrent report. The package acts as the report logic container for the corresponding XML Publisher data definition; its public package globals hold the report's bind and lookup values, and its functions resolve the descriptive text displayed alongside the report columns. The package is owner-qualified to APPS and is classified as OTHER in the ETRM repository, indicating it is a supporting report package rather than a public API for application developers. Its header indicates a last revision of 120.1 dated 2007, placing it squarely in the 11i-to-R12 lineage that remains valid in both 12.1.1 and 12.2.2.

The object name encodes its function: PER identifies the Human Resources (PER) schema family, PERRPREQ indicates "Requisition and Vacancy Status Report," and XMLP denotes the XML Publisher integration pattern. The package is referenced by no other packages, confirming that it is invoked by the report framework rather than called from application or custom code.

Key Procedures and Functions

The package exposes twelve documented programs. Two govern the report lifecycle: BeforeReport executes prior to report data retrieval, and AfterReport executes on completion. These functions perform standard XML Publisher pre- and post-processing, including initialization of session and parameter globals.

Eight functions resolve display values for report parameters and columns. GET_ORGANIZATION, GET_JOB, GET_POSITION, GET_GRADE, and GET_LOCATION return the human-readable names for the corresponding ID-based parameters, allowing the report to show descriptive text rather than numeric identifiers. GET_RECRUITMENT returns the name of the recruitment activity. GET_REQUISITION returns the requisition identifier or description. GET_APPS_STATUS returns the applicant or application status description, and GET_VAC_STATUS returns the vacancy status description.

The remaining program, C_BUSINESS_GROUP_P, is a packaging function that exposes the C_BUSINESS_GROUP global variable, which holds the business group name resolved during report initialization for use in the report layout.

The package also declares globals that are populated from the concurrent request parameters, including SESSION_DATE, P_BUSINESS_GROUP_ID, P_REQUISITION_ID, P_REQ_START_DATE and P_REQ_END_DATE, P_VACANCY_STATUS, P_ORGANIZATION_ID, P_JOB_ID, P_PEOPLE_GROUP, P_POSITION_ID, P_GRADE_ID, P_LOCATION_ID, P_RECRUITMENT_ACTIVITY_ID, P_APPLICANT_STATUS_ID, P_CONC_REQUEST_ID and P_GROUP_FLEX_NUM. A user searching for p_req_end_date has located the package global that carries the report's requisition end-date parameter into the report query and layout.

Tables Accessed

Per the ETRM metadata, the package reads from the following APPS synonyms:

• FND_SESSIONS — used to establish the current session context, including the effective date used when resolving dated HRMS information.
• PER_REQUISITIONS — the core requisition source; supplies the requisition records filtered by the start- and end-date parameters, including P_REQ_END_DATE.
• PER_RECRUITMENT_ACTIVITIES — supplies recruitment activity names resolved by GET_RECRUITMENT.
• PER_JOBS — supplies job names resolved by GET_JOB.
• PER_ASSIGNMENT_STATUS_TYPES — supplies status type descriptions used by GET_APPS_STATUS and GET_VAC_STATUS.
• DUAL — used by the lookup functions for single-row selection and validation queries.

The package performs read-only access; no inserts, updates, or deletes against application tables are documented.

Usage Notes

PER_PERRPREQ_XMLP_PKG is invoked by the XML Publisher concurrent program "Requisition and Vacancy Status Report." When the concurrent manager runs the report, the BeforeReport function initializes the globals from the concurrent request parameters, the report's data model query (bound to the package globals) returns the result set, the GET_* functions supply descriptive values, and AfterReport performs cleanup.

Because the package is not a public API and exposes no general-purpose business logic beyond report rendering, custom code should not call it directly. Customers requiring additional report output should build a custom XML Publisher data template that queries PER_REQUISITIONS and the related HRMS views independently, leaving this seeded package untouched to preserve supportability during upgrades to 12.1.1 and 12.2.2.