Search Results chk_primary_prof_field
Overview
APPS.PQH_CORPS_UTILITY is a public PL/SQL utility package in the Oracle E-Business Suite 12.1.1 / 12.2.2 public-sector and defense human-capital-management footprint. It centralizes shared helper logic used by the Corps / Career Progression and spinal-points functionality of Oracle HRMS (formerly the "PQH" family of packages). The package is declared AUTHID CURRENT_USER, so its SQL executes with the privileges of the calling session's current schema rather than the definer, allowing it to be reused by multiple owning business processes without requiring direct object grants on every base table. In practical terms, the package supplies lookups, validation checks, index/salary computations, and formatting helpers that would otherwise be duplicated across Corps definition forms, copy-entity transaction logic, and the assignable spinal-point processing. It is not a standalone business API; rather it is an internal shared library that other PQH and HR packages call to resolve names, currency amounts, and hierarchical spine attributes consistently.
Key Procedures and Functions
The documented interface includes one procedure and twenty-three functions. The remaining functions below are named and described according to the documented metadata:
- REVIEW_SUBMIT_VALID_CORPS — validates a Corps definition submission in the context of a copy-entity transaction, effective date, and business group.
- GET_STEP_NAME / GET_STEP_NAME_FOR_HGRID — return the descriptive name of a spinal-point step, used for display and for hierarchical grid rendering.
- GET_INCREASED_INDEX — this is the object matched by the user's search term ("get_increased_index"). It resolves the increased (uplifted) gross index for a given input, either by effective date or by copy-entity transaction context; it underpins progression and increment calculations on the spinal points.
- GET_SALARY_RATE — derives a salary amount from a gross index and effective date.
- GET_GLOBAL_BASIC_SAL_RATE — returns the global basic salary rate for an effective date.
- GET_CET_BUSINESS_AREA — retrieves the business area tied to a copy-entity transaction.
- GET_BG_TYPE_OF_PS / GET_CPD_STATUS / GET_CORPS_NAME — descriptive lookups for business-group type, CPD status, and Corps name by definition ID.
- CHK_STEPS_EXIST_FOR_INDEX / CHK_PRIMARY_PROF_FIELD / CHK_CORPS_INFO_EXISTS / IS_CAREER_DEF_EXIST — boolean-style existence and consistency checks.
- BUS_AREA_PGM_ENTITY_EXIST / GET_PGM_ID — verify and resolve business-area/program entities.
- LOS_IN_MONTHS — converts years/months/days of length of service into a total month value.
- GET_FROM_STEP_NAME — resolves the originating step name for a step/transaction.
- UPDATE_OR_DELETE_CRPATH / DECODE_STAGE_ENTITY — maintenance and decode helpers used by downstream progression logic.
Tables Accessed
The package reads and writes through APPS synonyms. Spinal-point and progression data come from PER_SPINAL_POINTS, PER_SPINAL_POINT_STEPS_F, PER_SPINAL_POINT_PLACEMENTS_F, and PER_PARENT_SPINES. Assignment context is drawn from PER_ALL_ASSIGNMENTS_F. Corps metadata resides in PQH_CORPS_DEFINITIONS and PQH_CORPS_EXTRA_INFO. Copy-entity transaction state is held in PQH_COPY_ENTITY_TXNS and PQH_COPY_ENTITY_ATTRIBS, with results in BEN_COPY_ENTITY_RESULTS. Organizational detail is in HR_ORGANIZATION_INFORMATION, currency data in FND_CURRENCIES, global index values in PQH_FR_GLOBAL_INDICES_F, and DUAL is used for single-row evaluations.
Usage Notes
Because PQH_CORPS_UTILITY is classified as an "OTHER" API rather than a supported business API, it should not be treated as a formally supported integration surface. It is typically invoked internally by other PQH packages (five packages reference it) and by Corps definition and copy-entity forms during validation and display of spinal-point data. Custom code that calls it should pin the expected signature, since the two overloads of GET_INCREASED_INDEX demonstrate that signatures may vary by call context. Direct DML against the underlying tables through this package is not the intended pattern; callers should invoke the documented functions and rely on Oracle's standard validation paths to preserve data integrity across releases.