Prev
Next
Forums Lawson S3 HR/Payroll/Benefits

benefit update reports

Sort:
You are not authorized to post a reply.
Author
Messages
Marla
New Member
Posts: 4
New Member
5/15/2007 10:50 PM
    I was curious if anyone had a timeline of when they run their benefit update reports for payroll. Recently we had a situation where I ran the BN100. and it had an error report. The errors indicated a change rule issues like "name change", "title change" etc. (things that do not affect benefits so I did not create a change rule) After about 3 hrs of global support including a web-x, they said, "Oh those are just warnings, not errors, and you can run it in update". This caused a MAJOR delay in the payroll process not to mention the years I lost on my life.

    The Lawson support also mentioned running the reports automaically on job scheduler. Why would anyone do that? We were advised to always run it in report mode first to find any errors (or errors that are warnings)If we did it through job scheduler and automatically scheduled the update we wouldn't have an opporutnity to see any error report.

    Sorry if I appear to have an attitude. I'm anti-Lawson right now.
    martingibbs
    Basic Member
    Posts: 18
    Basic Member
    10/11/2007 5:53 PM
      [We are 2 months from implementation]

      We run ours on a job schedule, but we have 40,000 + employees (not that we process that many in a given pay period) and the job runs around midnight each night. I found the errors vs. warnings a challenge as well, but I created a detailed procedure for reviewing the output in the morning. During our integrated testing, we found the process worked very well and with just a few tweaks to our rules and employee groups, the BN100 does just fine.
      You are not authorized to post a reply.