Search Results save_gsp_txn

Overview

APPS.HR_PAY_RATE_GSP_SS is a server-side PL/SQL package within the Oracle E-Business Suite covering the HR and payroll functional area. The suffix "SS" identifies it as a Self-Service component, indicating that the package supports the Oracle Self-Service Human Resources (SSHR) framework and, more specifically, the Grade Step Progression (GSP) business process. In Oracle EBS 12.1.1 and 12.2.2, Grade Step Progression enables organisations to move employees along a defined grade ladder automatically or by approval workflow, generating the associated payroll rate changes and pay proposals.

The package orchestrates the transactional logic that sits between the self-service user interface, the HR assignment model, and the payroll engine. It derives an employee's current salary from assignment data, determines whether the employee's grade step configuration permits progression, creates the resulting payroll transaction records, and persists the Grade Step Progression transaction for downstream processing. The package is embedded in the SSHR approval and notification flow through its use of Oracle Workflow entities, ensuring that GSP actions raised from self-service are tracked and auditable.

Key Procedures and Functions

The documented API surface consists of six procedures and functions, classified as OTHER rather than as a public HR API:

• GET_EMPLOYEE_SALARY — retrieves the salary associated with an employee, reading from assignment and pay proposal data to establish the baseline amount used in the progression calculation.
• GET_EMPLOYEE_CURRENT_SALARY — returns the employee's current, effective salary, distinguishing the present rate from any proposed or historical amount.
• CHECK_GRADE_LADDER_EXISTS — validates that a grade ladder definition exists for the employee's grade, acting as a prerequisite check before any progression can proceed.
• GETGRADELADDERNAME — returns the name of the applicable grade ladder, supporting user-facing messages and workflow routing.
• CREATE_PAY_TXN — constructs the payroll transaction record that represents the salary rate change arising from the grade step progression.
• SAVE_GSP_TXN — commits the Grade Step Progression transaction, including the associated workflow item state, so that the progression is durable and visible to subsequent processing.

Tables Accessed

The package reads and writes the following objects, accessed through APPS synonyms:

• PER_ALL_ASSIGNMENTS_F — the core assignment record, supplying the employee's current grade, step, salary basis, and effective dates.
• PER_PAY_BASES, PER_PAY_PROPOSALS, PER_PAY_TRANSACTIONS, and PER_PAY_TRANSACTIONS_S — the payroll configuration and transaction tables where the resulting rate change is recorded.
• BEN_PGM_F — the benefits program definition, consulted where progression interacts with benefits eligibility.
• HR_API_TRANSACTION_STEPS — the HR API transaction framework table, used to coordinate the multi-step progression transaction.
• WF_ITEMS and WF_PROCESS_ACTIVITIES — Oracle Workflow tables used to track the GSP approval item and its activity state.
• HR_TRANSACTION_SS and SSHR_SAL_PROP_TAB_TYP — self-service transaction and salary proposal structures supporting the SSHR entry point.

Usage Notes

HR_PAY_RATE_GSP_SS is an internal self-service component rather than a documented public API. It is most commonly invoked through the SSHR Grade Step Progression pages, where an employee or manager initiates a progression action, and through the associated Oracle Workflow approval process that references WF_ITEMS and WF_PROCESS_ACTIVITIES. The package is also referenced by HR_PROCESS_ASSIGNMENT_SS and HR_PROCESS_ASSIGNMENT_STEP_SS, which drive assignment processing and step-level handling respectively.

Because the procedures are classified as OTHER, direct invocation from custom code is not recommended. Customisations should instead call the supported HR and payroll APIs, allowing this package to operate as designed within the SSHR and GSP framework. Any modification carries the usual support implications for self-service HR objects.