Summary
This article explains how to process UDR Exceptions after resolving the problems that caused UDR Exceptions to be generated. If the issue that caused UDR Exceptions to be created has not been resolved, reference the article Handling Usage Exceptions prior to following the steps in this guide.
Exception Processing and Bill Runs
If processing occurs during the current billing period, the processed exception will move to the “UDR” table and the amounts will be added to the current billing Period UDRBiller (which will generate the invoice). In this case the current billing Period buckets will be applied to the usage (from UDR and UDRException) until the bucket finishes.
If processing occurs during the next billing period (after billing), the processed exception will move to the “UDR” table and the amounts will be added to non-billed UDRBiller (which is the next billing period). In this case the next billing Period buckets will be applied to the usage until the bucket finishes.
In short, once a UDR Exception is fixed and processed it joins the earliest open UDR Biller (invoice). The logic is as follows:
If the corresponding UDRBiller is open, it joins it
if the corresponding UDRBiller is closed, it joins the earliest open UDRBiller
If there is no new UDRBiller, a new UDRBiller is created
Rating Page Check Boxes:
The "Enabled" flag shows that the feed is enabled and the "Process Exceptions" indicates that there are exceptions set to reprocess.
The "Enabled" should be checked any time you need rating/rerating/processing exceptions to happen so its normal to leave it checked.
The "Process Exceptions" gets checked automatically when you process exceptions through the interface or the SQL job created for you.
Processing UDR Exceptions
Load the Admin owner account
Click on Rating
Click on the name of the UDR Feed you wish to process
Under the UDR Exceptions heading click View to select the filters you need for the UDR Exceptions report
Once the View Parameters are set, click the Update button and the UDR Exceptions will be listed
Address the UDR Exception (Note: see the Article Handling UDRExceptions for instructions on dealing with Exceptions)
To select exceptions:
Select the Exceptions you wish to process by checking the checkbox in the select column (Note:
all UDR Exceptions in the date range of the exception(s) selected will be processed)If you want to process ALL exceptions, not just a page at a time, just click 'process' without
selecting any of them and it will process all in the complete table, not just those shown in the list
of 20 or so
Press the Process button beneath the list of UDR Exceptions to being processing
Determining if Processing is Occurring
Under the admin owner account click on Reports
Under the Owner Reports heading click on Event Log
Look for 'Rating' events listed as "Processing Exceptions" in the Result column within the Event Log table. The name of the feed that you selected and processed will also be indicated in the Result column
You will know processing is finished when you see a 'Finished' Result, i.e. Finished Processing ( 32) Exceptions for feed xxxx
To see the number of UDRs rated view the main rating page and check the UDR and UDR Exception Counts.
Interpreting the UDR Count and UDR Exception Count
During UDR Exception processing, you will notice the UDR Count increases while the UDR Exception Count is constant. Once processing is done UDR Exception Count will drop down. The reason for this drop is once a UDR Exception is corrected, it moves to the UDR table (causing the UDR count to increase) and gets a success instead of an error message (causing the UDR count to remain constant). Once processing is done, all success messages are deleted.
Troubleshooting
No 'Processing Exceptions' Events in the Event Log
If Processing Exceptions are not present in the log ensure the BossRatingService is running
Click on Configuration on the tools links in the upper right of the AdminPortal interface
Under the System Check heading check to see if the BossRatingService is active
If it is not, enable the service in Windows (it should appear as 'EngageIP Rating Service' or 'EngageIPRatingService' in Services)
Attempt to process UDR Exceptions again and check the Event Log