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

Processing Pended ESS transactions

 2 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Margie Gyurisin
Veteran Member
Posts: 538
Veteran Member
2/18/2011 3:40 PM
    We are set up in Lawson as one company and multiple process levels. Each process level does their own employee maintenance. We are on LS9 security and those users do not have LID nor terminal access.

    When we run the BS531, the BNBATCH and BNDEPBATCH are created in the employees print directory. But to commit those records to the employee, you need to run the BN531 and BN532. The default delivered path for those is the common work directory.

    I am looking for advice on how to handle this so that users don't overwrite the BNBATCH file in the work directory.

    We tried ad-ins but there is no way to capture the date and time the ESS user updated the data. We can capture their user id in BNBATCH but currently not in BNDEPBATCH.

    How have others worked this out?

    Thanks for your responses.
    Shane Jones
    Veteran Member
    Posts: 460
    Veteran Member
    2/19/2011 2:05 PM
      Have you looked at the "jobdef" in LID? You should be able to have a different job setup for each and then change the file locations in the definition of the BN531/BN532 jobs.

      You would have a job created with a different name for each process level to run and then change the jobdef to say where the files should be stored... It should work.

      Shane Jones
      Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
      Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
      ** Teach others to fish...
      Margie Gyurisin
      Veteran Member
      Posts: 538
      Veteran Member
      2/19/2011 3:08 PM
        I tried to do that but receive a message that the user has to be assigned to a security class. I am guessing that is because they are no longer laua users???? I can do it for someone who is still a laua user.

        From that, we could turn the LS9 switch off, create the jobs and then turn it back on.

        Much simpler than I was thinking it would be. Thanks.