"Class Row: assumed property COMP_RATECD_TBL is not a valid record name" error on Salary Change Detail Page While Approving GSS Adhoc Salary Change Request
(Doc ID 2315860.1)
Last updated on NOVEMBER 23, 2023
Applies to:
PeopleSoft Enterprise HCM eCompensation - Version 9.2 to 9.2 [Release 9]PeopleSoft Enterprise HCM eCompensation Manager Desktop - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Symptoms
Issue : While approving the GSS Adhoc salary change request, when user clicks on Salary change details section, the page fails to load with an error message.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Class Row: assumed property COMP_RATECD_TBL is not a valid record name.
FUNCLIB_SALCHG.ADHOC_SALCHG_FUNC.FieldFormula Name:CalculateTotalComprate PCPC:33392 Statement:464
Called from:HR_GSS_MA.Salary.OnExecute Name:CalcSalaryAmounts Statement:96
Called from:HR_MSS_CT_MACMP_FL.Activate Statement:36
The specified object property is assumed to be a record name, but the record is not found in the current object.
Use the PeopleCode Debugger or a PeopleCode trace to determine the point of the error, and correct the program.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This only happens when the employee (for whom the request has been raised and being approved) have a comp rate code of type percentage in the Compensation Tab of Job Data (For Example: Comp Rate code: KABN01).
Once this error occurred, there is one additional button available in the header section called MORE, which is adjacent to Approve and Deny button. If user clicks on it they get Java error.
Please note : Comp Rate Code KABN01 is a reference to PeopleSoft Delivered Demo data.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |