Record Dropped From Last of Multple HIPAA 834 EDI Transaction Sets When It Should Contain the Maximum Members
(Doc ID 2950961.1)
Last updated on FEBRUARY 05, 2024
Applies to:
PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
On the run control for creation of the HIPAA 834 EDI file, the Max Members in Transaction Set is set to a number that will divide members equally among the transaction sets. When the last set is equal to that maximum, a record is dropped.
Steps to reproduce the issue:
1. Configure an EDI Trading Partner (Navigation: Set Up HCM > Product Related > Base Benefits > EDI Trading Partners).
2. Run the Benefit Enrollment Snapshot (Navigation: Benefits > Interface with Providers > Refresh Benefit Snapshot).
3. Create the HIPAA 834 file with the Max Members in Transaction Set set to equally divide members among multiple transaction sets (Navigation: Benefits > Interface with Providers > Create HIPAA EDI 834 File).
4. In the last transaction set, see that it is missing an employee.
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 |