Search Results get_next_oipl
Overview
PQH_GSP_DEFAULT is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Grade/Step Progression and salary defaulting logic used by Oracle Advanced Benefits and Oracle Human Resources. The package is defined with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner, which allows it to respect the row-level security and business group segmentation of the calling application context.
The package serves as a central repository for defaulting decisions within the grade step progression (GSP) framework. Its core business purpose is to determine, for a given assignment or plan enrollment, which grade, step, grade ladder, and progression option should be applied, and to compute related salary values such as the current salary and the salary corresponding to a particular step. The presence of the user-searched function GET_CUR_SAL reflects the package's role in resolving an assignment's current salary for a specified effective date, which is a prerequisite input when evaluating whether an employee qualifies for a salary-driven progression increment.
Key Procedures and Functions
The package exposes 22 documented procedures and functions. The principal ones include:
- GET_CUR_SAL — Returns the current salary for a given assignment as of an effective date. This is the entry point most commonly referenced when salary context is required before applying progression rules.
- GET_ASG_FOR_PIL — Resolves the assignment associated with a plan enrollment record, establishing the person-in-plan context for subsequent defaults.
- GET_LOWEST_SAL_INCR_STEP — Determines the lowest step that would produce a salary increase relative to a supplied current salary, optionally scoped to a grade and assignment.
- GET_SAL_FOR_STEP — Returns the salary value associated with a specified step and effective date.
- GET_ELECTBL_CHC and GET_DEF_AUTO_CODE — Derive the electable choice and the default automatic processing code for a person in a plan.
- GET_DEFAULT_PROGRESSION — Produces the full defaulting result, including electable choice, return code, and any error message.
- GET_DEFAULT_GL, GET_GL_DETAILS, GET_NEXT_GRADE, GET_NEXT_STEP, GET_NEXT_PLAN, and GET_NEXT_OIPL — Navigate the grade ladder structure to identify the default or next grade ladder, grade, step, and plan.
- GET_EMP_STEP_PLACEMENT, STEP_PROGRESSION, GRD_STEP_PROGRESSION_RESULT, GRADE_PROGRESSION, GET_DEFAULT_STEP, GET_STEP_SEQ, and IS_GRADE_IN_GL — Support placement evaluation, progression execution, and grade ladder membership validation.
Tables Accessed
The package reads and writes through APPS synonyms across benefits, payroll, and HR tables. Benefits tables such as BEN_ELIG_PER_ELCTBL_CHC, BEN_ENRT_RT, BEN_LER_F, BEN_PER_IN_LER, BEN_PGM_F, BEN_PLIP_F, and BEN_PTNL_LER_FOR_PER supply plan enrollment, electable choice, and rate eligibility context. Payroll tables including PAY_ALL_PAYROLLS_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F provide the salary element entries that underpin GET_CUR_SAL and GET_SAL_FOR_STEP. HR tables PER_ALL_ASSIGNMENTS_F, PER_GRADE_SPINES_F, PER_PARENT_SPINES, and PER_PAY_BASES supply assignment, grade spine, and pay basis definitions that drive grade and step traversal. Notably, the package does not write to core transactional tables; it functions predominantly as a read-oriented defaulting engine, deferring actual updates to the calling progression processes.
Usage Notes
PQH_GSP_DEFAULT is invoked indirectly, most commonly through the Grade Step Progression and salary defaulting workflows in Oracle Advanced Benefits, including the eligibility and automatic processing routines that elect progressions for plan participants. It is referenced by two other packages, which indicates it is a subordinate utility rather than a top-level API. Custom integrations typically call the functions in a read-only fashion, supplying an assignment or plan enrollment identifier and an effective date, then consuming the returned defaults to drive their own processing. Because the package uses AUTHID CURRENT_USER and depends on effective-dated tables, callers must supply a valid effective date and ensure the session context (business group) is set appropriately.