Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

eCATT GETGUI Cannot Find Screen Element in Replay Mode

Former Member
0 Kudos

Hi,

During HCM BP install, received the following error.

eCATT script /HRBPUS1/SCPR20_I001_KO2

Error in eCATT command GETGUI
Cannot Find Screen Element  in Replay Mode

Error Occurred in Previous SAPGUI, GETGUI, or CHEGUI Command. Due to the Start Option Settings of the Error Behaviour, Processing Was Cancelled and the Current Command Not Processed.

Any help would be greatly appreciated. Regards!

3 REPLIES 3

Former Member
0 Kudos

>

> Hi,

> During HCM BP install, received the following error.

>

> eCATT script /HRBPUS1/SCPR20_I001_KO2

>

>

Error in eCATT command GETGUI
> Cannot Find Screen Element  in Replay Mode
> 
> Error Occurred in Previous SAPGUI, GETGUI, or CHEGUI Command. Due to the Start Option Settings of the Error Behaviour, Processing Was Cancelled and the Current Command Not Processed.

>

> Any help would be greatly appreciated. Regards!

Hi David,

Are you installing builing blocks for HCM BP?

Please describe the background on where you are getting the error.

Probable reason for error : The GETGUI command is used inside the eCATT script to take/retrieve some values from a field in a screen.While you are executing the script for installation,this field is missing/not able to be identified by the GETGUI command and hence the error.In simple terms,there is a mismatch in the screen/field it seems.

Hope this info helps.

Regards,

SSN.

Former Member
0 Kudos

Hi David,

possible cause of this error could be due to the change in the screen/fields...

You can try executing this by replacing the screen to Optional where u find this error.

->processedscreen ->Active 'X' to 'O'.

Hope this helps you..

NV.

Former Member
0 Kudos

Thanks everyone.

SAP indicates we are on a patch level higher than what is supported by best practices. We have worked through some of these issues and are moving forward.