Workterra BenAdminProject Type: business

Workterra BenAdmin

Uploaded image for project: 'Workterra BenAdmin'
  1. Workterra BenAdmin
  2. WB-641

Export > Future Effective and Future Dead enrollment exporting wrong election on columnwise file

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Bug Fixed
    • Labels:
    • Environment:
      Production, Stage, QA
    • Categories:
      Export
    • Company:
      All Clients/Multiple Clients
    • Reported by:
      Harbinger
    • Level:
      Partner
    • Browser:
      Google Chrome

      Description

      Hi Vinayak Kulkarni,

      Found a scenario where future effective and future dead election is exporting wrong election on file

      1) Employee Enrolled in Med 1 from 1/1/2016
      2) Changes to Med 2 on 10/1/2017
      3) New election of Med 2 exported on file with eff date 10/1/2017
      4) Med 2 becomes dead termed as never effective and file is exported

      Result : Med 1 plan with effective date as 1/1/2016 and Termination date as 09/30/2017 exported on file

      Can you please check and update accordingly ?

        Attachments

        1. AffectedFiles.txt
          0.1 kB
        2. Wb-641.xls
          10 kB

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

          Hi Amit Thorve

          Can you please go through this scenario and let us know whether it needs to be handled?
          This is for column-wise file. Let us know if we need to discuss this. Thanks.

          Show
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Amit Thorve Can you please go through this scenario and let us know whether it needs to be handled? This is for column-wise file. Let us know if we need to discuss this. Thanks.
          Hide
          Permalink
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

          Hi Amit,

          Can you guide us here, I believe this is not an issue as we never face such issue into production, However wanted you confirmation?

          Show
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Amit, Can you guide us here, I believe this is not an issue as we never face such issue into production, However wanted you confirmation?
          Hide
          Permalink
          amitthorve Amit Thorve (Inactive) added a comment -

          Vinayak Kulkarni Is Med 2 is exported on file with 10/1/2017 date and then if it becomes dead then on next file the dead enrollment should roll out.

          We can discuss it with Aniruddha Dev today.

          Show
          amitthorve Amit Thorve (Inactive) added a comment - Vinayak Kulkarni Is Med 2 is exported on file with 10/1/2017 date and then if it becomes dead then on next file the dead enrollment should roll out. We can discuss it with Aniruddha Dev today.
          Hide
          Permalink
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

          Files affected: dbo.OES_UDF_Export_GetExportedDeadEnrollmentIDs.UserDefinedFunction

          Show
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Files affected: dbo.OES_UDF_Export_GetExportedDeadEnrollmentIDs.UserDefinedFunction
          Hide
          Permalink
          jenniferreed Jennifer Reed (Inactive) added a comment -

          Satya Vinayak Kulkarni I am not sure if I am understanding what is going on here..and what do we mean by the term "dead"? Does this mean inactive?

          Show
          jenniferreed Jennifer Reed (Inactive) added a comment - Satya Vinayak Kulkarni I am not sure if I am understanding what is going on here..and what do we mean by the term "dead"? Does this mean inactive?
          Hide
          Permalink
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment -

          Hi Jennifer,

          "dead" means "terminated as never effective".

          When a enrollment gets added in system, we report it on export file. However later on due to any data change event if that enrollment is terminated as never effective then we again report this termed as never effective on export file.

          We have to report this termed as never effective to stop payroll deduction if we sent active deduction earlier.

          This ticket is for one specific scenario where "termed as never effective" enrollment is not getting reported on export file. That scenario is mentioned on description of ticket. Let us know if you have any questions on this, Thanks.

          Show
          Vinayak.Kulkarni Vinayak Kulkarni (Inactive) added a comment - Hi Jennifer, "dead" means "terminated as never effective". When a enrollment gets added in system, we report it on export file. However later on due to any data change event if that enrollment is terminated as never effective then we again report this termed as never effective on export file. We have to report this termed as never effective to stop payroll deduction if we sent active deduction earlier. This ticket is for one specific scenario where "termed as never effective" enrollment is not getting reported on export file. That scenario is mentioned on description of ticket. Let us know if you have any questions on this, Thanks.
          Hide
          Permalink
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

          Attached test cases - 

          Wb-641.xls

           

          CC-Rakesh Roy Hrishikesh Deshpande

          Show
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Attached test cases -  Wb-641.xls   CC- Rakesh Roy Hrishikesh Deshpande
          Hide
          Permalink
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

          Verified all scenarios ,It is working as expected.

          Ready for pre-production deployment.

          CC-Rakesh Roy Hrishikesh Deshpande

          Show
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified all scenarios ,It is working as expected. Ready for pre-production deployment. CC- Rakesh Roy Hrishikesh Deshpande
          Hide
          Permalink
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

          Verified this on pre-production ,It is working as expected.

          Ready for prodution deployment.

          CC-Rakesh Roy Hrishikesh Deshpande

          Show
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified this on pre-production ,It is working as expected. Ready for prodution deployment. CC- Rakesh Roy Hrishikesh Deshpande
          Hide
          Permalink
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

          Verified this on production,It is working as expected.

          Hence closing this ticket.

          CC-Rakesh Roy Hrishikesh Deshpande

          Show
          swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified this on production,It is working as expected. Hence closing this ticket. CC- Rakesh Roy Hrishikesh Deshpande

            People

            Assignee:
            swapnil.eksambekar Swapnil Eksambekar (Inactive)
            Reporter:
            aniruddha.dev Aniruddha Dev (Inactive)
            Developer:
            Rakesh Shahane (Inactive)
            QA:
            Swapnil Eksambekar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Dev Due Date:

                Time Tracking

                Estimated:
                Original Estimate - 16h Original Estimate - 16h
                16h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 37.1h
                37.1h