Appraisal Objects created in 'Approved' Planning status

Question

Good day,
When creating Appraisal Template objects, they are created in 'Approved' Planning Status. We want them created in 'Active' Planning Status. We suspect this is the reason why we can't configure/define the process configuration for our template under IMG path: Personnel Management > Personnel Development > Objective Setting and Appraisals > Define Tabs and Process Configuration for Template. The system gives the following error message: "No process defined for form <template name>"
We've tried using program RHAKTI00 to make these objects (VA VB VC) active but are facing a further issue that it makes appraisal template unreleased. Vice versa when i released the template, it makes objects planning status to reset to approved from active. A similar issue has been posted in the below thread but an answer was not provided.
Objects created in 'Approved'  Planning status
Kindly assist.
Best regards
Hardus

Answer 1

>
Chris Thomas wrote:
> Michael - thanks as always for your insight and willingness to help out.
>
> Let me explain further.  Duke currently has a third party performance management system that allows the users to manage their Expected Job Results (EJR) in a catalog (translate to Qualifications catalog in R3).  In a separate step, the manager can select a single EJR and on the other side of the screen select all , or a subset of their employees to assign the EJR to.
>
> Extrapolate this to SAP PM.  We have created a Criteria group in our template and have experimented with adding qualifications via the BADI and this works fine EXCEPT that the manager would have to do this in each employee's appraisal, individually.  We are developing the tool to build and maintain the qualification catalog and assign to the employee via Manager Self Service, we are hoping to be able to facilitate the assignment of the EJR/Qualification into the employee's appraisal template.   The EJR's (Q objects) will be associated to a quadrant in their catalog: QK's - Clinical Quality, Customer Service, Finance and Work Culture
>
> The criteria group, Expected Job Results, has for criteria groups nested under it:  VB objects for four quadrants, Clinical Quality, Customer Service, Finance and Work Culture.   SO, we get to the crux of the matter.  Since we know the employee, we can get to the appraisal document and associated data in the tables.  The decision of which VB to go to is what we are trying to facilitate.  The textual names will be the same for the quadrants in the QK's and VB's BUT thats a bad way to try to make a decision, thus the thought to create a relationship between the QK and the associated, logically equivalent VB.  
>
> The issue comes up with some of our managers who have large (60+) direct reports so the thought of creating qualifications from the appraisal side, individually per employee does not work.  This is why we are thrashing around with trying to start outside and work our way in.  Make sense ?
>
> Chris Thomas
Hi Chris,
This is what I was trying to explain between free vs fixed enhancement. 
Free enhancement - user selects from a list to add something to the template
Fixed ehahcement - preloads data into the template
If your application that you build in MSS assigns the qualifications to the employees, you have a number of options to make this work as fixed enhancement.
First use the following fixed enhancement as your basis: 
HRHAP00_ENHANCE_FIX1 - Fixed Enhancement - Add Position Requirements
Now in your MSS application if you assigned the qualifications to the position and wanted all qualifications to show up in 1 criteria group, you can use this enhancement with no development. 
qualifications assigned to positions or jobs are called requirements
qualifications assigned to employees are called qualifications
if you have like 10 qualifications assigned to the position and 4 need to go to clinical quality VB, 3 need to go to finance vb criteria groups, you will create a BADI for each one of those, each criteria group wiill have its own unique badi.  in the badi you will apply the filter after all "requirements are selected from position" so that only the 4 belonging to the qualification block for finance are loaded into that VB. 
if your mss application MUST assign it the employee for business reason, you use the same logic except swap out position lookup with employee lookup. 
are we closer?