• Welcome to Winshuttle Studio
• Studio 11 Release Notes
• Studio 11 System Requirements
• Studio 11 Help
  • Getting started
    • Getting started with Studio v11
    • Step 1. Download
    • Step 2. Install
    • Step 3. Licensing
    • Step 4. Open
    • Finding your way around
    • Where is it in Studio v11?
  • Best Practices
  • Setting up
    • Setting up Studio 11
    • System requirements
    • Connecting to SAP
    • Authorization check
    • Required SAP Authorizations
    • What types of data files can I use?
    • GUI scripting and Windows scripting
    • Studio 11 options
    • Change the language
    • Error management and trace files
    • Single Sign-on (SSO) with 64-bit Studio 11
    • EP logon
    • Add an SAP system
    • Winshuttle Function Module
    • Admin info
      • Installing and uninstalling
        • Installing and uninstalling Studio 11
        • Single .exe: Fresh installation and upgrade
        • MSI: Fresh installation and upgrade
        • Network installation using Microsoft SCCM
        • Network installation using SysInternals PsExec tool
        • Uninstalling
        • How to create a response file
        • Coexistence of Winshuttle 10.x products with Studio 11
        • Access DB office 2007 (32-bit) installation behavior
      • Custom Winshuttle roles for the SAP server
      • Configure Studio 11 before first use
      • Winshuttle utility kit
  • Transaction
    • Create a script for a transaction
    • Recording
      • Record the script
      • Step-by-step guides
      • Recording modes
      • Using Transaction with Virsa Firefighter
    • Mapping
      • Map the fields
      • Map the fields in Excel
      • Map fields to an Access database file
    • Looping
      • Add a loop
      • Add a loop in Excel
      • Add a loop in Access
      • Advanced looping
    • Running
      • Run a transaction script
      • Use macros to run a script
      • Run a Transaction script from the command line
      • Run settings for Transaction
    • Schedule a Transaction run
    • View run logs and details
    • More Transaction commands and features
      • Record long text
      • Map and upload long text
      • Change the data file type
      • Open an existing data file
      • Add If conditions
      • Add transforms
      • Limit input values
      • Change the padding
      • Skip screens that are not present in the SAP system
      • Require data for a field
      • Attach documents
      • Filter Mapper settings
      • Restore an original recording in Studio
      • Download data from SAP
      • Chain scripts
      • Write headers
      • Change the transaction code
      • Change the core recording time
      • Publish a script with an Excel data file
  • Query
    • Create a script to query SAP
    • Choose fields
      • Choose query tables and fields
      • Choose query fields in an InfoSet or an SAP Query
      • Choose logical databases
      • Choose query fields from a recording
    • Define criteria for a query
    • Mapping
      • Map the query fields
      • Map query fields to Excel
      • Map query fields to Access
      • Map query fields to a text file
    • Running
      • Run a Query script
      • Run a script from Excel
      • Use macros to run a script
      • Run a Query script from the command line
      • Run settings for Query
    • Schedule a Query run
    • View run logs and details
    • More Query commands and features
      • Create joins between tables
      • Use the In operator
      • The Like operator and wildcard characters
      • Use dates as criteria
      • Change the data file type
      • Chain scripts
      • Add transforms
      • Write headers
      • Publish a script with an Excel data file
      • Authorizations
  • Direct
    • Create a script from a BAPI
    • GL document with multiple currencies
  • Runner
  • Working with LMS

Winshuttle utility kit

The Winshuttle Utility Kit provides seven tools that make it easier to work with Studio v11.x and to upgrade from earlier versions of Transaction and Query.

Upgrade tools:

• Import ALFs
• Import Schedules
• Convert 10.x and lower version Linked Scripts

General tools:

• License Switcher
• Edit Published Scripts
• Manage Add-Ins
• Generate Command Line/Macro

Import ALFs

Currently auto logon files (ALFs) are not recognized in Studio v11.x, which uses auto logon credentials (ALCs).

You can use the Winshuttle Utility to import and convert all Transaction v10.x and Query v10.x and earlier-version ALFs to ALCs. The converted ALCs will be displayed in Studio v11.

The ALFs will not be deleted by default, and they will remain available in the Transaction or Query folder.

If Studio v11 already contains an ALC for the same SAP system (for example, W6R_800), the ALF will be converted and the ALC will be saved as a copy (for example, W6R_800_1).

Note: The utility will show a list, highlighted in yellow, of any ALFs that could not be imported.

1. Click Import ALFs.
2. Click Start Importing Now.
3. Click Open.
4. Navigate to the ALF file that you want to import, select the file, and click Open.

   By default, .Alf files are stored in the C:\<username>\Documents\Winshuttle\<product>\Alf folder, where <product> is Transaction or Query.

5. Repeat steps 3-4 to open all the .Alf files that you want to import.
6. Click Next.
7. Select the files that you want to import, and then click Import.

   Note: You can also delete scheduled scripts by selecting them and then clicking Delete Selected.

