I've seen this mentioned a few times, but having written this up, I thought some of you might find it usefull to have a more comprehensive description os this new feature, which I personally - as someone working a a few multi-country set-ups - belief is really cause for serious celebrations. Thank you Customer Connection Program!
If your organisation has been using SAP HCM for, say, 10 or 20 years, you'll know this problem all too well, particularly if your organisation is spread over a large number of countries:
The list of personnel (sub)areas and employee (sub)groups gets longer and longer and there is no easy way of making sure users don't pick obsolete objects, because none of them comes with time dependency or a validity period.
This has now changed with SAP note 1883014. SAP offers now the option to use validity periods for the 4 organisational objects mentioned above. This validity period acts as a constraint for what can be captured in personnel actions and infotypes 0001, 1008 and 1013, and cleans up the list when you hit "F4".
Once the required support package has been applied, you can easily activate the new feature in table T77S0, entry ADMIN - DELIM:
Note:
The first change you'll notice after the activation is that the objects feature a validity period in entry helps now:
So, let's assume we want to create a new personnel subarea "Cardiff" valid only from 01/01/2014. You create it by copying an existing one and renaming it as you would normally do. Then you find the configuration for validity periods in the IMG via: Enterprise Structure > Assignment > Human Resources > Validity Period for Organisational Assignments and add a new entry for Cardiff:
If we try to change the current record for an active employee starting at 01/07/2013, we see the same result as above, because the new subarea isn't valid yet:
However, if we create a new record in infotype 0001 starting after 01/01/2014, we find Cardiff in the list of options:
The same logic applies to personnel areas, employee groups and employee subgroups. We consider this a very helpful improvement to increase efficiency, avoid user frustration and improve data quality in SAP HCM. We definitely recommend implementing it, so you can get rid of old entries from all four tables in day-to-day business. Particularly in large global organisations, the lack of such a validity period has always caused problems in the long run.
There are a few points to be considered in the business process:
Some technical notes:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |