Candidate Selection Workflow – Taleo

•CSW provides the framework to move candidates through the hiring process
•A CSW includes steps, statuses, and actions a recruiter must go through before hiring a candidate.
•CSW can be associated with Organizations, Locations, Job Fields
•CSW can be associated with Requisition Type
Navigation

Configuration–>Recruiting–> Administration–> Process –>Candidate Selection Workflow

 

Screen Shot 2018-04-10 at 5.59.55 PM

 

 

Screen Shot 2018-04-10 at 5.47.21 PM

 

Screen Shot 2018-04-10 at 5.47.55 PM

 

Screen Shot 2018-04-10 at 6.01.27 PM

Screen Shot 2018-04-10 at 6.01.55 PM

 

Screen Shot 2018-04-10 at 6.02.18 PM.png

 

Screen Shot 2018-04-10 at 6.02.46 PM

Screen Shot 2018-04-10 at 6.03.15 PM.png

Screen Shot 2018-04-10 at 6.03.35 PM.png

 

Advertisements

Error in Global Deployment Between same source and Destination BGs multiple times

When we try to do Multiple Permanent GD between the same source and destination BGs, an error is encountered

You cannot initiate this deployment because the employee is already deployed on the proposal start date.”

 

The cause of this issue is previous Permanent Deployment Proposals are not end-dated and end-dating the Permanent Deployment Proposals is not currently supported by Global Deployments functionality.

While end-dating the records from the back-end is not advisable/supported, we can delete the previous permanent deployment proposal for that person between the same source and target business groups as a work around

when we want to deploy a person more than twice or thrice between the same source and target business groups.

Also, this is only a work-around and not a solution.  This is because History will be lost if the earlier proposal is deleted from the application.

 

OR

Adding Final Process Date to the first Country would work.

Person type query

select
papf.full_name,
papf.business_group_id,
papf.start_date “Joining_Date”,
papf.effective_start_date,
papf.effective_end_date,
–papf.person_type_id,
ppt.user_person_type
from apps.per_all_people_f papf ,
per_person_type_usages_f pptu,
hr.per_person_types ppt
where papf.employee_number =’6674′
and papf.person_id = pptu.person_id
and papf.person_type_id = pptu.person_type_id
and pptu.person_type_id = ppt.person_type_id
–and pptu.effective_start_date between papf.effective_start_date and papf.effective_end_date
order by trunc(papf.effective_start_date)

Query for employee, element , entry value and input entry value

SELECT distinct
PETF.ELEMENT_NAME “Element Entry Name” ,
pivf.name “Input value”,
PAPF.FULL_NAME “Employee Name”,
PEEVF.EFFECTIVE_START_DATE “Entry Start Date” ,
PEEVF.EFFECTIVE_END_DATE “Entry End Date” ,
PEEVF.SCREEN_ENTRY_VALUE “Entry Values”
FROM
PAY_ELEMENT_TYPES_F PETF ,
PAY_ELEMENT_LINKS_F PELF ,
PAY_ELEMENT_ENTRIES_F PEEF ,
PER_ALL_ASSIGNMENTS_F PAAF ,
PER_ALL_PEOPLE_F PAPF ,
PAY_ELEMENT_ENTRY_VALUES_F PEEVF ,
PAY_INPUT_VALUES_F PIVF
WHERE 1 = 1
AND PELF.ELEMENT_TYPE_ID = PETF.ELEMENT_TYPE_ID
AND PEEF.ELEMENT_TYPE_ID = PETF.ELEMENT_TYPE_ID
AND TRUNC(SYSDATE) BETWEEN TRUNC(PEEF.EFFECTIVE_START_DATE) AND TRUNC(PEEF.EFFECTIVE_END_DATE)
AND TRUNC(SYSDATE) BETWEEN TRUNC(PIVF.EFFECTIVE_START_DATE) AND TRUNC(PIVF.EFFECTIVE_END_DATE)
AND PAAF.ASSIGNMENT_ID = PEEF.ASSIGNMENT_ID
AND TRUNC(SYSDATE) BETWEEN TRUNC(PAAF.EFFECTIVE_START_DATE) AND TRUNC(PAAF.EFFECTIVE_END_DATE)
AND PAPF.PERSON_ID = PAAF.PERSON_ID
AND PAPF.CURRENT_EMP_OR_APL_FLAG = ‘Y’
AND TRUNC(SYSDATE) BETWEEN TRUNC(PAPF.EFFECTIVE_START_DATE) AND TRUNC(PAPF.EFFECTIVE_END_DATE)
AND PEEVF.ELEMENT_ENTRY_ID = PEEF.ELEMENT_ENTRY_ID
AND PIVF.INPUT_VALUE_ID = PEEVF.INPUT_VALUE_ID
AND paaf.primary_flag = ‘Y’
AND paaf.assignment_type = ‘E’
AND TRUNC(SYSDATE) BETWEEN TRUNC(PEEVF.EFFECTIVE_START_DATE) AND TRUNC(PEEVF.EFFECTIVE_END_DATE)
AND PETF.ELEMENT_NAME = ‘ESPP’
and papf.business_group_id = 96;

Business group query

SELECT o.organization_id,
       o.organization_id,
       otl.NAME,
       o.date_from,
       o.date_to,
       o.internal_address_line,
       o.location_id,
       o.comments
  FROM hr_all_organization_units    o,
       hr_all_organization_units_tl otl,
       hr_organization_information  o2,
       hr_organization_information  o3,
       hr_organization_information  o4
 WHERE o.organization_id = otl.organization_id
   AND o.organization_id = o2.organization_id(+)
   AND o.organization_id = o3.organization_id
   AND o.organization_id = o4.organization_id
   AND o3.org_information_context = 'Business Group Information'
   AND o2.org_information_context(+) = 'Work Day Information'
   AND o4.org_information_context = 'CLASS'
   AND o4.org_information1 = 'HR_BG'
   AND o4.org_information2 = 'Y';

Changing front end password using script

Following script can be used for changing the password of a user:

select fnd_web_Sec.change_password(‘PRAY‘,’Welcome1234’) from dual;

 

Following block can be used to assign the user with the responsibilities from backend:

BEGIN

    fnd_user_pkg.addresp(

        ‘PRAY’,    ‘SYSADMIN’,  ‘SYSTEM_ADMINISTRATOR’,    ‘STANDARD’,

        ‘Add Responsibility to USER using pl/sql’,  SYSDATE,

        SYSDATE + 100   );

    COMMIT;

    dbms_output.put_line(  ‘Responsibility Added Successfully’

    );

EXCEPTION    WHEN OTHERS THEN

        dbms_output.put_line(

            ‘ Responsibility is not added due to ‘ ||  sqlcode    ||  substr(

                sqlerrm,     1,100)

        );

        ROLLBACK;

END;

/