Though we have used many Functional Modules and BADI’s in Objective Setting and Appraisals thought of sharing a scenario with relevant Functional Modules being used.
Scenario: Mass Appraisal Document Creation: We do not have standard functionality to create mass appraisal documents with Reviewer and Approver. Transaction code phap_prepare_pa have limited options to create appraisal documents.
We need to Enhancing the program - RHHAP_APP_DOCUMENT_PREPARE_PA to Create Mass Appraisal documents with Appraises, Appraiser and Further Participants details.
Reviewer: Managers Manager (One level up)
Approver: Reviewers Manager (Two level up)
Role ids and Sub status ids are to be considered while building the program.
a. Prerequisite: Basic Template Configuration with Status Flow and Roles should be in place.
Transaction codes can be used : OOAM, OOHAP_BASIC.Phap*
b. Function Modules: Below are the Standard functional Modules can be enhanced
Ø HRHAP_0DOC_DET_NEW_STATUS
Ø HRHAP_DOCUMENT_CREATE
c. BADI’s we have implemented:
Ø HRHAP00_COL_ACCESS-- Appraisal Document - Column Access – Based on Column we have restricted change and display access.
Ø HRHAP00_BUT_ACCESS- Appraisal Document - Pushbutton Access – Push button ids are disabled for few Roles.
Ø HRHAP00_ADD_HEADER- Appraisal Document - Additional Header Data (Additional Data for Appraisee) – WD ABAP component is enhanced to add custom fields.
As we have already some good blogs explaining the above Column Access Badi, thought of sharing the Functional Modules to create Mass Appraisal Documents with Different Scenarios.
Standard Appraisal Document process Flow is based on the Status and Sub Status and Roles (Person Authorized) configured in the Appraisal Tempalte. Appraisal Documents will be pushed to Different Participants In boxes and Status and sub status will be changed.
We have the below Status Flow Configured in the System.
Status Flow 1. We have defined the below status flow in the Apprasial Template.
Status | Sub Status | Pushbutton | Roles |
In Preparation -1 |
|
|
|
In Planning-2 | With Employee-M | Submit | Appraisee -AP |
In Review-3 | With Manager-J | Submit | Appraiser-AR |
In Review | With Reviewer-K | Submit | Reviewer -RR |
In Review | With Approver-A | Submit | Approver-AP |
In Review | With Admin HR- L | Complete | HR -HR |
Completed -5 |
|
|
|
There would be few scenarios where we may have to skip either Reviewer or Approver in the Appraisal Document. So, we have to skip the below Sub Status and Roles in few scenarios.
Below would be the Status Flow 2: Appraisal Document should be created skipping the Sub Status – With Approver and Role AP. We have not configured this flow in the Tempalte.
Once Reviewer Submit, Appraisal document Sub status should be changed to With Admin – HR skipping the With Approver sub status.
Status | Sub Status | Pushbutton | Role | Code |
In Preparation -1 |
|
|
|
|
In Planning-2 | With Employee - M | Submit | Appraisee | AP |
In Review-3 | With Manager-J | Submit | Appraiser | AR |
In Review -3 | With Reviewer-K | Submit | Reviewer | RR |
In Review -3 | With Admin HR-L | Complete | HR | HR |
Completed -5 |
|
|
|
|
Status Flow 3: Appraisal Documents should be created skipping Reviewer Sub status and Reviewer Role.Not Configured in the Template.
Once Manager submits, Appraisal document Sub Status should be set to With Approver.
Status | Sub Status | Pushbutton | Role |
In Preparation |
|
|
|
In Planning | With Employee -M | Submit | Appraisee - AP |
In Review | With Manager-J | Submit | Appraiser- AR |
In Review | With Approver-A | Submit | Reviewer - RR |
Completed |
|
|
|
Standard Status flow will not support for the above 2 scenarios, the below Functional Modules can be used in a zprogram which can be used for Mass Appraisal Document Creation. Appraisal Document header data will be updated as per the available Roles and corresponding document sub status is skipped during the process.
The same change will be applicable for the documents created using APPCREATE transaction code.
Ø HRHAP_DOCUMENT_CREATE
Ø HRHAP_0DOC_DET_NEW_STATUS: Enhancement Point to be implemented.
Based on Old and new sub status appraisal sub status will be pushed to next/completed status.
HRHAP_C_IT5026_READ:
Role id will determine the next status
The program will check the organizational Structure to Pick the Appraiser, Reviewer and Approver and Create the Appraisal Documents. Appraisal Document Header data will get updated as per the Available Roles in the template.
In my next blog planning to write a detailed Template configuration steps.
Thanks