Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Running Prepare Enrollment Batch in Workbook is removing enrollments

Summary: Running Prepare Enrollment Batch in Workbook is removing enrollments that are not part of the load


Content (please ensure you mask any confidential information): Client has an Unrestricted Program. Plan Types are 401a and 457. Trying to upload rate changes under the 457 only via the spreadsheet loader and it is completely removing the existing enrollments under 401a. When using the same Life Event via the UI, the 401a enrollments are retains properly. The same removal occurs if load is done by HDL that occurs with the spreadsheet loader. Ideally, there is no point in including the same 401a enrollments as there are no changes being made to it. Plus additional rows impact processing time. Is this standard Oracle behavior?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!