8. After the files are imported, click OK.

Studio v11 ALCs are stored at C:\Users\<username>\AppData\Roaming\Winshuttle\Connector\11\LogonSettings.xml.

Import Schedules

Scheduled tasks that were set up in v10.x are not automatically recognized by v11.x. Now you can use the utility to convert them.

The utility shows you all tasks that were scheduled in Transaction v10.x and Query v10.x and earlier versions.

After all the scheduled tasks have been imported, the older versions are deleted, and the tasks can be run through Studio v11 only. This prevents duplicated runs.

The status of imported scheduled tasks will say Not yet run even if the task was run in v10.x.

Note: The utility will show a list, highlighted in yellow, of any scheduled tasks that could not be imported.

1. Click Import Schedules.
2. Click Start Importing Now.
3. Select the scheduled scripts that you want to import, and then click Import.

   Note: You can also delete scheduled scripts by selecting them and then clicking Delete Selected.

4. After the scheduled scripts are imported, click Close.

Convert 10.x and lower version Linked Scripts

Currently v10.x scripts cannot be linked with v11 scripts, and v10.x linked scripts cannot be submitted to Foundation v11. Instead of converting the scripts individually, you can use the utility to do the following:

Convert script chains that were created in v10.x to the v11 format. The chained scripts will be created in the same folder and have the extension _v11, unless you check the Overwrite original box.

If any or all carry settings (data file, start row, end row, number of records, sheet) are carried forward from the first v10.x script, the converted v11 script chain will show the carry setting as Custom, with all of these settings carried from the first file. All other settings, such as ALC and backup SAP, will be picked from the individual files.

If the v10.x script chain has no carry settings defined for the first script, Studio v11 will apply the Run settings - All from Individual Script setting.

1. Click Convert 10.x and lower version Linked Scripts.
2. Click the Browse script button, navigate to the first linked script in the chain, click Open, and then click Open again.
3. Only linked scripts can be opened. If you select an unlinked script, an error message will appear.
4. To replace the original script, check the Overwrite Original box.
5. Click Convert.
6. Click Close.

License Switcher

Use the license switcher to change from Connect mode to Foundation mode or vice versa by selecting that mode and clicking Save.

If you are using this utility for the first time, you will be prompted to open Studio in the mode that you are trying to switch to.

If Studio does not recognize the Connect password or the Foundation website address and you are unable to log on, you can click Reset Activation, and it will prompt you to select the mode from Studio and provide a different password or a new website address.

Switch modes

1. Click License Switcher.
2. Click Connect or Foundation.
3. Click Save.

Change the password or website

1. Click License Switcher.
2. Click Connect or Foundation.
3. Click Reset Activation.

Edit Published Scripts

Use this tool to edit published scripts without republishing them from Studio.

1. Click Edit Published Scripts.
2. Click the Browse Excel file button, browse to the data file to which the script is published, click Open, and then click Open again.
3. Select the script.
4. Click any of the following options:
   • Reorder the scripts if more than one is published to the same sheet. Use the arrow buttons to move a script up or down in the order.
   • Edit the following fields:
     • Display Name
     • Sheet name (check the Bind to this sheet box to ensure that sheet is used)
     • Start Row and End Row
     • Backup SAP data
     • Launch SAP GUI
     • Skip field indicator

     (These fields might vary depending on whether the published script is for Transaction or for Query.)

     Note: If you are using Foundation mode, the Edit button is not available.

   • Add or delete scripts.
   • Undo an added script.
   • Unlink a script from a chain (this is helpful if you are getting an error during the run and you want to find out which script contains the error).

Manage Add-Ins

Important: To manage add-ins, you must run the utility kit as an administrator. Start the kit by right-clicking it and clicking Run as Administrator.

1. Click Manage Add-Ins.
2. Click the add-in that you want to change.
3. Do one of the following:
   • Register or un-register the add-in.
   • Register or un-register the macro. If the macro is unregistered, Run will no longer be available.
   • Load the add-in or macro if it is installed but has not been loaded.
   • Repair the add-in or macro. Repair basically un-registers and then registers the add-in or macro.

Generate Command Line/Macro

Command line code and macro code is complex and hard to prepare. This tool uses the run settings that you enter to automatically generate command line and macro code that you can copy and run on the command line or paste into an Excel macro.

Generate a command line

In Connect mode, provide the script file and data file paths. The rest of the fields are optional.

In Foundation mode, click URL and enter the path to the script on the Foundation site, or click Local Script, click the Browse button, navigate to the script, and click Open.

If you click ALC, type the SAP server description. If you click Server-Client, type the values for Server and Client ID.

Generating macro code

The utility for creating macro code generates only the Winshuttle portion of the code. You need to provide the rest of the macro code.

You have options for both published and unpublished scripts.

To specify the log column or cell, row selection, and run type, click more commands. For the run type, you can choose Run options, Debug options, or Validate options.