This is quite basic bug that needs to be fixed ASAP.

Concern: Import is getting failed for 'YYYYMMDD' data format

Cause: Import do support 'YYYYMMDD' date format. While working on generic solution to create users, we have added a new function in system, that stores newly added employees in a table in format of key-value pair. Here employee id is considered as key and effective date is considered as value. This data is getting used later for further enrollment data processing. Though, in file we allow different types of date formats, internally we use MM/DD/YYYY format for calulation. So, while storing data in table we convert all types of dates in MM/DD/YYYY format. For this conversion, we use default .net function. However, this function requires 10 characters length for date. Since, YYYYMMDD has only 8 characters it is throwing exception.

Correction: We have to change the code to format data in correction format.

Please note: We understand that this very basic bug. However, this will require a code change and we will have to go through entire deployment process, we would need development and deployment approval for this. Could you please take this up with Jennifer Reed and Nagini Indugula, so that we can plan the resolution as soon as possible.

Hi All,

Attaching the development approval email for your reference

Regards
Gaurav

Attached test cases Testcases.xls

File Changed:
1) D:\WT\branches\UiRefresh\App\BusinessLogic\ImportExportDTS\ImportValidation.vb

We need it on Prod ASAP as the client is waiting for it.

Hi Snehal Katkar,

Verified on LB
Company - ASML

Verified scenarios are attached in test cases
For below scenarios import is getting fail when date format in setting is YYYYMMDD :
1) Not mapping employee effective date. EmpEffectiveDate.txt
2) Mapping employee effective date but passing value as blank or ~
3) For enrollment effective date ElectioneffectiveDate.txt
4) For Waive effective date WaiveDate.txt
5) For Paycheck effective date
Other scenarios its working fine

Hence re-opening this jira.

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise Hrishikesh Deshpande Jaideep Vinchurkar

Hi Jayshree Nagpure,

I have changed the code for ElectionImport and WaiveImport. It's working fine now. Please take it ahead for testing.
However, issue of paycheck import is not related to effective date format. Hence, did not consider it under this ticket.

cc: Rakesh Roy, Jaideep Vinchurkar

Hi Snehal Katkar,

Employee import is getting fail for "YYYYMMDD" when initial load is YES
Also election and waive scenario which are mentioned in updated test cases are not working .
Error log is same as attached in jira

Re-opening this jira

Hi Jayshree Nagpure,

1) Considering scope of this issue, I have tested all the scenarios mentioned in the document related to 'Demographics Import' and they working as expected.
File changed - ImportValidation.vb

2) The scenario which got failed for 'Election Import' is an existing issue and not because of this code change. Please open a separate ticket for it.

3) Mentioned test cases for 'Waive Import' are working fine. No code change required.

Jayshree Nagpure, we will not be opening separate ticket for election import. We will fix in this ticket

Verified for employee Import
Company - QA ASML
Employee import "YYYYMMDD" when initial load is YES - scenario Working fine

After today's build will verify election import scenario, and will regress for all types of import.

Thanks,
Jayshree

cc : Prasad Pise Sachin Hingole Rakesh Roy Hrishikesh Deshpande

As per our analysis this is not an issue on Stage and Prod for now. We'll confirm this tomorrow.

We analyzed the issue from election import point of view, it is failing for very specific scenario, where effective date given in file is less than hire date of employee and date format of template is YYYYMMDD. We can fix this right now, but will need more time for unit testing. So as of now, we should go ahead with demographic import fix as many clients are waiting for it. And for election import, we can consider this issue in import restructuring where EDI team expecting date format rationalization (WT-8876).
Also, We found this is less likely scenario to happen. We scanned all companies on production using YYYYMMDD date format for election import and found a very few are using it currently.

So assigning this back to QA

Hi All,

Attaching the stage and production deployment approval email for reference: Unable to embed resource: FW Hot Fix and Development Approval Request.msg of type application/octet-stream

Also, i have attached the email which states that we will be deploying only the Demographics import issue for now and will be taking up election import as part of Import module restructuring initiative

Regards
Gaurav

Jayshree NagpureSuraj SokasaneJaideep VinchurkarSatyaSamirRakesh RoyJennifer ReedNagini IndugulaAbhay Patil

Hi Suraj Sokasane,

Verified on stage
Company - ASML for hspl

Verified only for demographics import
PFA : FinalUpdatedTestcases.xls
Verified for syn and async mode
Verified with Initial load Yes/No
Not considered any other import type.

Working fine, Marking item state as Ready for production.

Thanks,
Jayshree

cc : Rakesh Roy Prasad Pise Hrishikesh Deshpande Snehal Katkar

Question regarding comment by Suraj Sokasane - You have said the following.
_... from election import point of view, it is failing for very specific scenario, where effective date given in file is less than hire date of employee and date format of template is YYYYMMDD.
... . We scanned all companies on production using YYYYMMDD date format for election import and found a very few are using it currently._

I want to understand the following.

• Will YYYYMMDD format always fail for election imports - or will it fail only under the specific scenario you mentioned?
• When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? How many companies did you find?
  CC Cindy Wibbing Gaurav Sodani Jayshree Nagpure Jennifer Reed

Hi Abhay Patil,

Below are the answers:

• Will YYYYMMDD format always fail for election imports: No, election import won't fail always. It'll fail only in the specific scenario mentioned above.

• When you say you found "a few companies using YYYYMMDD format for election import" - do you mean that those imports will fail? : Yes, but as per the first answer above, only for the specific scenario and not always.

• How many companies did you find? : I'm attaching an excel sheet which contains data - Company name, Template name and number of imports on that template in 2017 till now. Here it is : WT-12252 Data.xls

Hope this successfully answers your queries. Please let us know if you know more details on same.

Hi All,

This Fix is Deployed and Tested on Production. This is working as expected for all date formats.
Closing this JIRA.

Thanks,
Hrishikesh.