The issue arises when attempting to change the legal employer hire date of a line manager from 1st February 2021 to 1st January 2021 in Oracle HCM. The system throws an error: "You can’t select this date because some assignments in the work relationship are used in a manager relationship. Remove the manager relationship to continue. (PER-1531839)"
Activate a sandbox Go to the Personal Details page Edit Page Composer Select the below component and edit it
We are getting a warning message when we click on the "Close" button under the Manage Employment page. And we are getting this warning after 20A, so we are not sure it happens because of an update or it’s an issue.
There are some steps to fix this issue.
When you are not able to find your created position under employee assignment then you need to check the employee business unit and the position business to which is you want to assign an employee it should be the same and another one is the effective date employee assignment effective date is always is greater than position created date.
There is a role called Human Capital Management Integration Specialist that we need to assign to the user in order to access the data exchange task.
We have terminated an employee with an attached document but when we are trying to download it from the transaction console then we are getting an error message "The file was not downloaded or was not downloaded correctly" then we have identified that we were attaching a blank word document, then again we have added some contents in the document and tried to download then it's downloaded successfully.
1. administrator login to BPM worklist for task configuration 2. click on 'Task configuration' 3. Search for 'Termination' 4. click on 'TerminationsApproval' 5. click on the pencil icon. 5. Click On 'Configuration' 6. Set 'Task Aggregation' as none
This option was removed from the Person Security Profile back in Rel 12 for performance reasons. I can't find the exact release readiness documentation link, but this change was documented. Please note the additional duty role that can be added.
Navigate to the Setup and Maintenance. Search for the Manage Administrator Profile Options. Search for the profile option PER_LOV_SEARCH_DEPARTMENTS_STARTSWITH Change the Site Level value from N to Y. Save and Close.
Reason/Root Cause: Kindly Check for all the Child Records for Employment and Personal Details. Example: Salary, Payroll Relationship, Element Entries, DOR, AOR etc.
You cannot deselect using the HCM Position Hierarchy because the line manager is synchronized from the position hierarchy. (PER-1531935)
A user wants to change the legal employer hire date from 1st Feb 2021 to 1st Jan 2021, but they are not able to change the hire date of an employee.
FUN-720323A scope value was not selected. Return to the task list and use an implementation project to select a scope value prior to selecting the task.
The assignment ID does not exist. (PER-1531229) Failed to validate a row with key oracle.jbo.Key[300000000000000 ] in AssignmentResponsibility
We need to run the required schedules process which is Synchronize Person Assignments from Position
Issue: There is an employee for that client who wants to update the hire date of an employee and they are getting below error. Error Message: You can't select this date as assignment having number E4663 is used in manager relationship. Remove the relationship or select a date that's before 18-Apr-2022
Step 1: Navigate to Tools > Transaction Console Step 2: Clear all the selected filters, including the status filter. Step 3: Change the "Transactions From" range to "9 Months" or more. Step 4: Enter the keyword in the search box like transaction name or employee username Step 5: Now select Status one by one
There are 2 options that we need to check. 1. We need to run the scheduling process and the process name is "Synchronize Notifications in Global Header" 2. The issue was caused by the notifications override being set under BPM Worklist Administration.
I have investigated and found that this is not related to only document records, it is happing for all approval where we have configured the conditions. When the approval is set to Auto Approve, an approval task is in progress status. So, there is a delay between submitting the transaction to completing the transaction. Hence users see that message displayed.