TAG LINE
SMALL TITLE

Usage Rate Group matching UDR not found

Last Updated: Sep 24, 2020

This error indicates that a rate group matching the mediated usage attributes could not be found in the rate plan. Typically this will mean that the currency set on the rate groups in the rate plan do not match the currency of the account that the usage relates to.

Steps to resolve this exception:

  1. On the UDR Exceptions screen select the Usage Rate Group matching UDR not found exception type

  2. Select an exception in the list that is relevant to the usage you wish to reprocess and then click the  icon next to the exception

  3. Ensure the Usage Rate Plan listed in the Mediated Record Detail has the appropriate rate group (a group that contains the rate you wish to apply) and that the currency configured on the rate group matches the currency of the account that the usage is applicable to

  4. Once the issue that caused the exception has been corrected, return to the UDR Exceptions screen, select the Usage Rate Group matching UDR not found exception type and Filter the results in the Edit UDR Exceptions panel to indicate what exceptions you wish to reprocess. Filtering is required to indicate which exceptions should be reprocessed, if filtering is not performed no exceptions will be reprocessed

  5. Click on the Reprocess button and on the modal that appears select a time to execute the reprocessing and then click Add

  6. After reprocessing the exceptions will be removed if rating was successful. You can verify the usage that was rated by running the Reports -> Rating & Usage -> UDR History report

  7. If the exceptions remain in the list click the  icon next to an exception and check the 'Last Rating Attempted' field to verify that rating did occur. If rating was attempted at the scheduled reprocessing time and the exception remains then the issue that caused the exception was not resolved. If the 'Last Rating Attempted' date did not change to the time the reprocessing was executed then rating/reprocessing did not execute. In this case contact LogiSense support for assistance in troubleshooting this issue