-
Type:
Change Request
-
Status: Closed
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ACA
-
Labels:None
-
Module:ACA
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
EE is not getting safe harbor codes if he is new hire.
This is boundary condition scenario.
EE is new hire on a day where he is satisfying both new hire and standard rules.
e.g: EE is new hire on 01/01/2016
and Measurement and Stability is of 3 months interval starting from 01/01/2016.
Concern:ACA: Measurement and Stability : EE is not getting safe harbor codes if he is new hire
Cause: EE does not have stability period for 1st 3 months from date of hire,safe harbor set on measurement and stability is not applied here. Due to boundary condition(01/01/2016), this new hire employee is getting standard rule as both the rule's measurement and stability period coincide.
This is a very rare scenario where employee is not having any safe harbor and he is not having any stability for 1st 3 months from date of hire.
Correction: We have updated the safe harbor of 1st 3 months to one of the safe harbor set in later months,So that safe harbor codes will get reflected.
Note: There may be some discrepancy in the safe harbor code if the codes differ on interval basis.
Ramya Tantry (Inactive)
added a comment - Concern :ACA: Measurement and Stability : EE is not getting safe harbor codes if he is new hire
Cause : EE does not have stability period for 1st 3 months from date of hire,safe harbor set on measurement and stability is not applied here. Due to boundary condition(01/01/2016), this new hire employee is getting standard rule as both the rule's measurement and stability period coincide.
This is a very rare scenario where employee is not having any safe harbor and he is not having any stability for 1st 3 months from date of hire.
Correction : We have updated the safe harbor of 1st 3 months to one of the safe harbor set in later months,So that safe harbor codes will get reflected.
Note : There may be some discrepancy in the safe harbor code if the codes differ on interval basis. We have done testing on LB and observed that it's working as expected.Hence marking ready for stage.
This jira is already moved to stage in other patch.
Ramya Tantry (Inactive)
added a comment - This jira is already moved to stage in other patch. We have done testing on Stage and observed that it's working as expected.Hence marking ready for Production.
This jira is already moved to Production in other patch.
Ramya Tantry (Inactive)
added a comment - This jira is already moved to Production in other patch. Can you please check this point
We have done testing on Production and observed that it's working as expected.Hence closing the same
Files affected:
Database Objects/MasterCompanyDB/04_Stored Procedures/dbo.OES_SP_Get_ACAIRS1095CData.StoredProcedure.sql