Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-12077

OPERS_ODC UHC GSF 1.30 - export error

    Details

    • Type: Analysis
    • Status: In Analysis
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      Production
    • Module:
      BenAdmin - Enrollment
    • Reported by:
      EDI
    • Company:
      OPERS
    • Item State:
      Development - In Analysis
    • Issue Importance:
      Must Have
    • Severity:
      Simple

      Description

      the mentioned file did not export this week due to the following error:

      Company Name: OPERS
      Template Name: ODC UHC GSF 1.30
      ErrorMessage: This constraint cannot be enabled as not all values have corresponding parent values.

      The file had been working. There is another UHC GSF for the OPERS group under the same company template that is built the same way and it's working. Can you tell me what happened with this file?

      cc: Olivea Carter

        Attachments

        1. 2017 election.png
          2017 election.png
          221 kB
        2. 2018 election.png
          2018 election.png
          223 kB
        3. wrong_member_coverage.png
          wrong_member_coverage.png
          75 kB

          Activity

          Hide
          rajendra.pawar Rajendra Pawar (Inactive) added a comment -

          Hi Kevin Hale

          We are looking into this, and will let you ASAP.

          Thanks,
          Rajendra Pawar

          Show
          rajendra.pawar Rajendra Pawar (Inactive) added a comment - Hi Kevin Hale We are looking into this, and will let you ASAP. Thanks, Rajendra Pawar
          Hide
          rajendra.pawar Rajendra Pawar (Inactive) added a comment -

          Hi Kevin Hale,

          This error occurred due to wrong member coverage in database, we have corrected this and now template is exporting without error.

          Avnish Yadav/ Rushikesh Dattatray Bane, Can you please scan and correct the data for other employees if any?

          Jyoti Mayne Please update 3C's.

          With kind regards,
          Rajendra Pawar
          --------------------------------------------------------------
          Vinayak Kulkarni Amruta Lohiya Swapnil Pandhare Prashant Samal

          Show
          rajendra.pawar Rajendra Pawar (Inactive) added a comment - Hi Kevin Hale , This error occurred due to wrong member coverage in database, we have corrected this and now template is exporting without error. Avnish Yadav / Rushikesh Dattatray Bane , Can you please scan and correct the data for other employees if any? Jyoti Mayne Please update 3C's. With kind regards, Rajendra Pawar -------------------------------------------------------------- Vinayak Kulkarni Amruta Lohiya Swapnil Pandhare Prashant Samal
          Hide
          shailendra.honrao Shailendra Honrao (Inactive) added a comment -

          Hi Kevin Hale,

          Problem Statement: Error on export due to wrong member coverage data

          Details of Analysis:
          Apart from reported employee, we have scanned all EEs and and found 1 EE affected.

          • For EE 'R OVERLY' enrollment was added by company administrator 'Holly Hanlon' with OE mode for 'UHC Medical Plan'.
          • While enrolling in plan through company admin workflow, incorrect coverage was stored in the system in form of EE+SP+CH.

          From back end we are not able to figure out with which tier enrollment was done for this EE.
          Please let us know what should be the tier for EE so that we can correct his coverage.

          Rashmita Dudhe We had tried this scenario but it is not reproducing.

          Please found below screenshot for wrong member coverage

          1. Login with EE, in EE workflow enrolled in plan with different combinations of tiers with effective date '01/01/2018'
          2. Enroll with company admin workflow in plan with effective date '01/01/2018'
          3. Added a new test EE and enrolled into plan with effective date'01/01/2018'

          In all of the above mentioned scenarios, member coverage is inserted properly.

          Can you help us to reproduce this issue?

          Thanks,
          Shailendra Honrao

          Cc: Amruta Lohiya,Jyoti Mayne

          Show
          shailendra.honrao Shailendra Honrao (Inactive) added a comment - Hi Kevin Hale , Problem Statement: Error on export due to wrong member coverage data Details of Analysis: Apart from reported employee, we have scanned all EEs and and found 1 EE affected. For EE 'R OVERLY' enrollment was added by company administrator 'Holly Hanlon' with OE mode for 'UHC Medical Plan'. While enrolling in plan through company admin workflow, incorrect coverage was stored in the system in form of EE+SP+CH. From back end we are not able to figure out with which tier enrollment was done for this EE. Please let us know what should be the tier for EE so that we can correct his coverage. Rashmita Dudhe We had tried this scenario but it is not reproducing. Please found below screenshot for wrong member coverage Login with EE, in EE workflow enrolled in plan with different combinations of tiers with effective date '01/01/2018' Enroll with company admin workflow in plan with effective date '01/01/2018' Added a new test EE and enrolled into plan with effective date'01/01/2018' In all of the above mentioned scenarios, member coverage is inserted properly. Can you help us to reproduce this issue? Thanks, Shailendra Honrao Cc: Amruta Lohiya , Jyoti Mayne
          Hide
          Kevin.Hale Kevin Hale (Inactive) added a comment -

          Hey Olivea Carter - see the comments above. I need you to recreate this scenario. Let us know of any questions. Thanks!

          cc: Deborah Larue

          Show
          Kevin.Hale Kevin Hale (Inactive) added a comment - Hey Olivea Carter - see the comments above. I need you to recreate this scenario. Let us know of any questions. Thanks! cc: Deborah Larue
          Hide
          hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

          Hi Shailendra Honrao,

          We are trying to Reproduce this issue. We will update you on this by tomorrow 11/15.

          Thanks,
          Hrishikesh.

          Show
          hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - Hi Shailendra Honrao , We are trying to Reproduce this issue. We will update you on this by tomorrow 11/15. Thanks, Hrishikesh.
          Hide
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment -

          Hi Shailendra Honrao,

          CC:Hrishikesh Deshpande,Rakesh Shahane,Jyoti Mayne,Samir,Satya

          I have tried to reproduce this issue but it is not getting reproduced.
          a reported employee does not have a child and also his spouse is not enrolled in the plan.
          and the wrong coverage sting was inserted with an EE+Sp+Ch tier with Employee id which does not exist in the company. Not able to catch this scenario but as per my end tried below scenarios:

          1] Add new employee.
          2] Enrolled in the medical plan with an effective date 01/01/2016
          3] through admin Workflow OE add Spouse.
          4]Change tier multiple times it showing proper coverage string in the database.
          5]Change enrollment of employee at the same time through employee login and admin login
          6] through the admin workflow logout form medical plan and again login and select other employee and enrolled in the medical plan with EE+SP+CH tier.
          7]Again go to the same employee and enrolled in EE tier. Proper coverage string is inserted into the database.
          8]Change employee tier with retro, current and future date.

          Need to have a discussion with other team member related this.

          Thanks,
          Rashmita

          Show
          rashmita.dudhe Rashmita Dudhe (Inactive) added a comment - Hi Shailendra Honrao , CC: Hrishikesh Deshpande , Rakesh Shahane , Jyoti Mayne , Samir , Satya I have tried to reproduce this issue but it is not getting reproduced. a reported employee does not have a child and also his spouse is not enrolled in the plan. and the wrong coverage sting was inserted with an EE+Sp+Ch tier with Employee id which does not exist in the company. Not able to catch this scenario but as per my end tried below scenarios: 1] Add new employee. 2] Enrolled in the medical plan with an effective date 01/01/2016 3] through admin Workflow OE add Spouse. 4]Change tier multiple times it showing proper coverage string in the database. 5]Change enrollment of employee at the same time through employee login and admin login 6] through the admin workflow logout form medical plan and again login and select other employee and enrolled in the medical plan with EE+SP+CH tier. 7]Again go to the same employee and enrolled in EE tier. Proper coverage string is inserted into the database. 8]Change employee tier with retro, current and future date. Need to have a discussion with other team member related this. Thanks, Rashmita
          Hide
          jyoti.mayne Jyoti Mayne added a comment -

          Hi Kevin Hale,

          Currently EE 'R OVERLY' is enrolled with wrong members in plan 'UHC Medical Plan' for 1/1/18 election and his cost is as per EE+SP+CH tier. PFA screen shot.

          His previous election in same plan is with EE tier 1/1/16 to 12/31/2017.

          Can we go ahead and correct its 1/1/18 'UHC Medical Plan' election tier to EE and cost?. Please provide your approval.

          Cc: Amruta Lohiya

          Show
          jyoti.mayne Jyoti Mayne added a comment - Hi Kevin Hale , Currently EE 'R OVERLY' is enrolled with wrong members in plan 'UHC Medical Plan' for 1/1/18 election and his cost is as per EE+SP+CH tier. PFA screen shot. His previous election in same plan is with EE tier 1/1/16 to 12/31/2017. Can we go ahead and correct its 1/1/18 'UHC Medical Plan' election tier to EE and cost?. Please provide your approval. Cc: Amruta Lohiya
          Hide
          Kevin.Hale Kevin Hale (Inactive) added a comment -

          Hi Olivea Carter - see Jyoti Mayne comments above regard the employee's Medical election. Can you fix please?

          Show
          Kevin.Hale Kevin Hale (Inactive) added a comment - Hi Olivea Carter - see Jyoti Mayne comments above regard the employee's Medical election. Can you fix please?
          Hide
          Olivea.Carter Olivea Carter (Inactive) added a comment -

          hi Kevin,
          This has been corrected. Let me know if you need anything further.
          Jyoti Mayne

          Show
          Olivea.Carter Olivea Carter (Inactive) added a comment - hi Kevin, This has been corrected. Let me know if you need anything further. Jyoti Mayne

            People

            Assignee:
            Kevin.Hale Kevin Hale (Inactive)
            Reporter:
            Kevin.Hale Kevin Hale (Inactive)
            Account Executive:
            Kevin Hale (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Dates

              Created:
              Updated:

                Time Tracking

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