The problem with green warnings is that while the script passes the OK code and already at the next screen, SAP does not proceed to the next screen. Worse even, troubleshooting is rather difficult as SAP will not tell you the error message through the log field (only if you manually simulate the same data entry in SAP will you see the warning message).
What you will see in the Winshuttle log field is that the script fails to find the first field on the next screen. That is how I usually recognize that SAP has not managed to proceed to the next screen, so I am probably dealing with a green warning.
Where I face these issues is usually the MRP fields in material master, where certain field value combinations bring the warning up. The problem is that I cannot predict what combinations will bring up the error, so usually I only face it when the end-user complains.
The solution for me was to control data entry instead of handling this through the script, which I found rather difficult.
It would be nice if SAP passed the content of the green warning message to the Winshuttle log, not sure why it does not.
It works for the yellow warning (extended log) and the red error (short log).
That way at least troubleshooting would be easier.
Attila
------------------------------
Attila Nemeti | Master Data Operational Excellence Specialist
Celanese International Corporation | [City] | +3616277652
------------------------------
Original Message:
Sent: 11-09-2018 11:14
From: Sigrid Kok
Subject: Soft warning stops script
Hi Benjamin,
Warnings usually do not stop scripts from running. In my almost 9 years with working with Transaction/Sutido, I may have run into this once or twice, and I have created a lot of scripts.
The additional enters are not captured nor needed in the script. Winshuttle will usually take care of that for you. If you do run into one that causes issues, and some have stated they have run into this , too.
If you'd like to share your script, some of us in the community may be able to think of a workaround. Read only/disabled fields are often in that state because of other data you have entered, so often IF statements based on that other data may help.
If it's not just disabled fields causing the warnings that stop the script, I would also suggest that you open a ticket with Support, so that we can get to the bottom of what is happening and get it fixed, if at all possible. This will help you and anyone else who runs into this issue.
One last suggestion - if the t-code is really problematic, you might consider a BAPI or remote-enabled function module, if there is one.
Best Regards,
Sigrid
------------------------------
Sigrid Kok
PSE | Winshuttle North America
Original Message:
Sent: 09-26-2018 17:22
From: Benjamin Kielas
Subject: Soft warning stops script
When I am in IW52 or other transaction and a soft warning comes up when recording I enter through pressing enter a few times until it goes way. When I go though debug those additional enters do not show up. How do I add those enters in to pass though the soft warning?
------------------------------
Benjamin Kielas | SAP Master Data Team Lead
Generac Power Systems, Inc. | [City] | 262-544-4811
------------------------------