While researching why some test scenarios were failing for our personnel actions processflow (salary changes outside the min/max rates were not being identified correctly) I discovered that a field was being returned truncated from a PA52 read.
PA52_PCT_NEW_VALUE_1r1, which had the new rate of pay in it should have returned with a value of 11.1234 but instead would return 34. It is being moved into EmpNewPayRate a double persistent variable. Our failed test scripts were using whole number and returning zeros. The logic we were having a problem with had code to get around other pa's that didn't change salary, so we skipped around the logic.
We had been using a java script expression to determine where the rate of pay was in the table, but I removed it and hard coded the assign in my debug processflow. I then removed all the other nodes in the flow one by one to see if one of them was causing the issue. No luck . When I test the call in the transaction builder (copying and pasting the call from the work unit log) I can see the correct value being returned in the window.
So far this has happened in 2 out of 6 test cases and if the user has the problem once it will happen again for that person. Lawson refuses to look at it because its a custom flow and I really don't feel like i can force the issue with them while we struggle to recreate the error. Anyone seen anything like this before? I'm out of ideas on how to track it down but the users aren't happy to hear about intermittent problems with work units.
FYI We're on processflow and LSF 9.0.0.6. Below is the PA52 call, it works correctly for most employees from what I can see. Thanks.
_PDL=&_TKN=PA52.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Inquire&PCT-COMPANY=&PCT-EMPLOYEE=&PCT-ACTION-CODE=&PCT-EFFECT-DATE=&PCT_ACTION_NBR=&_DELIM=%09&_EOT=TRUE
No luck, we're still getting the truncrated value.