Skip to main content

Error : Claim.MeasDetailID is either empty or in the MeasDetailID valuelist.

Testing Feedback

Hi CEDARS team,

For the following errors

  1. Claim.MeasDetailID is either empty or in the MeasDetailID valuelist.

  2. Claim.ShipmentDate and Claim.SalesDate are empty.

the issue might be triggered because the CEDARS test site has a MeasDetailID value list that is not in up to date with eTRM.

Can you look into it?

Thanks

Environment
Testing cedars-3
Select user type
Posted by sacharya ·
Status: Completed12 comments

Log in to comment and vote

Comments12

  • Gabrielle Roth

    Team•

    Jun 17, 2025

    Thank for you for providing examples! These values are being excluded from the sync; I’ll put in an internal ticket to correct this.

  • Gabrielle Roth

    Team•

    Jun 16, 2025

    Hello,

    Thanks for reporting this problem. The MeasDetailID value list is updated nightly so it should be reasonably up-to-date with eTRM values.

    I would like to verify that with your uploaded file, but I don’t see that file in the upload history on the testing host. I believe we recloned the testing environment late last week; that could be why the file is missing from the history.


    Could you pleae send me a copy of the file so I can reproduce the problem?

    Thank you!

    Gabrielle

    • sacharya

      •

      Jun 16, 2025

      Thanks for the response, Gabrielle.

      I’ve just reuploaded the Claims in testing but looks like only folks at SCG could access this file. I’ve attached the local zipped file for you to test.

      Thanks,

      Sapan

      Edit: I'm unable to attach the file here. Could you provide your email address so I can send it directly to you?

  • Roopa Reddy

    •

    Jun 17, 2025

    @cedars team
    PG&E has encountered the error “Claim.MeasDetailID is either empty or not in the MeasDetailID value list.” The MeasDetailID value list is not up to date with the 2025 revisions, causing the validation to fail.

    For example, PG&E has Q1 claims associated with the following valid measure packages: SWWH028-06, SWWH027-06, SWWH025-09, SWAP013-05, and SWWH006-09. These measure package permutations are currently missing in the MeasDetailID value list.

    Thank you for your assistance with this error.

  • Gabrielle Roth

    Team•

    Jun 20, 2025

    Update: I have a new version of our sync job ready to try out on Monday. I’ll let you know how it goes.

  • Gabrielle Roth

    Team•

    Jun 23, 2025

    @RoopaReddy_PGE @sacharya I’ve rolled out a fix to the testing environment (cedars-3). You should be able to see measure packages that start in 2025 now.

    Please let me know how it goes.


    Gabrielle