-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ACA
-
Labels:None
-
Environment:QA
-
Module:ACA - Reports
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
Company Name - ACA Automation
Export Template - Sachin - BSG Export
COVG|200000016| |01/01/2016||BSG plan Three|1|1|122.00|248.00|01/01/2016||Yes|Yes|Yes|BSG plan Three|BSGPlanThre_OLD|BSGPlanThre_OLD|01/01/2016|200000016
Step :-
1.Add EE+SP with Classes Eligibility
Class 1 – BSG C
Class 2 – BSG F
Employee EIN = 222222222
2.Add Export Template
3.QE - In Jan 16 -Event date and (Effective Date Rule - Event Date) are same. Enrolled into BSG plan Three
4.Export File for Month Feb 16 - from date 02/01/2016 to date 02/26/2016 and click on Export
5.Download file
Screen Shot - DTS_Medical Plan Coverage Level Code , Medical Plan Coverage Level Description.jpg
COVG - Incorrect Medical Plan Coverage Level Code , Medical Plan Coverage Level Description value.jpg
Actual - "1 " value display for Medical Plan Coverage Level Code , Medical Plan Coverage Level Description field in COVG tag
Expetced - "EE + SP" should be display for Medical Plan Coverage Level Code , Medical Plan Coverage Level Description field
- is caused by
-
WT-2601 BSG ACA Reporting
-
- Closed
-
Company - ACA Automation
We have regressed this issue on LB and observed that issue still exist.Hence reopen the same.
Please refer attached BSG export file for more info.
This issue is fixed. As we have changed fields that need to map with coverage level code field.
Yogesh Chaudhari (Inactive)
added a comment - - edited This issue is fixed. As we have changed fields that need to map with coverage level code field. Company - ACA Automation
We have regressed this issue and observed that issue does not exist.Hence marking ready for stage.
Rakesh Roy Nandkumar Prabhakar Karlekar Sachin Hingole
Hi,
As per yogesh comments in the JIRA, there is not required to code checkins for this jira either for stage or production.
Regards,
Revan
This issue is not reproduce. As we have not make any changes in code. we are using existing code.