 |
Objective Setting and Appraisals
Increase Flexibility in Controlling Template Field Properties
Template configuration in Performance Management first defines for each field, whether it is open for input or not. Then it is possible to control for columns and rows, depending on Status and User Role, whether they are open for input, display only or hidden. But that’s it. More finetuning or using different criteria such as the substatus are not possible in the normal configuration in the appraisal template catalogue.
One way to get around this restriction is by using the BAdI HRHAP00_VAL_DET, which is originally designed to determine default values for fields.
As the data to control field availability are accessible in this BAdI, it can use it slightly different than originally intended. However, you need to check in each individual case, whether the result you are aiming at is actually achieved.
However, even with this BAdI it is not possible to hide the first column holding the objectives. This is particularly annoying in ECC 5.0 or earlier releases, because they restrict field control in the template catalogue to columns and do not allow hiding rows. This becomes available only in ECC 6.0. A way to get around this is to modify SAP standard coding in the method BODY_VALUE_DETERMINATION in class CL_BSP_HAP_DOCUMENT_UI. This can be particularly useful, if only required to bridge the gap between your current release and an upgrade to ECC 6.0 or higher and can be done by means of standard configuration afterwards. In any case these changes must be implemented by an ABAP OO developer really familiar with Performance Management and its BAdIs and you definitely need to test the whole process meticulously across all stages afterwards.
|
|
