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.
Best Practice for Managing Time Periods in Fusion
Summary
Interested in knowing how others manage time periods when set up incorrectlyContent
We are migrating away from a EBS Coexistence model to fully using Fusion. Currently in Fusion, the payroll time periods were created incorrectly (dates are wrong). We would like to change them, but can only modify the Cutoff Date, Date Earned, Payroll Run Date, etc. - not the pay period dates. Since we have element entries already due to existing coexistence data from EBS, we want to make sure we don't mess it up.
What would you recommend us doing? Should we create a new version of our biweekly payroll with brand-new time periods, or is it even a possibility to log an SR to ask Oracle Development to fix the dates?
Tagged:
0