You are on page 1of 2

1) Update Test Script.

2) Involved in day to day support on customer basis.


3) Prepared Functional specifications as per business requirement.
4) Prepared Functional specifications for DM reports as per business requirement.
5) Involved in Unit testing and documentation of test results.
6) Involved in preparing End User training Manual.
7) Involved in preparing product manuals, Demo presentations and designing screens

Where some answers:

1)What are the possible changes required for device info record(billing specific)?how it works?

DIR should be create has master data records and only change exploradicatly. Within the
Installations you might have to change from a DIR confirguration to another.

2)Do we configure static notes for the meter reading order? What r the notes in real time
scenario?

YES, see examples:

Estimated consumption

Real consumption

Parcial Estimated consumption

Migrated consumption...

3)How to Scheduled mass maeter reading order jobs in the back grouond? What is the TCode for
each

job? Transaction EL09 - Mass MRO creation.

4)Do we monitor these jobs in SM37? for Utility also? what r the different possible variants?

Yes, SM37 is used also in IS-U.

SLG0 - Application logs.

EMMA - BPEM - EMMA Cases.


5)How to upload the periodic meter readings? What are issues we face in realtime?

By Idocs or Manually. If it's done by Idoc's, customer validations need to be specified and
implemented trought a ABAP development/enhancement. Error Handling is the biggest
issue. Define fallback scenarios. Provid Business w/ tools to diagnosticate and solve the
errors. Request replacemente Read (rectification) and so on.

6)How to generate report on implausable meter reading results by portions/MR Units/Period)?

It already exits. Program RELEABL3.

7)How and why we need to configure validation process for the meter reading(
plausible/implausible) and what would be the values?

8)How to define the tolerance limits?

You might also like