How to do mass upload of meter readings in ISU

May 01, 2009 at 09:58 AM | 141 Views

Hi,

Could anybody please guide me how to do mass upload of meter readings in ISU?

How to use Transaction code ELEU or ELMU?

Thanks and Regards

Edited by: Akhil Garg on May 1, 2009 11:59 AM

Utilities
Follow
RSS Feed
Related questions
Is there any connection between ELMU and ManufSerialNo?
By Valentina Solorzano, Oct 25, 2018
Estimated Meter reading from previous consumption for Mo
By Praphulla Kanade, Jan 07, 2019
How to estimate interval meter readings in SAP-ISU
By Binod Nath, Sep 06, 2017
4 Answers
Sort by: Votes| Newest| Oldest
avatar image
Former Member
May 01, 2009 at 11:15 AM
0
Hello This information may be of some help as an option for upload:

http://help.sap.com/saphelp_utilities472/helpdata/en/9f/
03693582f4db60e10000009b38f889/frameset.htm

Regards

Olivia

Share
avatar image
Former Member
May 01, 2009 at 06:08 PM
0
For these transactions...: ELMU & ELEU.

There are 2 types of meter reading uploads are there.

1) Basic-Meter reading Upload

2) Interval Meter read Upload

You have to create one development for this.

In this development u will create one idoc after this you will execute EL01 t-code
to upload Basic meter readings.

For uploading meter reading result you need use IDoc. Some industries(regulated)
have the reading uploaded themselves. For ex, field agent with mobile device, this
comes into SAP as IDoc and uploaded using BAPI (BAPI_MTRREADDOC_UPLOAD). If the
readings are coming from third party meter reading comany as a file then you would
need to write a program to process each records in the file , create IDoc and then
further uploade readings.

Sap Help for uploading the meter readings.

You can upload meter reading results from external systems (such as MDE devices)
using a BAPI or IDoc of type ISU_MR_UPLOAD01 (upload meter reading results). The
BAPI method is called MeterReadingDocument.Upload. Corresponding structure
BAPIEABLU contains the following fields:

� MATERIAL (material number)

Material/device category

� SERIALNO (device serial number)

� REGISTER (register number)

� MRREASON (meter reading reason)

� MRIDNUMBER (internal meter reading document number)

The meter reading number identifies a meter reading order. A meter reading order is
created for each register to be read. The meter reading document number must be
downloaded and uploaded from the external system.

� READINGRESULT (meter reading)

The data record is transferred to the system if either a meter reading result or
note was provided.

� METERREADINGNOTE (meter reading note)

The data record to be uploaded is transferred if either a meter reading or note was
provided. The meter reading note can be assigned to a control function in IS-U. The
control function defines follow-up actions.

� ACTUALCUSTOMERMRTYPE (meter reading type)

Describes how the meter reading result was recorded u2013 by a meter reader or by
the customer, for example.

� METERREADER (meter reader number)

The meter reader number is used to identify the meter reader. It is used as a
default value and can be stored in the schedule record of the meter reading. You
can use the Meter reader number field to indicate that the actual meter reader is
different from the default meter reader.

� MRDATEFORBILLING (meter reading date)

Billing occurs on this date, which is also the end of the billing period. The end
of the billing period is determined.

� MRTIMEFORBILLING (meter reading time)

� ACTUALMRDATE (actual meter reading date)

� ACTUALMRTIME (actual meter reading time)

� MRDATEOFMAXIMUM (date of maximum reading)

� MRTIMEOFMAXIMUM (Time of maximum reading)

� SMORDER (service order number)

� ACTIVE (active indicator)

There are two upload scenarios:

1. Meter reading orders were already created and downloaded in IS-U.

Meter readings are assigned to IS-U orders via the document number when they are
uploaded. In this case you do not have to maintain the following fields:

Material number

Device serial number

Register number

Meter reading reason

2. There are no meter reading orders in IS-U/CCS

In this case you have to specify the serial number and the register number to
identify the device for which readings are to be entered in IS-U/CCS.

