New hire PMPs - how to publish for certain target groups

Publishing plans for certain groups of people only is very difficult if not impossible in Oracle Talent Management 12.0.7 and earlier.

I have already in a earlier blog post indicated how we can setup that a PMP goes only to certain people.

Now further, if you are using Objectives & Objectives library though it maybe possible to restrict whose scorecard will have valid objectives and whose doesnt. This in a sense can functionally restrict whose scorecard can get appraised by the supervisor and whose scorecard cannot be.

Objectives in the Objective library are linked to employees via eligibility profiles. Eligibility profiles can be defined based on many many parameters including date of hire, date of joining etc...now if you setup such a eligibility profile say only those whose 'length of service' should be minimum 6 months atleast and link it with an objective then a PMP which includes this objective will have scorecards with objectives only if the employee has been in the org for 6 months atleast.

how to restrict a PMP for just specific people in the hierarchy

Here is a tip for those working with Talent Management . It looked like there was no way to publish a plan just for a specific person using PMP. So for example new hire cases used to be a pain right ?. And invariably one would have to customize for this.

There maybe a simple functional workaround for this.

SUP_ASG hierarchy type of PMP will create scorecards and appraisals only if the worker assignment number of the supervisor is in place. So if you want to publish a plan just for a specific person(s) in the hierarchy you should setup their assignment record with worker assignment number of the supervisor ( there are two assignment numbers in the assignment screen) and publish a PMP of type SUP_ASG. This plan will appear only for those specific people now.

HR issues in project management - when not to let go of an employee

If a popular employee or a intelligent person in the group is to let go, the effect seems to be that credibility of management goes down bcos it gives out the sign that management did not want to hear such a person.

Considering the psychological effects of letting go of a person or, in general, of any decision is very crucial to the success of the decision.

People see trends in everyday occurences.

Republishing a PMP

Problem in republishing PMP v 12.0.6 :

If Appraisals are created and then PMP is republished then scorecards cannot be edited bcos an appraisal id is already created.

Hence a good practice is to avoid resetting appraisal dates : have a good gap between the objective setting period and appraisal start date if possible

quirks in implementation

The problem in implementations comes not from business rules but rather from the exceptions that users want to have to the rule. eg...HR specs that a manager shud be able to view only his hierarchy. No problems. But then the manager for many reasons does not make changes themselves so they give access to their secretary or second level leadership to do the menial jobs.....that is where issues start coming in....

pride goeth before a fall

There is nothing wrong with learning new stuff in apps. But what is shortsighted is to not share it with anyone and becoming proud of your niche. Some other fellow who knows more than you will come along and that will be the day you meet your maker.

code to get the supervisor id and employee number for certain employee numbers

select ppf.employee_number,

---code to get supervisor's emp number

(select employee_number sup_number from per_all_people_f ppf

where ppf.person_id = paaf.supervisor_id

and TRUNC(SYSDATE) BETWEEN ppf.effective_start_date AND ppf.effective_end_date

) super_number,

paaf.last_update_date,

paaf.effective_start_date , paaf.effective_end_date

from per_all_assignments_f paaf, per_all_people_f ppf

where TRUNC(SYSDATE) BETWEEN ppf.effective_start_date AND ppf.effective_end_date

AND TRUNC(SYSDATE) BETWEEN paaf.effective_start_date AND paaf.effective_end_date

and paaf.last_update_date = (select max(paaf.last_update_date) from per_all_assignments_f paaf where paaf.person_id = ppf.person_id )--and ppf.employee_number = 2794

and ppf.person_type_id in (1120,1121)

AND ppf.person_id in ( select ppf.person_id from per_all_people_f ppf where ppf.employee_number IN (

2796,2794,2791,2797,2784,2799,2801,2802,2803,2806,2800,2815,2819,2818,2823,2824,2829,2825,2827,2836,2841,2833,2112,2830,

2843,2831,2845,2839,2832,2848,2828,2847,2844,2849,2846,2850,2852,2854,2853,2858,2855,2856,2851,2862,2863,2857

)

)

and paaf.person_id = ppf.person_id

order by ppf.employee_number