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.
Termination Life Event - coverage not ending when global transfer happens
Summary
Coverage should end with termination life event, then restart with global transfer life event triggered. Coverage not ending.Content
Client has a requirement that when a global transfer happens, previous coverage ends, and new coverage begins at the beginning of the month.
Example:
Global transfer is entered on 12/15/19, with an eff date of 12/8.
Termination life event is triggered.
New Hire life event and Global Transfer life events are triggered.
When the next evaluate life event process runs at night on 12/15, the termination life event is processing, but not end dating the benefits.
New Hire life event and Global Transfer are picked up in next process. And these collapse into each other, working just fine.
Tagged:
0