If the serial number is not unique, you also have to provide the material number
and device category. You also have to supply the meter reading reason, a meter
reading date and a meter reading.

Share
avatar image
Former Member
May 20, 2009 at 05:06 AM
0
As mentioned by Olivia Above to upload the meter readings, you need to provide the
details like meter read document number, reads, read dates , read reasons etc to
BAPI_MTRREADDOC_UPLOAD.

A snipet of the code is below :

Part 1 : Filling the internal table to pass to BAPI

Move
WA_MRUDATA-GERNR to WA_BAPI_UPD-SERIALNO,
WA_MRUDATA-ZWNUMMER to WA_BAPI_UPD-REGISTER,
WA_MRUDATA-ABLESGR to WA_BAPI_UPD-MRREASON,
WA_MRUDATA-ABLBELNR to WA_BAPI_UPD-MRIDNUMBER,
WA_MRUDATA-U_READING to WA_BAPI_UPD-READINGRESULT,
LV_NOTES to WA_BAPI_UPD-METERREADINGNOTE,
WA_MRUDATA-U_M_READER to WA_BAPI_UPD-METERREADER,
WA_MRUDATA-U_ACT_DATE to WA_BAPI_UPD-ACTUALMRDATE,
WA_MRUDATA-U_READ_TIME to WA_BAPI_UPD-ACTUALMRTIME.
append WA_BAPI_UPD to IT_BAPI_UPD.
Part 2 : Call the BAPI
call function 'BAPI_MTRREADDOC_UPLOAD'
tables
METERREADINGRESUPDATE = IT_BAPI_UPD
RETURN = IT_BAPI_RETURN.
if not IT_BAPI_RETURN is initial.
loop at IT_BAPI_RETURN into WA_BAPI_RETURN .

if ( WA_BAPI_RETURN-TYPE eq 'E' or
WA_BAPI_RETURN-TYPE eq 'A' ).

LV_ERR_FLAG = 1. " Errornous record

endif.

endloop.
Hope this is helpfull

======================================
MR Results upload
Function documentationUpload Locate the document in its SAP Library structure
Use
You can upload meter reading results from external systems (such as MDE devices)
using a BAPI or IDoc of type ISU_MR_UPLOAD01 (upload meter reading results). The
BAPI method is called MeterReadingDocument.Upload. Corresponding structure
BAPIEABLU contains the following fields:
� MATERIAL (material number)
Material/device category
� SERIALNO (device serial number)
� REGISTER (register number)
� MRREASON (meter reading reason)
� MRIDNUMBER (internal meter reading document number)
The meter reading number identifies a meter reading order. A meter reading order is
created for each register to be read. The meter reading document number must be
downloaded and uploaded from the external system.
� READINGRESULT (meter reading)
The data record is transferred to the system if either a meter reading result or
note was provided.
� METERREADINGNOTE (meter reading note)
The data record to be uploaded is transferred if either a meter reading or note was
provided. The meter reading note can be assigned to a control function in IS-U. The
control function defines follow-up actions.
� ACTUALCUSTOMERMRTYPE (meter reading type)
Describes how the meter reading result was recorded � by a meter reader or by the
customer, for example.
� METERREADER (meter reader number)
The meter reader number is used to identify the meter reader. It is used as a
default value and can be stored in the schedule record of the meter reading. You
can use the Meter reader number field to indicate that the actual meter reader is
different from the default meter reader.
� MRDATEFORBILLING (meter reading date)
Billing occurs on this date, which is also the end of the billing period. The end
of the billing period is determined.
� MRTIMEFORBILLING (meter reading time)
� ACTUALMRDATE (actual meter reading date)
� ACTUALMRTIME (actual meter reading time)
� MRDATEOFMAXIMUM (date of maximum reading)
� MRTIMEOFMAXIMUM (Time of maximum reading)
� SMORDER (service order number)
� ACTIVE (active indicator)
There are two upload scenarios:
...
1. Meter reading orders were already created and downloaded in IS-U.
Meter readings are assigned to IS-U orders via the document number when they are
uploaded. In this case you do not have to maintain the following fields:
� Material number
� Device serial number
� Register number
� Meter reading reason
2. There are no meter reading orders in IS-U/CCS
In this case you have to specify the serial number and the register number to
identify the device for which readings are to be entered in IS-U/CCS.
If the serial number is not unique, you also have to provide the material number
and device category. You also have to supply the meter reading reason, a meter
reading date and a meter reading.
Further information on IDocs:
� For general information, see Structure linkIDoc Interface/Electronic Data
Interchange
� For detailed information, see Structure linkUsing Documentation Tools
Here you determine which documentation you can display for a certain IDoc.
Features
The enhancements EDMMRRES are available for upload. You use this enhancement to
manipulate meter readings after results have been uploaded and before the readings
are validated.

