-
Type:
Support Activity
-
Status: Closed
-
Priority:
High
-
Resolution: System Behaviour
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Support Task Type:Configuration
-
Environment:Production
-
Reported by:EDI
-
Company:JE Dunn
-
Module:BenAdmin - Import
-
Severity:Simple
Company JE Dunn
Import template: Employee_Ongoing_Terms
Remote Directory: jedunn/inbound
Inbound file name: WT_TERMS.csv
Run Date: 12/20/2017
The termination for Clyde Rowe was not processed on 12/20/2017, there is no 'bad file' visible for 12/20/2017.
There is an invalid phone number for Clyde Rowe, a 'bad file' was expected.
The remaining terminations in the 12/20/2017 file did process successfully in Workterra at the date/time the file processed in workterra on 12/20/2017.
When the issue was discovered, the record for Clyde Rowe was processed in a new inbound file on 1/25/2018 , and a 'bad file' was created on 1/25/2018 as expected. The 'bad file' for 1/25/2018 processed successfully.
Please check to see what happened on 12/20/2017 for when the inbound termination was processed. An explanation is needed for the client.
Hi Rochelle Thomas,
We have checked inbound file of 12/20/17. The termination for Clyde Rowe was not processed on 12/20/2017 and bad file was created for this with reason i'e 'Home Phone: Invalid Length '. Pleas find below snap of bad file which was created on 12/20/2017.
Please refer Bad_WT_TERMS12_20_2017 12_33_35 PM.csv to download bad file.
Thanks,
Ganesh
The JE Dunn Inbound file of Terminations processed all in the file except for one record on 12/20/17 - there should be a 'bad file' for 12/20/17; What happened during the inbound processing of the Terminations file WT_TERMS on 12/20/2017?
CC:Andrea Dennis, Kevin Walker, Cindy Wibbing