Search Results position_control_enabled

Overview

APPS.PER_PQH_SHR is a shared PL/SQL package within the Oracle E-Business Suite Human Capital Management (HCM) schema, created with AUTHID CURRENT_USER and identified in the ETRM repository under the API classification OTHER. The package name and its associated header comment (pepqhshr.pkh) indicate that it serves a supporting or "shared" role for position, assignment, and budget validation logic within Oracle HRMS. Its principal responsibility is to expose reusable runtime functions that determine whether position control is enabled for a given organization or assignment and to return descriptive status information about positions, including funded status and pending future approved actions. The package also aggregates a broad collection of business-layer entry points and validation routines—identified by the _BUS suffix and the per_abv prefix—that other HCM packages call to enforce consistency across position, assignment, location, and budget data. Because the object is shared rather than user-facing, it functions as a service layer invoked by higher-level HRMS APIs, forms, and concurrent processes rather than being executed directly by end users.

Key Procedures and Functions

The documented surface of PER_PQH_SHR comprises 25 procedures and functions. The function position_control_enabled—the object referenced in the search term—returns a VARCHAR2 indicating whether position control is active, resolving the setting against an organization, an effective date, and optionally an assignment. The function open_status returns the funded status of a position for a given position and effective date, describing whether the position remains open or filled/budgeted in a particular state. The function future_approved_actions returns information describing pending approved actions associated with a position.

The remaining documented routines fall into two groups. The validation procedures per_abv_insert_validate and per_abv_update_validate support the assignment budget value (ABV) mechanism, validating assignment budget records on insert and on update respectively. The _BUS routines—HR_PSF_BUS, PER_ASG_BUS, HR_LEI_BUS, HR_LOC_BUS, PE_AEI_BUS, PE_PEI_BUS, PER_PER_BUS, PER_APL_BUS, PE_JEI_BUS, PE_POI_BUS, PER_JOB_BUS, PER_DPF_BUS, PER_PSE_BUS, PER_JBR_BUS, and PER_VGR_BUS—form a set of business-layer handlers covering position, assignment, legal entity, location, applicant, person, job, grade, and related entities. These routines encapsulate business rules so that calling programs do not have to re-implement them; the ETRM metadata names them but does not expose their parameter lists, and parameter signatures should therefore be obtained from the package specification rather than inferred.

Tables Accessed

Through APPS synonyms, the package reads core HRMS tables. HR_ALL_ORGANIZATION_UNITS, PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS supply the organization hierarchy and structure data used to resolve position control at the correct organization and effective date. PER_ALL_POSITIONS and HR_ALL_POSITIONS_F provide position definitions and their dated (effective) attributes, while PER_ALL_ASSIGNMENTS_F supplies assignment rows for the assignment-aware functions. PER_ALL_PEOPLE_F provides person data. Setup and reference tables—FND_LANGUAGES, FND_TERRITORIES, and FND_USER—support multilingual and user-context resolution, and WF_PARAMETER_LIST_T is used for workflow parameter passing. These tables support read-oriented lookups that feed the package's validation and status functions.

Usage Notes

PER_PQH_SHR is not intended for direct end-user invocation; it is called from Oracle HRMS forms (particularly position and assignment maintenance windows), from concurrent programs, and from other PL/SQL packages—the ETRM metadata records that it is referenced by eight other packages. The _BUS routines and the ABV validation procedures are typically invoked during record insert and update processing to enforce budget and position-control rules before data is committed. Customizations integrating with position control should call position_control_enabled to test configuration rather than querying setup tables directly, and should pass explicit organization, effective date, and assignment values. Because the package runs AUTHID CURRENT_USER and relies on APPS synonyms, calling sessions must have the appropriate HRMS execution privileges. Signature details for all routines should be confirmed against the deployed package specification for the target release (12.1.1 or 12.2.2), as the header version reflects later patch levels.