Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

ESS Payment Modeling "Change"

 1 Replies
 1 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
TBonney
Veteran Member
Posts: 281
Veteran Member
2/8/2018 1:29 PM
    Forgive me if this is the wrong forum to which this should be posted. I have also posted it in the security forum as well, since it may be the result of an unintended security modification or require a security modification to fix.

    I have several users reporting that they are no longer able to 'Re-CaIculate' to see the effects of a different rate on their taxes, etc, using the payment modeling tool in ESS. They are still able to change all the other fields and see their effect, just not the pay rate. At Lawson's suggestion, I tried clearing the IOS cache in the portal, the security cache on the server and the user's personal internet browser cache. However, none of that worked.

    The users used to be able to change any of the field values and re-calculate to see what the effect on taxes and net pay would be. However, no changes were made to the system recently, with the exception of the application of year-end patches for HR/PAyroll and ACA. So I am wondering if something in one of those patches may have taken away a user's ability to change their rate within this tool.

    Has anyone else in the community experienced this and, if so, can they advise me on the fix/resolution to give this functionality back to the users?


    Or, whether or not the result of a recent patch, can anyone advise me as to where within Lawson security the authorization is granted to allow/disallow the various capabilities of this payment modeling tool functionality so that I may allow our users to use the full functionality of this tool once again?

    Thank you in advance.
    Bob Canham
    Veteran Member
    Posts: 217
    Veteran Member
    2/8/2018 1:38 PM
      We did not have any issues with payment modeling due to the year end patching (v10). If you want to do some more research into this, a good place to start is the ios log on the server ($LAWDIR/system). Are you able to reproduce this yourself? If so, you can see in that log if there are any errors reported, it should also indicate if there are security restrictions on something that is being done.

      From a security perspective, most of the rights to allow the payment modeling is controlled by the user's access to the PR89.1. So, if someone modified security for that form to prevent actions if the pay rate is changed, that could cause what you're seeing.