Settings in Personnel Development
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.
Number Ranges
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 don’t 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.
Can’t maintain using Detail Maintenance?
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.
Creating a new relationship deletes the existing record?
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.
Qualifications linked to more than 1 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).
Qualification short name defaulted through – without the ability to modify it?
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.
Linking other Infotypes to certain Objects
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.
Useful Report - Maintain and Display a Structure
There is a very useful report. Menu path:
Org Mgt.
Remember to choose the correct evaluation path.
Changing the Text of a Relationship
If you wish to change the text of a PD relationship you can do so in table T777E
Business Event Type short names
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.
Capacity for Business Event Type – mandatory field
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.
Personnel Cost Planning
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.
Table T77S0 - Controls key PA and PD default settings
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.
PA-PD Integration
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.
Org Structure - Data Migration
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
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.
Transporting PD objects
This is carried out using the program RHMOVE30.
It is best to run the program RHINTE10 before you move any objects through the transport system. This updates the tables that are common to both PA and PD. You can use RHMOVE30 to include your objects in the transport. Note that with the new object types in version 4.7 it can be a bit trickier to move the objects via transports using this method. Objects such as categories and templates etc within Appraisals (MBO functionality) are examples of this.
If you would like to check the integration objects, you can do so at any stage by running the report RHINTE20. This gives you the PD objects not in PA etc.
To run RHMOVE30, you can use the menu path:
System
The program, like most PD objects, hinges on evaluation paths. Choose the object that you would like to transport. The evaluation path gives you an opportunity of taking other objects with the chosen object - the relationships go with it as well.
Transporting: Org Units, Positions and the Cost Center assignment.
Choose O(org unit) as your chosen object. Use o-s-k(from-via-to) as the evaluation path. From the list of available options, choose "kostos" as the path.
Click on the execute button. First test it (make sure that the test check-box is ticked)
The result will only show org units and positions. The relationships to the cost centers are there but the actual cost centers are not in the PD domain, hence the reason why you can't see them there.
Run the report again without the "test" on. Make sure that the check-box "objects to be transported" is on.
The resultant output shows you all the objects again (org units and positions) but this time they have a transport icon next to them, which is ticked.
Click on the transport icon to transport the objects.
To check and see what objects and relationships are going to be transported (once they have been released and are ready to be transported), use transaction code SE10. Click on the transport and use the menu path:
Request/task
Double-click on the line and you will see what is going to be transported.
Transporting the Qualifications catalogue
Use the evaluation path QUALCATA which is the complete qualifications catalogue.
Transporting all the Tasks
Use the evaluation path A* and B* to cover all possible relationships.
Transporting the remaining objects and relationships
Use the following evaluation paths:
All relationships around positions including reporting structures, infotype records etc
Use: A* and B* - put them in the same transport
All Relationships around jobs including the relationships to qualifications and tasks etc
Use: A* and B* - put them in the same transport
Org Mgt - Object Attributes
If you wish to find out the attributes of an object in Organization Management, you can do so using the menu path:
HR
You may wish to find out which user created or last changed the object. Fill in the object type and object ID and tick the checkbox down below - "last changed by". This will give you the information detailing when the record was created and by whom.
Depreciation Meters
The depreciation meter used to be called the decay meter in earlier versions of SAP. It is updated far more frequently than it used to be in earlier versions of SAP. You can specify that the depreciation meter should not be taken into account, by a specific system user (user parameter PEH).
The validity allows you to show that certain qualifications (such as licenses) expire and have to be renewed regularly. If you have defined a validity for a qualification it will be shown against the person's profile for the duration of its validity.
Decay of Qualifications
Usually, one sets the decay for a qualification (for example 1 year). Anyone who is given that qualification will only have that qualification for a year from the start date of the record.
There is a report in T&E "Attendees Qualifications" (RHXQALIF) which shows the user which qualifications are no longer valid. Choose a date after which the qualification should have decayed, and it will appear in dark blue - to indicate that it is no longer valid.
Qualifications Catalogue and Profile Match-ups
To fully integrate PD and Personnel Administration, one needs to set the integration switch to on. You will then see a different view on IT 0024 in the employee's master data. You will be able to dip into the qualifications catalogue to assign entries for the employee.
You can create a qualification catalogue (OOQA) wherein you maintain all the requirements and qualifications. You can maintain the requirements of the position from PD (PPPM) and assign various qualifications in the positions profile.
You can run a profile match-up, between actual qualifications held by the employee and the potential requirements of the position.
In Training and Events you can set up the relationship A028 - Imparts Qualification (00ET) at the business event type level.
During a profile match-up run as a consequence of succession planning, if there is a qualification which is a deficiency for a particular employee and it is defined as an imparted qualification for the business event type, then the system prompts you to nominate the employee directly for the required training course.
How SAP calculates the Suitability Percentage
It is best described by way of an example.
If Joe has 3 qualifications and the position requires 4 then his suitability will be 75%.
Assuming Joe now has the 4 required qualifications. 3 of them have a scale of "Yes". Each of those will make up 25% of his suitability fit. So his suitability will be equal to 75% plus whatever "fit" he has for the 4th qualification.
If the 4th qualification has a scale which is made up of 5 values ranging from 1-5(1 being poor and 5 being excellent).
If the position calls for a 3 and Joe has a 1 then he is only given 1/3 of the remaining 25% which means that his suitability is then 75%+(0.33333x25)=83.33% Should he have been given a 2 for that qualification then he will have a suitability of 75%+2/3(25)=91.67% Having a scale of 3 against his name will give him a 100% match, because that is exactly what the position calls for.
Now if Joe is overqualified, i.e. he has a 4 or a 5 then that will either give him a suitability of more than 100 or less than 100 depending on the setting for the value "Quali Overq" in table T77S0.
PD - Graphical Reports
Information which you may not know about the graphics in PD on SAP.
Information about the object (position) in the organisation chart is available in the menu called EXTRAS. You can get quick info about the object in a separate window on the same screen. This can be used to differentiate between position types.
An object's shape can be changed but that is valid only in the current session. If you use the options and save it, the shape of all the objects change.
You can, however, differentiate on the status of the object e.g. planned / active.
It may be possible to modify the table and the underlying program to include sub group etc. as a decision parameter along with the object status. This can be done in the IMG under the step: Create Data Sets.
The entire structure can be printed to a file with extensions .psc or.cgm . This can then be manipulated using additional software.
No comments:
Post a Comment