2019 Sep 29 2:57 PM
dears,
I have an issue when creating Mass MROs in the background, is that the system does not check for the interval, and creates MROs with period period less than 15 days (this is the rule in my company). However, when I execute in the foreground the system behaves correctly.
It seems like the system does not consider the check box (interval check) when executed in the background.
can anyone please advise how to force the Inerval check even in background runs
2019 Sep 30 8:47 PM
There is an interval check flag, are you using it? I'll copy paste the help text for the field, its very explainatory & links to relevant config in your system.
Means the system checks whether a meter reading order or result already exists within the meter reading interval. If so, the system suppresses the meter reading order whose meter reading reason has the lower priority.
If you do not perform the interval check, this speeds up meter reading order creation, but the meter reading/billing order is always created, even if one already exists.
You define the priority of the meter reading reasons in IS-U Customizing under Define Priority of Meter Reading Orders for the Meter Reading Interval Check.
2019 Oct 01 10:07 AM
Hello Daniel,
thanks for the answer. Yes I am using interval check,and I have the the reasons priority configured. and strangely it works when I run in foreground, but When I run in background I find MROs that violate the interval check.
Do you have an idea what could the problem be..