2015 Jul 14 4:11 PM
hello,
EL22 / EL20 used for online mass meter read upload doesn't seem to support read reason 03 and 06 (move-in/out) meter read uploads. IS there any specific reason for this. Also, is there any way it can be enhanced to support move-in/out read uploads?
Any help would be appreciated!
Thanks.
2015 Jul 15 9:17 AM
Hi Ankit,
Yes it is not possible to punch move-in , move-out , device-installation or removal , disc or re connection etc via these TCODEs .
Reason is to put fast reading using EL20 /22 we use "Entry no" & "Check value" combination, so for one MRU & schedule meter reading date "Entry no" & "Check value" combination will point to one particular MR doc id which is not true for other reading reasons.
Like in my case .
I have two device D1 & D2 falling in same MRU and moved out on 15.07.2015 (Same date Schedule MR date ) now if you check in EABL table you will find they have same "Entry no" & "Check value" value (infact for so while putting reading how system will know this reading belongs to D1 or D2 that is why these reading reasons are not present in EL20 or El22 screens.
2015 Jul 15 9:17 AM
Hi Ankit,
Yes it is not possible to punch move-in , move-out , device-installation or removal , disc or re connection etc via these TCODEs .
Reason is to put fast reading using EL20 /22 we use "Entry no" & "Check value" combination, so for one MRU & schedule meter reading date "Entry no" & "Check value" combination will point to one particular MR doc id which is not true for other reading reasons.
Like in my case .
I have two device D1 & D2 falling in same MRU and moved out on 15.07.2015 (Same date Schedule MR date ) now if you check in EABL table you will find they have same "Entry no" & "Check value" value (infact for so while putting reading how system will know this reading belongs to D1 or D2 that is why these reading reasons are not present in EL20 or El22 screens.