Organisation key

[Former Member]

Hi experts

My client has a requirement wherein there is a set of employees for whom they want to maintain data in the system and run payroll for the same. These employees are not yet hired in the system. The main requirement is my client wants that the master data of these employees should be visible to only one user Id and not all. Even the payroll for these employees should be run through this specific User id and other user id should not be able to run it. Whatever reports are generated in the system the data relating to these set of employees should not be displayed by the report if it is executed by another user id.

All in all updating, maintaining & capturing employee life cycle, running payroll can be done by only 1 user id and the reports generated by other user id should not contain these employees.

Kindly guide how to make use of Organisation key for accomplishing the above requirement.

Best regards

Mahwish Khatib

[former_member194940 · Accepted solution]

Hi Mahwish, In this scenario,Please follow the below points: 1. First of all you will have a separate user id who will be responsible to do this transactions. 2. Create a separate role which will have authorization for this role that can be validated using org key. 2. A separate payroll for this group of employees needs to be created to differentiate the payroll and also can be used for authorizations. 3. Go to - SPRO - Personnel Administration- Org. data - Org. Assg. - Setup Org key here maintain - Organizational key: Maintain feature VDSK1 - Organizational key: Control - Organizational key: Creation rules. Once this configuration is done,then in the particular role you will be able to assign a org key. Hope this helps. Thanks, Bhabagrahi

[Former Member · Accepted solution]

Issue resolved

[Former Member]

Thank you Jagan and Bhabagrahi. Will try the same and reply.

[jagan_gunja]

To achieve this type of access for a group of employees, I'd suggest:

1) Security profiles - it would be preferable to use separate profiles by transaction code.

2) The security profile should not be based on pers.no., because it is too specific.  It is advisable that they are in a specific personnel sub area, org unit, or pay scale area, contract type, etc., so that the security profile is built based on this attribute/value.

3)It is also better to use a generic SAP logon id for example PRODnxx where n is a serial no. and xx is the attribute value from step 2 above.  You may have several such user id's to be used in the prod system/client.  The reason is that production jobs should not be run under a user id associated with his/her personnel number.

4)One logon id may have one/more security profile/s from above.

5)These id's should be used by the person/s as per the business rules.  The id needs to be administered by the HR/Payroll area/s.