cancel
Showing results for 
Search instead for 
Did you mean: 

SAP GuiXT -come out of IW51 without save of data entered

Former Member
0 Kudos

Hi,

We facing an issue with GuiXT. When user click on GuiXT push button on IW51 screen then user come out of IW51 to initial SAP screen without save of entered data. After 2-3 attempt user able to enter and save same data in notification. This issue is intermittent and for many users. Could you please suggest/help to find out root cause of issue.

Please see attached document for error and SAP logon pad details.

Thanks

Harsh

Accepted Solutions (0)

Answers (2)

Answers (2)

marc_marco
Contributor
0 Kudos

Hi Harsh,

Dose this GuiXT pushbutton perform some action on Table control ?

if the notation in the GuiXT script is column number you can replace it ith the technical name , that might resolve this problem.

Can you share the Guixt script  ?

see exemple :

Regards,

Ziv

Former Member
0 Kudos

Hi Ziv,

I am new to GuiXT scripting. There are around five push button. And what I guess for each one there is background scripting linked to Table control. I have attached one screenshot for sample. This issue could happen for any one from those buttons. Surpise it does not happen for me. I am on GUI 730. However issue is intermittent for users (GUI720). What I guess it is something related to GuiXT scripting or GUI logon pad. Please suggest.

Thanks

marc_marco
Contributor
0 Kudos

Hi Harsh,

You need to change these scripts with technical name  , just click on the F1 in the required column and get the technical name

see exemple :

for  your exemple it should be set cell[Table,technical name..,30] replace the technical name as show above with the column that should be filled with by the Guixt Script

After you change , test it in your 730 gui version if it works ok then goto other user with 720 gui version and try again with this modified script.

Good luck

Regards

Ziv

MTerence
Active Contributor
0 Kudos

Hi Harsh,

Check by re-installing SAP GUI.

In case if this still exist, you need to replicate the issue and raise to SAP, so they can assist you to provide solution.

This looks like a Basis issue than transaction issue, please check in Basis Forum also.

Regards

Terence