-
Type:
Bug
-
Status: Production Complete
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BenAdmin
-
Labels:None
-
Environment:Production
-
Bug Type:Functional
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:Harbinger
-
Company:Wacker Neuson Corporation
-
Item State:Production Complete - Closed
-
Sprint:WT Sprint 36 - Bugs
Template Name: Employee Ongoing New Hires
Error Log: Import FailureExecuteImportDTS.AutomatedImportFile->ImportValidation.ImportData->ImportValidation.GetImportExportFieldsData An entry with the same key already exists.
Getting reproduced for manual import.
Needs to be taken on priority as next import will be failed.
Hi Vishal Bajad,
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
Working fine
Hence marking item state as Ready fo stage
Thanks,
Jayshree
Jayshree Nagpure (Inactive)
added a comment - Hi Vishal Bajad ,
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
Working fine
Hence marking item state as Ready fo stage
Thanks,
Jayshree verified on stage
Company - ASML for hspl
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
5))Marked Date of Employee as required - pass date of Employment as blank - Pass
Working fine
Hence marking item state as Ready fo Production
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - verified on stage
Company - ASML for hspl
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
5))Marked Date of Employee as required - pass date of Employment as blank - Pass
Working fine
Hence marking item state as Ready fo Production
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise verified on Production
Company - ASML for hspl
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
5))Marked Date of Employee as required - pass date of Employment as blank - Pass
Working fine
Hence marking item state as Production complete
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise
Jayshree Nagpure (Inactive)
added a comment - verified on Production
Company - ASML for hspl
Verified below scenario :
1)Marked Date of Employee as required - Pass
2)Mapped DOE with DOE and Effective date - Pass
3)Marked all mandatory field as Is Required for Demographics import - Import done successfully
4)Also verified Spouse and Child data with "IS required" as YES - Pass
5))Marked Date of Employee as required - pass date of Employment as blank - Pass
Working fine
Hence marking item state as Production complete
Thanks,
Jayshree
cc : Rakesh Roy Prasad Pise 
Hi Vishal Bajad,
we do not required code change here. Here employee full name field was mapped as second field, which is a export field and should not be shown in import mapping screen.
we have WT-11192 for such fields. Please revert your changes. If scenrio mentioned by Jayshree Nagpure is working with valid import field. no code fix is required for this issue.