Leaving content frame

Posted 9th March 2011 by sush

0 Add a comment
MAR
9
Meter Reading
Meter Reading Locate the document in its SAP Library structure
Purpose
This component allows you to organize meter readings and meter reading results.
Devices are either read periodically for periodic billing or aperiodically, such as
for control meter readings and readings at the time of device replacement, removal,
or disconnection.
Devices can also be read for a certain activity, such as a move-in or a removal. In
this case, the meter reading is triggered directly by the activity, and not by the
Meter Reading component.
Meter Reading ProcessThis graphic is explained in the accompanying text
First, the meter reading order is created and printed as a meter reading document
or downloaded to an external entry system. The meter reading results are either
entered manually or uploaded. They are then validated and corrected, if necessary.
The results are then forwarded to the Contract Billing (ISU-BI) component.
Integration
The following Business Application Programming Interfaces (BAPI) are available in
the Business Object Repository (BOR) for selecting meter reading orders and
results:
MeterReadingDocument.GetList (select meter reading orders and results)
MeterReadingDocument.Upload (upload meter reading results)
Further information on IDocs:
For general information, see the
Structure link BAPI User Guide and Structure link BAPI Programming
For more information, see the BAPI documentation in the BO

==========================================================
Hi Heb,

You got to create a winding group with transformer type: Combination

transformer(Current & Voltage) and mention the Tr.Voltage & T.Current columns with
relevant values in the Winding data table.

On the Device category you got to set the type of measurement as '1'(Indirect) or
'3' (semi/indirect) for measurements.
Share
avatar image

heb abu

Sep 05, 2017 at 03:45 PM

Hello Ricky,

thank you for the answer....

the issue here is that some transformers have only currents,, and some have only
voltages, and some have both (current and voltage together)..

moreover, these transformers need to be installed together as groups, with various

combinations (only current transformers, and sometime current and voltage
transformers).

my issue is when to use each winding group type (0 or 2 or 6, as all of them allow
maintaining current values), and in that case how i am going to use the devices
having these winding in the groups mentioned above...
Share
avatar image

Narasimha MS
Sep 10, 2017 at 03:20 PM

Hi Heb

For Device categories with semi indirect method we must use a Transformer with
winding group created for low Voltage Current transformer because here the load
voltage and rated voltage of meter are same only current is issue , we need a step
down transformer which can transform load current example 200 amps to Meter rated
current as 10 amps . we need winding group with only Primary 200 amps and Secondary
windings as 10 amps

For device categories with indirect method of measurement we need transformer with
winding group containing only and primary and secondary Voltages

For device categories with semi indirect and indirect method we require both
primary voltages , primary currents and secondary voltage and current in winding
group

Also which meter is to be used depends on prevailing load voltages and currents and
ratings of meters
=============================================
BAPI_MTRREADDOC_UPLOAD - UPLOAD METER READING RESULTS
ROGBILLS - Synchronize billing plans TXBHW - Original Tax Base Amount in Local
Currency
This documentation is copyright by SAP AG.
SAP E-Book
FUNCTIONALITY
This BAPI imports the meter reading results and additional information from one of
the following three tables of meter reading results into the IS-U/CCS system:

