[vc_row][vc_column][vc_column_text]SAP HR Personnel Development[/vc_column_text][vc_column_text]
The transaction code PPUP is really useful for creating frequently used settings in PD and is not that well known amongst HR users in SAP.
You can set your default plan version and the reporting period which is to be used in PD.
You can decide here, whether to include alternative qualifications and essential requirements for a qualification and whether to disregard totally the depreciation meter in SAP.
You can also enter your default appraisal model as well as default appraiser and appraisee types.
Before you configure number ranges, it is important to decide on whether the new number ranges are to be applied across all plan versions or be specific to individual plan versions.
You can configure number ranges in PD to be more specific for each of the different object types. The standard SAP system comes with the internal number range set on for all objects. This means that all of the objects, whether they be organisation units, jobs, positions, qualifications, tasks etc, all get their numbers from the same internal range.
You might want to, for example, configure the number range for jobs to be in the range 10000000 – 19999999.
Make sure that you dont delete the entry $$$$ which needs to be there for all of the other objects in SAP.
Create a number range $$C with the required number ranges. You can specify different internal and external number ranges. In addition you can set the current number for the internal range.
For additional number ranges, create the number ranges which start with a $$ followed by the object name.
Where you use the $$ value for the plan version, you need to make sure that the value for NUMRG COMP in table T77S0 in the step Set Up Number Assignment for All Plan Versions has an X. The number ranges are now valid across all plan versions.
Trying to maintain a PD object using detail maintenance (transaction code PP01). You will get an error message saying cannot be maintained via .
It is probable that the checkbox no maintenance has been ticked on table T77CD. Uncheck the tick. This table is specific to each infotype and each object type within the infotype.
As an example, you may wish to modify qualifications in PP01. Double click on IT 1000 and then look at the entry for Q.
Also look at table T777I. This holds details such as the no maintenance flag at the infotype level. So if IT 1000 is in this table with “no maintenance” ticked then this will apply to all objects on IT 1000.
Look at table T777I. This holds the time constraints for each object and relationship type. Change the time constraint from 2 to 3 to allow multiple overlapping records.
You will need to do the above if you wish to create and modify qualifications in detail maintenance, and if you wish to have one qualification linked to more than one qualification group.
It is not possible to link a qualification to more than 1 qualification in the qualification catalogue. What you can do is change the time constraint on table T77ZR to allow you to do this if this is not the correct table then see elsewhere in this document to give you the other table numbers. You also need to allow qualifications to be modified in Detail Maintenance. You need to take off the tick on the checkbox stopping you doing this – table T77CD and T777I (only if IT 1000 is in this table).
When you create a qualification group, you don’t get the chance to enter or change the abbreviated name. Look at table T777I this table holds the settings, which you can alter. This will then allow you to modify either Q or QK in Expert Mode General.
If you wish to link other infotypes to certain objects, you need to modify table T778M. You may wish to add the infotype for “web address” against an external instructor.
There is a very useful report. Menu path:
Org Mgt. Info System General Structure Display/Maintain
Remember to choose the correct evaluation path.
If you wish to change the text of a PD relationship you can do so in table T777E
When creating Business Event Types, make sure that the short names are unique if you have 2 types that fall into different Business Event Groups. If the short names are the same, then the system will warn you that the name is not unique. This is a warning message. You can plough through this. The problem is that if you use a matchcode search, entering the first few letters, then the system may crash.
The capacity infotype 1024 is a mandatory field when entering the details for a business event type. You can change the attribute from Duty to Mass or blank in the table which controls the Actions for Org Mgt. This field will no longer be mandatory for the business event type.
Take care as the capacity for a business event type is a crucial part of the system when validations are done for the business event which is ultimately created.
PCP is a planning tool and is great for looking at salary budgeting, costs relating to organizational change, enterprise bargaining impacts and general “what if” scenario running. Set up a couple of key wage types to start on. These might include a wage type with a free amount field and another wage type with perhaps a percentage value.
Run PCP based on the last payroll period’s results and make the planning period, for example, the next financial year. Take the results and produce some ‘what-if’ scenarios. What if I reduce 3 people from the one sales team but increase the number of positions in another. Or what if I reduce the drilling crew to supervisors only, give them a 5% increase and place in contractors at a flat rate. All the time, you can see what effect these strategies will place on the bottom line as the system recalculates the totals.
There are a number of shortcomings with SAP’s PCP functionality.
SAP’s PCP functionality does not cater very well for public sector customers. Payscale grade functionality is quite restricting with the current functionality.
You can only bring up payroll results by payroll periods.
If you have, for example, an employee in the monthly payroll who is on 3 weeks annual leave with a 15% loading, not only is this wage type calculated for the rest of the year (giving the person about 45 weeks leave for the year), but in addition the 15% will also inflate your results as it is also amplified to get the annual figures.
If you are aware of these shortfalls, then you can work around them.
If you wish to store more than 7 cost elements, you have to change the time constraint of the infotype, to allow more than one record.
You are not able to select on Personnel Area or Employee Sub-Group for different “what if” scenarios. You would have to create a user exit to accomplish this.
Scenario: You have 19 cost items to be considered for Projected Pay. But SAP only allows a maximum of 7 wage elements. What options are available?
Answer: Change time constraints of infotype 1015 to 3 and you can create any records of infotype 1015.
This table holds key bits of configuration relating to integration and control fields within SAP HR. All the HR modules have settings in this table. It is worth trawling through this table to get a better idea of what is contained in it. It is not worthwhile trying to memorise all the possible settings (there are too many). It is important to know what switches and controls are available to you.
Users often get confused about the way in which Personnel Administration is linked to Organization Management. There is no ‘link’ as one would imagine. When the integration is switched on any new position created in Organization Management is created in the database HRP1000 – where all the objects are created. In addition, the position is copied into table T528B which is used by Personnel Administration. When an employee is assigned a position, the system does a check to see whether the position ID exists within table T525B.
The integration switches are held in table T77S0. The key entry is “plogi orga” entry. If this is set to “X” then the integration is turned “on”, if there is a blank entry in this field, then integration is turned “off”. Don’t take for granted that your integration will always be spot on. Check different aspects of the integration in terms of the data synchronisation between PA and OM with the integration programs outlined below.
RHINTE00: This program transfers the PD objects from Personnel Administration to Organization Management. The system creates a batch input session (SM35) which you have to execute for the changes to be effected.
RHINTE10: This program is generally run if you have created any objects in Organization Management, before integration has been turned on. If you turn on integration before you create any objects, then you should not have to run this report. This report copies the objects into the Personnel Administration tables for jobs (T513, T513S), positions (T528B, T528T), org units (T527X) etc.
RHINTE20: This program is run to check the consistency between the objects in Personnel Administration and Organization Management. If any inconsistencies are found, you are able to correct these by double-clicking on a particular object type.
RHINTE30: This program updates Personnel Administration with any new data that has been entered in Organization Management. It creates a batch input session for the employees selected. Leave the selection blank to choose all available employees. Take the tick off the checkbox “Open Personnel Numbers Only”. If this tick is on, the system looks in table RHINTE30 to see whether the employee exists in this table. If they do then they will be processed.
If you are using 4.0b or above, it is fairly simple to transport PD objects from one client to another. Use the menu path:
HR Org Mgt Tools Data Transfer Create Sequential File
You can also use transaction code OOMV. The report name is RHMOVE00. This will convert the objects to a sequential file. Use RHALTD00 to convert the sequential file to a batch input file. Run both programs in the source client and run the batch input in the target client.