MSS and Personnel Actions

 3 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Shane Jones
Veteran Member
Posts: 460
Veteran Member
    I have a group of HR Representatives that I want to have entering Personnel Actions for associates that do not report directly to them.   I know that I could give them access to PA52 but it is not very user friendly and would give them way too many actions to pick from...   If I have personnel actions that the manager of an associate can enter does anyone know a way to tell the system that the HR Rep should be allowed to enter for all associates?
     
    I am trying to find a way to make the system list ALL associates instead of just direct reports on the "/lawson/xhrnet/personnelactions/personnelactions.htm" form so that it looks more like MSS when entering a change....

    Thanks in advance for your ideas...   
    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...
    Roger French
    Veteran Member
    Posts: 549
    Veteran Member
      Quick thoughts:

      If you have Design Studio you could design a simple from from the PA52. Then you also could apply security to it and the data underneath it as required for your needs.

      Another way if you specifically want Hr rep to use the MSS direct report functions like managers/supervisors have, you could customize the code behind the scenes in MSS to look at all employees, not just direct reports. 
      Shane Jones
      Veteran Member
      Posts: 460
      Veteran Member
        Roger,
        I was looking at the code for "personnelactions.htm" and it looks like it uses "paactions.htm" which gets the employee names that are displayed from an array that is created in "dr.js".   The array appears to be DirectReports.

        I was thinking I could have the dr.js copied to a new file called "allassociates.js" with an array called "AllAssociates" and then create copies of the other two files - with new references to the custom files.   However, the dr.js file uses HS10.2 (Direct Report Inquiry) to create the list so it is not as easy as just changing the select statement - it looks like an entirely new data pull process is needed in the array creation to populate the necessary variables...

        dr.js pulls a bunch of information about the associates that is not needed in the personnelactions.htm process (like: hiredate, birthdate, work description, etc.)    Really it just needs to pull the employee's company, employee number and full name...   Something like:

        http :// Server /servlet/Router/Data/Erp?PROD=PROD&FILE=EMPLOYEE&INDEX=EMPSET3&KEY=1%3DA1%2D%3EL9&FIELD=COMPANY;EMPLOYEE;FULL%2DNAME;LAST%2DNAME&OUT=CSV&DELIM=%09&NOHEADER=FALSE&NEXT=TRUE&MAX=2000

        I am able to modify (tweak) existing selects but I am not sure I would know how to create the new "AllAssociates" arrary for use with the existing "personnelactions.htm" and "paactions.htm" on my own...  I was kind of hoping that there was a way to configure the MSS to setup someone to see everyone automatically or to use a different "delivered" MSS page that is already configured to show all associates.  I will probably investigate your idea further unless someone else has an interesting solution...  
        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...
        David Williams
        Veteran Member
        Posts: 1127
        Veteran Member
          Typically when you modify a form like PA52 for certain users you will set it as the Default Presentation so when they form transfer the modified form is the one they see. If you need to have another PA52, like for HR reps, you will need to create another PA52 form in Design Studio, but with no modifications. You would then create a new Bookmark, called PA52X for example, pointing to this form that the HR users would use when they need to access the vanilla version of PA52.
          David Williams