PA100-enter changes early but not affect HR11?

Sort:
You are not authorized to post a reply.
Author
Messages
Michael
Basic Member
Posts: 8
Basic Member
    Hello gurus!

    Issue:

    Employees need to be entered in Lawson early so that our benefits team can get a head start.
    HR is unable to enter changes early, process them early and not affect HR11. 

    Current process:
    Enter changes early, process them early using PA100. This also updates HR11 even through the effective date is a future date.

    Requesting:

    Enter changes early, process them early using PA100 and not update HR11 until the effective date.

    Lawson's response:

    If you are running PA100 changes early (future effective date) then they will show up on HR11. The only way to change this is not run PA100 for a future date or change the reports to include effective date of action. Lawson does in almost all the tables store effective date of action and time/date stamp so that we can report off of this information.


    ***
    I still want to process transactions but not update HR11. It does not look like it is possible to to process early changes without affecting HR11.


    Please help, thoughts, alternatives?

    thank you
    Dave Curtis
    Veteran Member
    Posts: 136
    Veteran Member
      I know of no way to process a change without actually making the change.

      However, if the main goal is to inform benefits (or anyone else) of the change. You could just build a report that pulls the change detail from the pending actions. This would allow you to get the info to benefits but not really process the change.
      BarbR
      Veteran Member
      Posts: 306
      Veteran Member
        The best way would be to use work flow (process flow). Adding an action on Pa52 will trigger a flow if set up to do so on Pa50 and a service created with that action name. The flow can do notifications, require approvals if desired, almost anything you can think of.
        Michael
        Basic Member
        Posts: 8
        Basic Member
          Thanks, Dave. I appreciate the time.
          Michael
          Basic Member
          Posts: 8
          Basic Member
            Thank you, BarbR. We'll have to give it a try. Dave also suggested a report, which was also a tool we'll be using. You guys are great!
            Shane Jones
            Veteran Member
            Posts: 460
            Veteran Member

              Michael,

              Everyone is correct that once you run PA100 to make it so that their record can be used for "other" processing they will show on HR11.   In fact, you cannot really do anything to the record until they show on HR11.    Of course having a process to notify on hires is a good thing and could be with a report or process automation email...   A different creative solution - have them show on HR11 with a status code that is setup as not being an employee when first pulled into HR11.   They could be non-paid and non-counting EMP_STATUS on HR11 and then on the day of hire (or one day before) you could have their status changed.    (A lot of thought would need to be put into this because if you have employee groups tied to benefit plans the code would need to be setup correctly for those groups. -- especially when they are tied to benefit plans on BN15...

              Good luck!

              Shane

              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...
              Michael
              Basic Member
              Posts: 8
              Basic Member
                Hi Shane,

                Thank you for the added information. You and the other members have been helpful as always.

                Much appreciated!
                You are not authorized to post a reply.