Banner_Blog.jpg
Subscribe

Search

When Good Scripts Go Bad: A Guide to Trouble-Shooting Winshuttle Transaction

Posted by James Thomas on Mar 08, 2016

Share:     

Blog_Good-Bad.jpg

More and more companies are investing in big data to identify trends and spot business opportunities. Never has it been more important for your small data to be accurate so the big picture coalesces correctly.

Winshuttle Studio provides your business with the tools to manage data on your terms. With the ability to create customizable scripts that manage the data elements important to you, Winshuttle is the premier tool in the Data Maintenance market.

But how can a Winshuttle author – the person responsible for creating and maintaining your Winshuttle investment – effectively trouble-shoot scripts. Here are four go-to strategies that should be investigated as groundwork for addressing Winshuttle failures:

Is the script running the most current version of the software?

Errors often occur because the user is running a different version of the software than the script was composed in. There are a few ways to check this.

First, go to Help > About and view the version of the software the user is running.

Winshuttle_blog_image_1.png


The version of the software used in the script can be found in the log:

Winshuttle_blog_image_2.png


To update your software, go to support.winshuttle.com, click ‘Downloads’, and follow the path to the most recent release.

Another good option is to set up a daily check for any recent updates. When you open the software, the Winshuttle checks to see when the last time a software update check was executed. If a check has not been done in the last 24 hours, the check is performed.

To set this up, go to Tools > Options > Auto Update, and set this to ‘after 1 days’.

Winshuttle_blog_image_3.png


Are User-Specific Parameters set up?

Does the user have parameters set in transaction su3 that are populating fields in the script? If the answer is yes, the parameters could come into play when the script is running, causing unexpected results or failures. Even more frustrating, the script could be working for one user and failing for another user.

To solve this problem, go to transaction su3 for the user experiencing the failures and review the entries in the ‘Parameters’ tab. Remove entries, save, and log out of SAP. When the script runs again, the parameters will not default in the recording. Parameters may also be set in the transaction so investigate these as well.

Is the Launch GUI Box checked/ticked? 

If you’re receiving an error message when testing your script but are not sure why, tick ‘Launch GUI’ in the settings of the script. If this is part of a chain of scripts, the whole chain should be re-published to see this change take effect.

Winshuttle_blog_image_4.png

 

What function does the ‘Launch GUI’ box perform?

Checking the "Launch GUI" box on the Run screen enables the SAP GUI launch without using GUI Mode of recording. Winshuttle has a more detailed explanation (https://support.winshuttle.com/s/article/Why-do-we-use-Launch-GUI-Check-Box)  on their support website

Is there a problem with the transaction process? Run in ‘Stop on all Screens’ Mode to Simulate the Transaction.

Once you’ve ruled out errors in steps 1-3, it’s time to look at the specific case that is causing an error. Use the ‘Stop on all Screens’ mode to walk-through the script and see why the error is occurring.

Winshuttle is an excellent tool to accelerate your ERP’s power. If you have additional questions or are interested in learning more about Winshuttle or G3G, please contact us.

Share:     

Related Posts