Hi Jennifer Leugers,
CONCERN:
When try to import the correction , the bad files are saying the # of fields do not match.
CAUSE:
In template (WT system) customization, there was a EIN field column present which you need to provide either blank value or valid value against EIN column in import file and as per customization, import file should have header which was not in your file.
CORRECTION:
To resolve a concern we followed as per below points.
1. In import file has been added header row.
2. From template customization has been removed EIN field.
3. Data transformation has been done for member type in Part 3 template.
After expected changes done in template customization, we occurred below issues while importing
1. In the file was provided a wrong SSN for the employee, we set the correct SSN for the employee by taking the reference of Member SSN & corrected in the file
from wrong SSN-5481173571 to correct SSN-548173571
2. While Importing part-2 correction, we get a bad record file for the employees 6049X2X63, 5559X9X38 for the error of Invalid code for 1H,2G and for 569XX93X7-invalid code-1A/2A .
Hence we changed in the file for those employees as 1H,(Blank) and 1A,(Blank) respectively.
Please find the below run details which we run after correction import on Main Production Company..
Report run time-1/2/2018 3:42:18 AM
We have corrected the files & imported using this Corrected Files.zip
file.
Password will be sent in mail.
Thanks,
Revan
CC- Ramya Tantry, Kumar Chhajed, Nandkumar Prabhakar Karlekar, Smita Pawar, Sachin Hingole,Gaurav Sodani
Please change dates to the 2017 calendar year (1.1.17 - 12.31.17) and group is ready to run. Thanks!