METERREADINGRESULTS
METEREADINGRESCHANGE
METERREADINGRESUPDATE
For a description of the individual table fields, see the documentation for the
parameter.

In order to process an uploaded record, a meter reading or a meter reading note

must exist.

To start uploading meter reading results, one of the three parameters must be
filled.

There are three different processes:

Enter Meter Reading Results

The parameter or table METERREADINGRESULTS contains the uploaded records of the
meter reading results to be entered.
Change meter reading results
The parameter or table METERREADINGRESULTS contains the uploaded records of the
meter reading results to be changed.
Update Meter Reading Results
The parameter or table METERREADINGRESUPDATE contains the uploaded records of the
meter reading results to be updated or the meter reading results to be entered and
changed.
ENTER METER READING RESULTS
There are two processing scenarios:

A corresponding meter reading order exists for the uploaded meter reading result.
In this case, the result was previously downloaded to an external system. The
records uploaded from this system contain the internal ID of the meter reading
order. The Material, Serial Number, Register, and Meter Reading Reason fields can
be ignored.
No meter reading order exists for the uploaded meter reading result.
In this case, the key fields for one of the following alternatives must be filled:
Serial Number, Register, Meter Reading Date
If the serial number is not unique in the system, a material must also be provided.
Serial Number, Register, Meter Reading Date
If the serial number is not unique in the system, a material number must also be
provided.
Point of Delivery, Register, Meter Reading Date
If no meter reading order exists for the uploaded meter reading result, you have to
enter data in the meter reading time (MRTIMEFORBILLING) field in addition to the
key fields described above. All meter reading results of an installation with the
same meter reading reason must be entered at the same time.
An upload without previously creating a meter reading order is only possible for
the following meter reading reasons:

01 Periodic meter reading

An order creation for meter reading reason Periodic is only possible if a
corresponding schedule record can be determined. In Customizing for Meter Reading
under Basic Settings ->Define Control Parameters for Meter Reading Data Processing
in the Interval for MR Order Creation During Upload of Periodic Results field, you
can enter an interval to determine the relevant schedule record based on the meter
reading date.
You can also enter the planned meter reading date. The interval is not taken into
account in this case. The corresponding schedule record is accessed directly.
08 Meter reading upon technical installation
Meter reading results for technical installation can be uploaded outside of the
installation transaction. These meter readings are then added when installation
takes place.
09 Interim meter reading without billing
13 Meter reading on disconnection of installation
18 Meter reading on reconnection
19 Delivery meter reading
02 Interim meter reading with billing
CHANGE METER READING RESULTS
The uploaded record changes the existing meter reading results in the system.

There are two processing scenarios:

A corresponding meter reading document with a meter reading result exists for the
uploaded result. The uploaded records contain the internal ID of the meter reading
document. The Material, Serial Number, Register, Meter Reading Reason, and
Auxiliary Date fields can be ignored.
A corresponding meter reading document with a meter reading result exists for the
uploaded result. The internal ID of the meter reading document is not known and the
uploaded records do not contain the ID. In this case, the key fields of one of the
following alternatives must be maintained to identify the meter reading document to
be changed:
Serial Number, Register, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material must also be provided.
Serial Number, Register Code, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material number must also be
provided.
Point of Delivery, Register Code, Meter Reading Date, Auxilliary Date
The auxiliary date for background processing (MRDATEFORIDENTIF) must be specified
in order to identify the meter reading result to be changed. This date corresponds
with the meter reading date of the meter reading result to be changed before
processing.
If no meter reading result to be changed can be identified during the upload
process, the meter reading data of the uploaded record is not imported into the
system.

- The meter reading time cannot be changed by the upload process.

- If the meter reading data for the installation meter readings (MR reasons 21, 08,
24) is not uploaded using the internal ID of the meter reading document, the
information on the meter reading reason must be specified in the uploaded record.
UPDATE METER READING RESULTS
The uploaded record can either change the existing meter reading result in the
system or it can generate/enter a new meter reading result. This process is a
combination of the two previous processes.

There are three different processing scenarios:

