Non-ANSI 834 Benefits Extract Records Are Not Sorting Properly
(Doc ID 2890913.1)
Last updated on JANUARY 29, 2024
Applies to:
Oracle Advanced Benefits - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior:
When running a custom Full System Extract file (not the ANSI 834), sorting is not occurring according to expectation.
Instead - certain people have one plan that sorts out of order on one run, and on the next run nothing is out of order.
Uncertain what is causing this.
We see the following:
210 Record (for plan 1)
999 Record
999 Record
999 Record
210 Record (for plan 2) ** Mis-sorted
If Plan 3 is encountered - everything sorts correctly:
210 Record (for plan 1)
210 Record (for plan 2)
210 Record (for plan 3)
999 Record
999 Record
999 Record
Expected Behavior:
Expect the sorting to occur according to sequencing on the file layout panel, and according to the Sort Sequence setup.
Record 210 should come before any record 999, as 210 is sequenced before the 999 record.
Example of expectations below:
210 Record (for plan 1)
210 Record (for plan 2)
210 Record (for plan 3)
999 Record
999 Record
999 Record
If plan 3 is not encountered, we expect the following:
210 Record (for plan 1)
210 Record (for plan 2)
999 Record
999 Record
999 Record
Steps to Reproduce:
1. Navigate to US Super HRMS Manager > Mass Information eXchange > System Extract > Extract Layout
2. Put together record sequencing in order by sequence.
3. Also define the sorting by person level first, then plan type data element in the sorting panel.
4. Check the remove duplicates checkbox as well for the 999 record sequence.
5. Now run the extract and review results
- Sorting is occurring properly for most people.
- But for combinations of certain plans on new hire events only it is not working
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |