Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
New Assignment Before Position Synchronization Data
Summary
After Position Synchronization data generate (for change of manager), Promotion data get Approved but with Effective Date earlier than the Synchronization dataContent
How we should do with this kind of transaction
Before Promotion Data Approved :
1. 1 Oct 2019 - Position Synchronization - Admin Data Management Staff
2. 1 Apr 2019 - Promotion - Admin Data Management Staff
After Promotion Data Approved :
1. 1 Oct 2019 - Position Synchronization - Admin Data Management Staff
2. 1 Sep 2019 - Promotion - Admin Data Management Supervisor
2. 1 Apr 2019 - Promotion - Admin Data Management Staff
With this kind of behavior, we need to manually changed the Position for 1 Oct 2019 data.
Is it an expected behavior? Can we just enable Position Synchronization only for Future Date. What is the best practices for this kind of transaction?
Tagged:
0