-
Type:
Enhancement
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ACA
-
Labels:None
-
Module:ACA - 2017
-
Reported by:Support
-
Item State:Production Complete - Closed
-
Issue Importance:Must Have
Same like Eligibility, user can define the population which needs to be processed for multi employer transition relief.
Note: Need to check on a monthly basis, if the employee is falling under the defined population, then only need to process the non calendar transmission relief.
- relates to
-
WT-5020 ACA_1H-2E automation enhancement_Validation is not working properly on 1095-C report
-
- Closed
-
Changes done are -
1) Exposed new Eligibility Drop down on IRS 1095C Reports named - Eligibility Rule for Multi Employer
2) After selecting the rule, the employees which fall under those criteria will get '1H' on Line 14 and '2E' on Line 16 for that particular month.
3) If the employee has by default code 1H on Line 14 and 2A or 2D on Line 16 combination then their codes will not be updated.
We have verified above mentioned enhancement on LB company [ACA Automation].
Its working fine.
Attaching test cases for enhancement.
Note:We have not checked the impact on other codes now as we will cover same in regression testing after 2017 Codes changes in IRS forms will get release
Smita Pawar (Inactive)
added a comment - - edited We have verified above mentioned enhancement on LB company [ACA Automation] .
Its working fine.
Attaching test cases for enhancement.
Note:We have not checked the impact on other codes now as we will cover same in regression testing after 2017 Codes changes in IRS forms will get release We have verified above mentioned enhancement on stage [Caiso for Hspl].
Its working fine.
Scenarios verified which are as follows
1. SAVE and RUN Apply User Correction with flag settings as YES and NO
2. Validation checks on the page.
Attaching screen for verified employee.
Smita Pawar (Inactive)
added a comment - We have verified above mentioned enhancement on stage [Caiso for Hspl] .
Its working fine.
Scenarios verified which are as follows
1. SAVE and RUN Apply User Correction with flag settings as YES and NO
2. Validation checks on the page.
Attaching screen for verified employee. Verified on production, working fine.
Sachin Hingole (Inactive)
added a comment - Verified on production, working fine. 
Files affected are -
Modified : /branches/LB/App/BusinessLogic/Reports/StaticReports.vb
Added : /branches/LB/Database Objects/MasterCompanyDB/01_DDL/267_WT2604_WTB_ACA_ModTable_ReportDetailsStatic.sql
Added : /branches/LB/Database Objects/MasterCompanyDB/01_DDL/268_WT2604_WTB_ACA_ModTable_StaticReportControls.sql
Added : /branches/LB/Database Objects/MasterCompanyDB/01_DDL/269_WT2604_WTB_ACA_NewTable_ACA_MultiEmployerEligibilityData.sql
Added : /branches/LB/Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_ACA_1095CFetchMultiEmployerEligibilityData.sql
Modified : /branches/LB/Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Get_ACAIRS1095CData.StoredProcedure.sql
Modified : /branches/LB/Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Report_InsertUpdateStaticReport.StoredProcedure.sql
Added : /branches/LB/Database Objects/MasterCompanyDB/07_Data/078_WT2604_WTB_ACA_NewData_StaticReportControls.sql
Modified : /branches/LB/Shared Library/SharedFunction/SharedFunction/BenAdminSharedFunction.cs
Modified : /branches/LB/Shared Library/ValueObjects/ValueObjects/BenAdmin/StaticReport.cs
Modified : /branches/LB/Web/Web Projects/BenAdmin/Areas/Report/Models/StaticReportModel/StaticReports.cs
Modified : /branches/LB/Web/Web Projects/BenAdmin/Areas/Report/Views/Report/StaticReport/StaticReports.cshtml