A corresponding meter reading document with a meter reading result or a meter

reading order exists for the uploaded result. The uploaded records contain the
internal ID of the meter reading document. The Material, Serial Number, Register,
Meter Reading Reason, and Auxiliary Date fields can be ignored. The uploaded record
changes the existing meter reading result or creates a new result in the system.
A corresponding meter reading document with a meter reading result exists for the
uploaded result. The internal ID of the meter reading document is not known and the
uploaded records do not contain the ID. In this case, the key fields of one of the
following alternatives must be maintained to identify the meter reading document to
be changed:
Serial Number, Register, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material must also be provided.
Serial Number, Register Code, Meter Reading Date, Auxilliary Date
If the serial number is not unique in the system, a material number must also be
provided.
Point of Delivery, Register Code, Meter Reading Date, Auxiliary Date
The auxiliary date for background processing (MRDATEFORIDENTIF) must be specified
in order to identify the meter reading result to be changed. This date corresponds
with the meter reading date of the meter reading result to be changed before
processing.
- The meter reading time cannot be changed by the upload process.
- If the meter reading data for the installation meter readings (MR reasons 21, 08,
24) is not uploaded using the internal ID of the meter reading document, the
information on the meter reading reason must be specified in the uploaded record.
If no meter reading result to be changed can be identified during the upload
process, a meter reading order is identified for the uploaded result or in no meter
reading order exists, a meter reading document is generated and the meter reading
result is entered in the system.

No meter reading order exists for the uploaded meter reading result.
In this case, the key fields for one of the following alternatives must be filled:
Serial Number, Register, Meter Reading Date
If the serial number is not unique in the system, a material must also be provided.
Serial Number, Register, Meter Reading Date
If the serial number is not unique in the system, a material number must also be
provided.
Point of Delivery, Register, Meter Reading Date
If no meter reading order exists for the uploaded meter reading result, you have to
enter data in the meter reading time (MRTIMEFORBILLING) field in addition to the
key fields described above. All meter reading results of an installation with the
same meter reading reason must be entered at the same time.
UPLOAD CUSTOMER-SPECIFIC FIELDS
it is possible to upload customer-specific fields (also see customer enhancement
EDMMR001). The table EXTENSIONIN is used for this purpose. The customer-specific
data is not uploaded with the standard data, but in a separate table. The table has
the following structure:

Structure
Valuepart1 + Valuepart2 + Valuepart3 + Valuepart4
The valueparts consist of strings of 128 characters. The key data and customer-
specific data is stored there. You enter the structure in the structure field. (If
you use a BAPI to upload meter reading results, there is only one segment and
therefore one structure).

If you use the short material number with a maximum length of 18 digits, the
structure is BAPI_TE_EABL.

Structure BAPI_TE_EABL contains the following fields:

Material number, 18 digits

Serial number
Register
Meter reading reason
Meter reading date
Meter reading document number
Register code
Point of delivery ID
INCLUDE CI_EABL
If you use the long material number with a maximum length of 40 digits, the
structure is BAPI_TE_EABL2.

You can find more information about the material number extension in Customzing
under Cross-Application Components -> General Application Functions -> Field Length
Extension.

Structure BAPI_TE_EABL2 contains the following fields:

Long material number, 40 digits

Serial number
Register
Meter reading reason
Meter reading date
Meter reading document number
Code for register identification
Point of delivery ID
INCLUDE CI_EABL

EXAMPLE
NOTES
Messages are returned in the RETURN parameter.
FURTHER INFORMATION

PARAMETERS
EOSBUPLOADDATA
EXTENSIONIN
METEREADINGRESCHANGE
METERREADINGRESULTS
METERREADINGRESUPDATE
RETURN
X_AUTHORITY_MTREAD_CHECK
X_USE_OPEN_LOG
EXCEPTIONS
FUNCTION GROUP
MTRREADDOC

ABAP Short Reference Vendor Master (General Section)

This documentation is copyright by SAP AG.

Length: 14653 Date: 20200610 Time: 120733 sap01-206 ( 55 ms )