eCATT SAPGUI: dealing with collapsed/ expanded nodes

[Former Member]

When you access SAP screens following a refresh or say with a different test ID, you encounter situation with some t-codes where you need to make changes to get to the default screen that the script was initially recorded with.

A classic example in my mind is ME21N, where the "Header", "Item", "Item overview" nodes are collapsed and document overview is on (see screenshot). As a result, the script fails. I am sure some of you folks out there must have faced this situation.

I am looking for inputs on how you managed this situation within the script itself.

Thanks!

[Former Member]

When you access SAP screens following a refresh or say with a different test ID, you encounter situation with some t-codes where you need to make changes to get to the default screen that the script was initially recorded with.

A classic example in my mind is ME21N, where the "Header", "Item", "Item overview" nodes are collapsed and document overview is on (see screenshot). As a result, the script fails. I am sure some of you folks out there must have faced this situation.

I am looking for inputs on how you managed this situation within the script itself.

Thanks!

[nisha_sharma1]

Hello Archana

There is a table ESDUS which stores the values for last successful execution for transaction & user  and default it in next execution for that user & transaction.

ME21N Node States with Above ESDUS table values:

Above values control the expand & collapse of nodes. (Toggle state)

Create a script for ESDUS table & insert these values & Then REF ESDUS script before PO creation in Me21n Script.

By doing this you are always referring to default one state in ME21N and your script will work in all releases & all systems.

Note: You can insert/change ESDUS table.

Regards

Nisha

[Former Member]

Thanks Nisha! Something like this was exactly what I was looking for.

Archana