Search Results process_salary_java

Overview

HR_PAY_RATE_SS is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It supports the Self-Service Salary (SSHR) functionality, specifically the pay rate and salary change business flows exposed to managers and employees through the compensation self-service pages. The package acts as the transactional engine behind salary proposals, handling rate retrieval, currency conversion, validation, and the workflow-driven approval processing that underpins a salary change transaction.

The package is classified as an OTHER API rather than a public HR API. It is primarily intended for internal consumption by Oracle's own self-service components, including HR_PAY_RATE_GSP_SS (the generated self-service page API) and HR_TRANSACTION_SS. The "SS" suffix denotes its role within the self-service salary framework, and its dependencies on SSHR_SAL_COMP_TAB_TYP and SSHR_SAL_PROP_TAB_TYP confirm its integration with the salary comparison and proposal structures used by the SSHR salary pages.

Key Procedures and Functions

The package exposes 19 documented procedures and functions that collectively manage the salary change lifecycle:

• CHECK_MID_PAY_PERIOD_CHANGE — Determines whether a proposed salary change falls within an existing pay period, affecting proration and effective dating logic.
• CHECK_ASG_TXN_DATA / CHECK_GSP_ASG_TXN_DATA — Validate assignment-level transaction data for the standard and GSP (generated self-service page) flows respectively.
• MY_GET_DEFAULTS — Retrieves default salary, rate, and currency values for the current transaction context.
• GET_RATE_TYPE and GET_RATE — Resolve the applicable rate type and the corresponding pay rate value from element or grade rules.
• CONVERT_AMOUNT — Performs currency conversion between the transaction currency and the assignment currency.
• START_TRANSACTION — Initiates the salary change transaction record.
• VALIDATE_SALARY_DETAILS — Applies business validation rules to proposed salary components prior to submission.
• IS_TRANSACTION_EXISTS and GET_TRANSACTION_DETAILS / GET_TXN_DETAILS_FOR_REVIEW / GET_TRANSACTION_STEP_DETAILS — Query existing transactions and their workflow step state for display and review pages.
• PROCESS_SALARY_JAVA and PROCESS_API — Execute the core processing that writes the salary change through the HR API or Java layer.
• DELETE_TRANSACTION_STEP — Removes a workflow step when a transaction is withdrawn or rejected.
• PRATE_APPLICANT_HIRE — Handles pay rate definition during applicant-to-employee hire processing.

Tables Accessed

The package reads and writes through APPS synonyms. Workflow integration tables include HR_API_TRANSACTION_STEPS, WF_ITEMS, WF_PROCESS_ACTIVITIES, and WF_ITEM_ACTIVITY_STATUSES_V, which track the approval routing of each salary transaction. HR_API_TRANSACTIONS and HR_API_TRANSACTION_VALUES hold the transaction header and detail values written through the HR API layer. Payroll configuration is drawn from PAY_ELEMENT_TYPES_F, PAY_GRADE_RULES_F, PAY_INPUT_VALUES_F, and PAY_USER_COLUMN_INSTANCES_F, which supply the salary element definitions and grade rate rules used in rate resolution.

Person and assignment context is retrieved from PER_ALL_ASSIGNMENTS_F, PER_ALL_PEOPLE_F, and PER_ASSIGNMENT_STATUS_TYPES. Currency information comes from FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES to support CONVERT_AMOUNT. The BEN_PGM_F table is also referenced, reflecting integration with benefits eligibility checks.

Usage Notes

HR_PAY_RATE_SS is invoked indirectly by the SSHR salary change self-service pages and their generated page packages (HR_PAY_RATE_GSP_SS), which call the check, default, validate, and process routines in sequence. It is not intended for direct invocation from custom forms or concurrent programs; standard HR salary change APIs such as HR_ASSIGNMENT_API should be used for external integrations. Customers extending or debugging self-service salary workflows may reference this package to understand validation logic and workflow step handling, but modifications are unsupported. Because the package is VALID and references only documented ETRM objects, it remains a supported internal component in both 12.1.1 and 12.2.2.