Usage Rate matching UDR not found

This error indicates that a rate cannot be found that matches the values within the mediated usage. This exception occurs if:

• The class of the usage does not match the usage class configured on rates in the rate groups that are setup in the rate plan

• For GeoTree Rated Rate Types: The terminating identifier in the usage does not match a pattern in the GeoTree

• For GeoTree Rated Rate Types: The terminating identifier in the usage does match a pattern in the GeoTree but no rate could be found in relation to the matched pattern

• The account that the usage relates to is setup with a currency that does not match the currencies configured on rate groups in the rate plan

• Conditions on rate groups in the rate plan are not met, causing rates in the groups to be ignored and therefore no valid rate was found which matches the usage

Steps to resolve this exception:

1. On the UDR Exceptions screen select the Usage Rate 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. On the Mediated Record Detail modal that appears review the usage details including which Usage Rate Plan was selected

4. Validate that the rate you wish to apply exists within a rate group that is in the rate plan found in the exception message. If the desired rate is present ensure that it is configured with the proper usage class (this should be the class listed in the exception) and that the currency of the rate group where the rate resides matches the currency of the account that the usage relates to. If the rate uses the GeoTree as its rater, check the tree to ensure the Terminating Identifier in the usage exception matches a pattern in the tree

5. Once the issue that caused the exception has been corrected, return to the UDR Exceptions screen, select the Usage Rate 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

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

7. 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

8. 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