Search Results per_pay_transactions_s

Overview

APPS.PER_SSHR_CHANGE_PAY is a PL/SQL package body in the Oracle E-Business Suite APPS schema responsible for processing salary and pay-related change transactions submitted through Self-Service Human Resources (SSHR). It acts as the server-side engine that validates, stages, and commits changes to an employee's pay proposal, salary basis, payroll, and assignment information. Within the Oracle HRMS architecture, SSHR change-pay transactions flow through the HR API transaction framework; PER_SSHR_CHANGE_PAY serves as the orchestration layer that interprets the workflow payload and applies the appropriate HRMS APIs. Its dependency list confirms a strong coupling to the HR API transaction model (HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, HR_API_TRANSACTION_VALUES), the payroll data model (PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_TYPES_F, PAY_INPUT_VALUES_F, PAY_ALL_PAYROLLS_F), and the pay proposal structures (PER_PAY_PROPOSALS, PER_PAY_PROPOSAL_COMPONENTS, PER_PAY_BASES). The package status is VALID and it is referenced by two other database objects.

Key Procedures and Functions

The documented package exposes eighteen procedures and functions that collectively manage the lifecycle of a pay change transaction:

• PROCESS_API / PROCESS_PAY_API — primary entry points that drive the overall processing of a submitted pay change.
• PROCESS_NEW_HIRE — handles pay-related setup during new hire processing, including initial assignment and pay proposal creation.
• GET_PAY_TRANSACTION — retrieves the pay transaction record associated with a change request.
• GET_TRANSACTION_STEP — returns information about a specific step within the HR API transaction.
• CREATE_SALARY_BASIS_CHG_STEP / CHECK_SALARY_BASIS_CHANGE — creates and validates the transaction step required when an employee's salary basis changes.
• DELETE_TRANSACTION / ROLLBACK_TRANSACTIONS / UPDATE_TRANSACTION / UPDATE_COMPONENT_TRANSACTION — support maintenance of the transaction and its component records, including deletion and reversal of uncommitted work.
• GET_CREATE_DATE / GET_CREATE_DATE_OLD / GET_UPDATE_PARAM — utility functions that retrieve creation dates and update parameters used during processing.
• GET_PAYROLL_PERIOD — resolves the applicable payroll period for the transaction.
• GET_COMP_FLEX — returns the descriptive flexfield information relevant to the pay component.
• GET_FTE_FACTOR — obtains the full-time equivalent factor used in salary calculations.
• CHECK_GSP_MANUAL_OVERRIDE — validates manual override behaviour in the context of grade step progression.

Each routine is designed to be invoked within the SSHR transaction flow rather than called independently in normal use.

Tables Accessed

The package reads and writes several core HRMS and payroll tables through APPS synonyms. It manages transaction state in HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, and HR_API_TRANSACTION_VALUES (with the _S sequence view). Employee assignment context is sourced from PER_ALL_ASSIGNMENTS_F and PER_ASSIGNMENT_BUDGET_VALUES_F. Pay proposal data is maintained in PER_PAY_PROPOSALS and PER_PAY_PROPOSAL_COMPONENTS, with PER_PAY_BASES supplying salary basis definitions. Payroll and element configuration is read from PAY_ALL_PAYROLLS_F, PAY_ELEMENT_TYPES_F, PAY_ELEMENT_ENTRIES_F, and PAY_INPUT_VALUES_F. Supporting data comes from BEN_PGM_F (benefits program), HR_ORGANIZATION_INFORMATION, and the flexfield usage view FND_DESCR_FLEX_COL_USAGE_VL. The user's search term PER_PAY_TRANSACTIONS_S appears in the dependency list and is used to populate surrogate keys when inserting pay transaction rows.

Usage Notes

PER_SSHR_CHANGE_PAY is not typically called from a form or concurrent program directly; instead it is invoked by the SSHR self-service flows and by the HR transaction APIs that process workflow-driven salary changes. Oracle's delivered salary change SSHR function and the HR_MAINTAIN_PROPOSAL_API both interact with this package to commit proposals into active assignments. Custom code should treat it as an internal implementation package — Oracle does not guarantee procedure signatures across patch levels. When diagnosing pay change issues, DBAs commonly trace HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS rows created by this package. Because the body is VALID and referenced by two other objects, modifications in custom environments risk invalidating dependent packages and should be avoided.