02-04-2014 11:47 PM
Hello,
I have a scenario I'm wondering if anyone else has come across. A periodic order is created on Jan 1st with a scheduled meter read date of Jan 3rd. A move out is then created on Jan 2nd with the same read date of Jan 3rd. The periodic read is uploaded on Jan 3rd with a wrapped read (read is less than previous read), causing it to go implausible. The meter technician (separate from the technician that entered the periodic) then updates the move out with a plausible read. Billing runs that night and bills the move out disregarding the implausible periodic, which is not being suppressed. We do not want the periodic to be suppressed. We would have expected the billing to error out, because of the implausible read, however it is being included in the billing.
If anyone has come across this before, what was done to rectify this situation?
02-05-2014 11:04 AM
Hi Allison,
This kind of issue needs to be taken care of at the time of saving the Move-out Meter Read. We can have a check as below :
1. If the Enetered read is Move-out Read check the following:
a. If any previous Billable MRO is open with or without Read.
b. If yes then,
This logic will lock the move-outy reads, if the previous reads are implausible.
Hope this helps.
Regards,
Gagan
02-05-2014 11:04 AM
Hi Allison,
This kind of issue needs to be taken care of at the time of saving the Move-out Meter Read. We can have a check as below :
1. If the Enetered read is Move-out Read check the following:
a. If any previous Billable MRO is open with or without Read.
b. If yes then,
This logic will lock the move-outy reads, if the previous reads are implausible.
Hope this helps.
Regards,
Gagan
02-10-2014 3:29 PM
Thank you for the response. While considering your feedback I came across a BADI (ISU_BI_CUST_CONTROL ) within FM ISU_METER_READING_RESULTS_GET. When implemented it worked to fix the scenario we were coming across and prevent billing from occuring.
Allison