Check if an Employee is attached to FND_USER record?
If yes, then run the below query
SELECT status, start_date, parent_orig_system_id AS user_id
WHERE parent_orig_system LIKE ‘FND_USR’
AND NAME = ‘PRAY’ ;
If no record is returned, but you still have FND_USER record, then run the process:
Synchronize WF LOCAL tables
•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
Configuration–>Recruiting–> Administration–> Process –>Candidate Selection Workflow
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.
Adding Final Process Date to the first Country would work.
from apps.per_all_people_f papf ,
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)
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”
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 ,
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;
FROM hr_all_organization_units o,
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';
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:
‘PRAY’, ‘SYSADMIN’, ‘SYSTEM_ADMINISTRATOR’, ‘STANDARD’,
‘Add Responsibility to USER using pl/sql’, SYSDATE,
SYSDATE + 100 );
dbms_output.put_line( ‘Responsibility Added Successfully’
EXCEPTION WHEN OTHERS THEN
‘ Responsibility is not added due to ‘ || sqlcode || substr(