Skip to Content
author's profile photo Former Member
Former Member

MSS Start Process for Employees

Hi ,

Can you advice what is the best way to get only the direct and indirect reportees under the start process for employees ->employee search . Currently it seems when the manager is searching for employees he is able to see literally everyone. Thanks.

Cheers,

Shyam

Add a comment
10|10000 characters needed characters exceeded

Related questions

7 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2014 at 10:11 AM

    Hi All,

    Finally managed to resolve the issue. The problem was on the configuration Personnel Management->HR Admin Services->Configuration of Forms/Processes->Process Configuration->Set Up Processes->Determine Processor Roles. The manager was set as a specialist as well and thats why he was getting the generic employee search screen. I have removed the checkbox and Nakisa View is showing up now. The backend table is t5asrprocrole.


    Agent.jpg (84.3 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 07, 2014 at 07:53 AM


    In Standard, it will display only direct and Indirect reportees. It wont display any employees other than his org.unit and sub.org.unit employees.

    See below screen shots for more clear.

    There is one org.unit and sub.orgunit

    When user logon and click on Start Process it will display employees from his orgunit and suborg.unit i.e Direct and Indirect reportees.

    Manager can search employees from his direct and indirect reportees only.

    He can't view other than his direct and indirect reportees in search criteira.

    See below screen shot. The org unit 10000499 is not under him, when he tries to search it wont display any thing.


    OU.PNG (67.4 kB)
    SP1.PNG (78.6 kB)
    SP2.PNG (91.3 kB)
    SP3.PNG (83.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2014 at 09:54 AM

    Hi Shyamlal,

    Whatever details which is getting displayed in the Start processes is based upon the OADP configuration maintained in the below node,

    Check for the object selection and the rules attached with the object selection and based upon this only the data is getting displayed in the application. I have shown a sample case here below,

    Likewise you can drill down from the node Group Organizational Structure views to the rules of object selection. In this start process application it uses the group MSS_ASR_TMV_EE and check for the assigned views against the group.

    Hope this gives an idea and helps you in finding how the applications behaves.

    Regards,

    Mithun K


    oadp.jpg (46.7 kB)
    MSSDIR.jpg (47.0 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2014 at 12:45 PM

    Hi Mithun / Sankar,

    Thanks heaps for your response. What I have noticed is when the manager logs in and clicks on start process for employees the nakisa chart as specified in the screen shot specified by Sankar is not showing up. Instead it just shows an employee search text box allowing the manager to search for any employee, select him and proceed with HCM process (similar to HR Admin searching for an employee).

    Previously for the same manager the Nakisa Org chart was getting displayed correctly. Recently we have made some role changes. I am really suspecting if by mistake we removed any of the required roles for Nakisa display. Any thoughts ??? Do you know whats the exact manager role required for Nakisa display ? Your help is very much appreciated.

    Cheers,

    Shyam

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 07, 2014 at 07:11 PM

    As others above have asked, please specify EhP level (and if on HR Renewal) but from the sounds of it, you are not using the MSS "Start Process" app. or you are using the incorrect "initiator role". Sounds like you are passing (or using the default) "HRASRA" which is the HR Admin "initiator role" and DOES allow a "wide open" search of employees. Make sure that the iView (or link) you are using is passing/using the correct "initiator role" such as "HRASRB" (manager) or your own custom one (anything other than HRASRA).

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2014 at 08:10 AM

    Hi All,

    I did some more analysis. I checked in our development system as well as our testing system. In development for all managers the Nakisa view is not getting loaded but its all good in the testing system. I am attaching the technical help from both the systems after clicking the Start Process for Employees. The initiator role is manager in both cases however the disable personalisation is checked in the Nakisa View while that parameter is not there in my development system. Can personalisation be the issue ???. Any advice on where I should be checking ?

    SIT system

    Dev System

    Cheers,

    Shyam


    SIT-1.jpg (105.5 kB)
    SIT-2.jpg (83.6 kB)
    DEV-1.jpg (94.3 kB)
    DEV-2.jpg (76.2 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2014 at 09:31 AM

    Hi All,

    Some more inputs and I guess we are close to resolve. I have debugged on the development system. When we click on start process for employees it goes to the WDA component HRASR00_PROCESS_EXECUTE_1. In the view V_SELECT_EMPLOYEE. Inside SET_NAKISA_SWITCH CHECK wd_assist->use_oadp_search = wd_assist->true. Currently in development the OADP search is coming as blank and it will default to the normal employee search but if I manually change it to 'X' the Nakisa view comes up ( screen shot attached). Can anyone advise where the OADP search is set up .

    Cheers,

    Shyam


    OADP search.jpg (312.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.