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.
Benefits - Make SSN required for dependents only, not contacts or beneficiaries
We went live with Oracle this January. Previously our benefits application allowed us to collect SSN only for those dependents covered by insurance, so when we went live with Oracle we had SSN set to be optional. However, once we went live, several new employees enrolled in our benefits in Oracle without providing dependent SSNs which caused errors on integration files. We have now changed course and asked our implementation partner to make SSNs required, which they’ve done. This update has caused SSNs to become required across the whole HCM system, including for contacts. We would like to only require
Tagged:
0