testing in SAP Utility

[Former Member]

Hi All ,

Can you please let me know about testing in SAP Utility .

1. generally how we perform testing in SAP utility ?

2. how many methods or types avilable in SAP utility ?

3. what is the procedure for SAP ISU testing ?

Regards

Rahul

[Former Member]

hi Rahul.

testing in SAP IS-U is done by creating master datas(one can use MDTs) and then using these data to create bills

utilizing different scenarios ,one can either be given set scenarios(in form of test cases) or one can directly experiment and play around in the system with ones own scenarios.

there can be manual and regresion testing,manual been the more interesting one as one has the liberty of playing with the system.

I dont know abt the procedure for sap isu testing, i guess you have to have an access to an isu system ,know how to create master data and create bills.

if you have any more queries abt testing in isu kindly revert back

cheers,

Rakesh..

[Former Member]

Here are list of things that you need to do

For ISU only system, you can perform following end-to-end test

Create Business Partner

Create Contract Account

Create Connection object

Create Premise

Create Installation with Point of Delivery

Create Device location

Create Connection

Create Full technical installation

Create Move-in (contract will be created in background)

Process initial meter reading

Schedule periodic meter reading

Check meter reading in EDM

Create Invoice

Pay Bills

Process GL

For ISU with CRM, add following steps

You need to create Business partner and Business agreement in CRM

Technical master data in ISU

Create Contract from CRM

ISU will create move-in and contract

Then continue rest of the steps starting meter reading from above.

If you client is in deregulated market then you need to test IDE (market communication) and whole 9 yard of contract modifications also.

[Former Member]

Hi there,

There are various test cycles that utilities goes through. Below is the different test cycles:

1. Unit Tesiting - Which is transaction code testing and establishing that screens and buttons are working.

2. String Testing - Which testing a business process within a IS-U for Device Management Meter Reading Process.

3. System Intergration Testing - Which is the IS- U from end to end. From Creating the Business Partner to Invoicing the Busines Partner. SIT is sceanrio bases testing.

4. User Accectance Testing - This testing involves Business User Testing the system by performing the daily activities which they normally perform.

5. Regression Testing- Is testing all the failed test conditions of the previous test.

6. Batch Testing - This testing involves testing all the Batch jobs that must be executed by Periodic Processing

7. Negative Testing - Is testing all abnoraml things which must not occur on the system , which users normally try.

Hope this helps

Angelo Carolus

[friedrich_keller]

Hi,

and last but not least two wisdoms:

- always test on migrated data already from the beginning. This also means that you have to setup 2 scenario for each test script: one based on migrated data and one more based on data created in the system ba online transactions

- tests can only be replaced by tests 🐵

Cheers,

Fritz

PS: do no forget the online stress test

PSS: do not forget to arrange all test activties properly otherwise mile stones such as correction close might prevent you in implementing correctons ... this rule is almost always ignored, unfortunately!

[william_eastman]

And another last important test for utilities implementations is Parallel Testing. it is vital to test the meter reading, billing and payments with same data as in production for a period so that the calculations, printed docs, etc can be compared to those that are done already in the current system. This is a special flavor of the batch testing process.

regards,

bill.

[Former Member]

solved it own

[Former Member]

Hi All,

What are the wireframes in SAP ISU testing? like we have in web testing

When we write the test scripts then actual and expected result we write.

How do we khow that we have got expected testing?

With what we compare our current testing. with Functional specification or technical specifiaction or what?

Like If there is scenario  for as above String Testing -  Which testing a business process within a IS-U for Device Management Meter Reading Process.

then

Does functional consultant give any document to SAP testers for testing that this is what is expected result?

I am not clear about it can somebody help me on this?

Thanks, Madhur.