TAG LINE
SMALL TITLE

UDR time does not match time period of UDR Usage Identifier

Last Updated: Sep 24, 2020

This error indicates that the date of the usage is earlier or later than the start date or end date set on the usage identifier associated with the account-service. If the usage is valid then then typically the usage identifier's start date was not set to the correct date. Correcting the effective date on the account-service will back date the UID start and allow the usage to be reprocessed.

Steps to resolve this exception:

  1. Use the global search in the UI with the 'Usage Identifier' Search Filter set in order to find the account-service that the Usage Identifier listed in the usage exception relates to

  2. On the Account -> Packages tab that loads check the Services tab for the selected package and locate the account-service that has the Usage Identifier that matches the UID in the UDR exception

  3. If the Effective Date of the account-service is listed as 'Same as Package' then rolling back the effective date of the account-package will result in the usage falling into a valid time period. Modify the account-package Effective Date so that it is effective at the proper date (starts before the date in the UDR exception)

  4. Return to the UDR Exceptions screen and select the UDR time does not match time period of UDR Usage Identifier exception type

  5. 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. Verify that the account-service effective date precedes the udr exception date. 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