2014 Nov 27 3:16 PM
Hi,
I am trying to upload meterread results through my program using this BAPI . However I get an error in some scenarios with error text " Error in segment XXX: MR does not meet customization" . However when I try to enter same reads through El28 , same reads are uploaded successfully.
Any insight into the possible issue ?
regards,
AM
2014 Nov 28 4:35 AM
I will assume you are referring to EL533 Segment number &1: MR result does not meet Customizing requirements
SE91 for this message, review the long text. The procedure noted in the Performance Assistant will guide you to
"Check your settings in Customizing for Meter Reading under Meter Reading Result -> Change -> Define Change Process for Meter Reading Data and change them if necessary."
basically thats the fix. This config manages the meter reading results that are modifiable during upload via IDoc type and the BAPI ISU_MTRREADDOC_UPLOAD.
2014 Nov 28 4:35 AM
I will assume you are referring to EL533 Segment number &1: MR result does not meet Customizing requirements
SE91 for this message, review the long text. The procedure noted in the Performance Assistant will guide you to
"Check your settings in Customizing for Meter Reading under Meter Reading Result -> Change -> Define Change Process for Meter Reading Data and change them if necessary."
basically thats the fix. This config manages the meter reading results that are modifiable during upload via IDoc type and the BAPI ISU_MTRREADDOC_UPLOAD.
2014 Nov 28 10:42 PM
Thanks Daniel . My problem was that if I am able to upload same read with same read type through el28 , why would BAPI give me an error. Looks like standard tcode doesnt use this BAPI and thats why I get an error while uploading the read through BAPI.
Although I dont understand the rationale behind keeping this customization only for reads uploaded through BAPI!!
2014 Nov 30 11:51 PM
The config identified controls the BAPI. There are separate controls to a dialog session. If you have concerns over the seperation of online vs background uploads, you could raise a SAP incident. But that said, the functionality is documented & is simple enough to enable by maintaining that SPRO node.