Affordable Care Act (ACA) Employee Transmittal Data Insert Does Not Populate BIRTHDATE on the ACA_EMPLOYEE Record for a new Effective Sequence Row.
(Doc ID 2829579.1)
Last updated on AUGUST 22, 2023
Applies to:
PeopleSoft Enterprise HCM Benefits Administration - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
When inserting a new row for an employee in order to make changes to ACA employee Transmittal Data, BIRTHDATE is not carried forward to the new effective sequence row in the ACA_EMPLOYEE record.
Steps to Replicate:
- Run the ACA Data Extract process for an employee. Navigation: Benefits, ACA Annual Processing, Create ACA Form Data, ACA Data Extract.
- Insert a new Employee Transmittal Data row and save. Navigation: Benefits, ACA Annual Processing, Create ACA Form Data, ACA Employee Transmittal Data.
- Query the ACA_EMPLOYEE record showing the new EFFSEQ row does not populate BIRTHDATE.
NOTE: This does not cause ACA Reporting concerns as the birthdate that is stored in ACA_EMPLOYEE is not currently used. The birthdate in ACA_DEPENDENT is the one used for ACA reporting which is populated when a new row is inserted.
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 |