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

Smart Notification of PA52

 3 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Lacey
Basic Member
Posts: 14
Basic Member
6/17/2011 1:37 PM
    With MSS our supervisors will be entering personnel actions pending that will flow to the PA52. We would like this to trigger a smart notification with all the information that has been entered to the indirect supervisor. I can only get it to pull the header information (name, action, effective date) and the indirect supervisor code. It see the new information fields as repeats, combines them all together, and the field stays blank. How to I solve this issue?

    Thanks,

    Lacey Bisnett
    Carl.Seay
    Veteran Member
    Posts: 109
    Veteran Member
    7/1/2011 10:51 AM
      I typically use SQL Queries with Smart Notes. You could join PERSACTION and PADICT (to get the field names). In your scenario this would only work while the action is pending, once the PA100 runs it will go into PERSACTHST/HRHISTORY.
      Shane Jones
      Veteran Member
      Posts: 460
      Veteran Member
      7/1/2011 12:08 PM
        Have you considered using process flow. It is built to trigger off PA52 actions. You could pull everything when the action gets entered to PA52 and then email the results.
        You could build a different flow for each action type and instead of just notifying - you could trigger jobs, automatically verify data entered, or change other fields at the same time.

        Do you have process flow installed?

        Good luck. Let me know if you want to discuss.

        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...
        Todd_R
        Basic Member
        Posts: 4
        Basic Member
        7/1/2011 3:48 PM
          I would agree with Shane. A simple process flow set up might be efficient in the long haul. We have a lot of process flows and they might be a little unweildy, but if you use a simple design, you'll find it works well.