Should Users Create Position Code

In our organisation, after recent implementation of SAP HCM, creation of Org Unit, Job Code, Position Code is done by a OM module Core Team member. 

Our users prefer to create position code, Org Unit on their own and requesting us to train them. On the first hand, we are not comfortable in handing over this module to the end users as right from uniformity in text will be missing. But before rejecting their request, we would like to know the practice in other companies. 

Suggestion:

As per our organization units, end user should not have an authorization to create position code or anything related to organization structures or master data configuration, their job is to maintaining and updating data. 

Creation of PD / OM objects must be centralized. That is why in SAP technical terms they are called as Planning Objects. If you focus on the word 'Planning' you will know it's importance. 

You have to foresee for next 5 years on what will be the state of your database if you give it to end user. 

The biggest of mistake they will do is in validity dates. 

Ask yourself this question as how many Position will they create in a day/month/year. 

How many Org.Units will a company practically create in a Year. 

Alternate solution is, if you have ESS / MSS and E-Rec the end-users can raise a Request. 

So keep all this in mind you have to gather your courage to say a big NO to the end-users. 

You have to take note that Org units, jobs, positions, etc creation/maintenance should be the responsibility of a HR area looking after the establishment (of the organisation). They also need to follow established standards, procedures, user guides. The standards / procedures need to be reviewed/amended periodically. 

Normal production version would be 0 or 1. Changes are usually made in a different version or more than one version. The changes are from a specific change effective date The changes are reviewed by the senior management, amended as necessary, and then approved. Change management requires managing the impact on the organisation and its people and a good strategy. 

Once the changes are approved, they are communicated to the organisation. The changes will be moved to the standard production version. 

Then employees are assigned to the required positions/jobs as required by individual org units. These changes will be the responsibility of the org unit managers and their HR admin. 

The security or authorization profiles are accordingly maintained and assigned to the positions. The positions are assigned to the employees. Sometimes an employee may have additional responsibilities or tasks other than those assigned to the position he/she holds. For this purpose, the person may need additional security profile assigned for a specific period. 

SAP HR Tips

Also See
Meaning Of MSN20, MSN21 and MSN32

SAP Human Resouce Books
SAP HR Books - Certification, Interview Questions and Configuration

SAP Human Resource Tips
SAP HR Tips and Human Resource Management

Main Index
SAP Basis, ABAP Programming and Other IMG Stuff

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.