Web Help

Previous versions

Contents New features in version 10.6/10.7 Bugs fixed in versions 10.6/10.7 Known issues in Transaction versions 10.6/10.7

Previous versions

New features in 10.5

Released February 13, 2013

• The Winshuttle Function Module recording mode leverages the SAP-certified Winshuttle Function Module (WFM) for TRANSACTION to avoid difficulties with non-batch mode scripts that do not run when SAP BASIS 7.00 Support Package 24 and other related updates are installed. Note: the Winshuttle Function Module mode does not replace GUI scripting, which is still available.
• The IF on index setting now supports SAP line selection.
• Winshuttle TRANSACTION is compatible with Windows 8.
• Winshuttle TRANSACTION is compatible with Microsoft Office 2013.
• The Winshuttle RUNNER add-in works in Microsoft Excel 2013.
• Winshuttle TRANSACTION is compatible with SAP GUI 7.30.
• Documentation for Winshuttle products is available in the product as web help and on the Winshuttle Community site. PDF documents are no longer available.
• The latest ERP connection is now integrated.
• A SAP trace is now available from the Error Management tab to trace calls through the Winshuttle Function Module for TRANSACTION.
• BapiRule.xml file includes a listing for BAPI_QUALNOT_MODIFY_DATA
• Scripts recorded in 10.4 or earlier versions of TRANSACTION work with Transaction Winshuttle Function Module mode without re-recording.

Bugs fixed in 10.5

• Multiple RFC Connections generated executing linked scripts
• Extended logs disabled in WFM
• No Dropdown Menus with SAP Logon Pad 7.30 and Transaction 10.4
• Current "if on index" does not support highlighting a line [selected]

Bugs fixed in 10.4

• Incorrect error descriptions in log message for FV60 and KS02 Tcodes
• For a Direct based script, fixed value uploads contained within multi-sheet loops result in an error
• When column width is below a minimum values, error occurs on trying to view or print mapper details
• If the value of ‘Number of rows to remain empty before run stops’ is more than 499, Run fails
• Macros for Validate and Run cannot be imported one after the other
• Connect error logs are not getting captured in the application trace
• Runner for Transaction mapper can be viewed on a locked script as well
• Extension of evaluation copies is made available again
• PA40 tcode recording errors out at the end in some customer environments
• Scripts recorded in GUI scripting mode hang after recording/run in some SAP environments
• Connect connection indicators do not work as expected in FR and NL locales
• If condition values in a script recorded with GUI scripting mode are rounded off to last three digits leading to incorrect results
• No intimation is received by the user in case a migration request for a Connect license is successfully sent
• GUI scripting record/run fails if GUI XT component is installed on an SAP system
• When you publish a cell mapping Transaction script to an excel file, headers are not written
• Refresh issues on trying to schedule a Transaction script when Connect logon credentials are not remembered
• Grid resizing issues in Mapper and Home screen
• For some Tcodes,e.g. PP01, MM02, the long texts recorded using Non Batch method, result in an error
• Connect logon dialog ‘Remember Password’ setting will be checked by default
• Write Headers is not available for cell mapping scripts
• {from to} and {between} operators fail for values containing text
• For a Direct based script, if the first condition fails, rest of the if conditions are evaluated as false
• Output tables such as for Read List BAPIs can be filtered based on one of the output fields by using an ‘if on SAP’ condition
• Use a wildcard character in list of values to denote different possible values for a field
• ROI chart label enhancements
• Connect logon labels are truncated in some locales for add-in
• Characters ‘<’ and ‘>’ cannot be used as comparison values in if conditions
• Cell based mapping does not work with line items identifiers in hidden columns
• UI issues in the List of values pop up
• BCD data type fields, if left blank for a Direct-based Transaction script, lead to errors in the log message
• Blank rows in between records in a data file are considered as transactions
• In some cases, error message "The transaction was terminated by the user" appears in log column when a script is run repeatedly

New Features Added in Winshuttle TRANSACTION version 10.3

• Script metadata shows the Winshuttle program version that the script was built with.
• A chart shows log activity for the previous 30 days.
• Winshuttle CONNECT-based licensing integration is now available. CONNECT provides centralized control of Winshuttle product licenses for your organization.Added in Winshuttle TRANSACTION version 10.2

Bugs fixed in version 10.3

TRANSACTION and RUNNER for TRANSACTION

• If Winshuttle Runner is installed using a 64-bit application, the Generate Support Information feature lists Runner for Transaction, Runner for Query and Runner as three different products.
• An error occurs if logon details are recaptured while editing a scheduled task.
• Write headers does not write header for Extended Log column.
• Running a Transaction script created using Authority_Check function module gives incorrect results.
• On Validating an Access data source script, an error occurs when the if condition around the loop equates to false.
• Run on Errors does not work as expected if the data file is protected.
• Specify row for update does not work correctly if the field being updated is a check box or a button click.
• If you run a column mapping script on selected or filtered rows and then open a cell mapping script, an error appears.

TRANSACTION

• Aborting creation of a DIRECT-based script from the consumption screen does not allow the user to record a Transaction script in the same instance.
• Filters do not work correctly for all options in the Expert mode in the mapper.
• If a Transaction (64-bit) screen is kept idle for 10-15 minutes after logging into SAP and selecting the GUI scripting mode of recording, errors are returned from SAP.
• If on indexed field cannot be edited for a script with cell-based mapping.
• An error message appears if the Excel cell range used for importing a Validation list contains a single value.
• For cell mapping scripts, a field inside a loop cannot be mapped as a download field if loop start row = 1.

TRANSACTION and Runner for TRANSACTION

• TRANSACTION supports Office 2010 for both 32-bit and 64-bit versions. TRANSACTION has two versions 32-bit and 64-bit to enable support for 32 and 64-bit of Office 2010.
• TRANSACTION is now localized in Spanish and Dutch.
• TRANSACTION scripts now work with Google Spreadsheets as a data source.
• "Validate by list" property of a field can be used to restrict set of possible values that this field can have.
• TRANSACTION supports embedding macros in data files from the TRANSACTION script and also provides default macros to auto split documents when data exceeds transaction limits.
• If the "Application trace" setting is ON, the user will get a warning message indicating that the setting can result in a slower run.
• TRANSACTION script will be automatically closed after a scheduler run if the Advanced run option - Close application after run is checked.
• "Select SAP values" function is supported from macros as well.
• "Write headers" button is available from Client as well to allow users to create Excel templates to upload data.
• GUI scripting supports "Skip screen if not found" property.
• Excel data files can be sent as an email attachment at the end of a scheduled run. TRANSACTION scripts can be scheduled to run on console.
• The number of files in the Recent Files list can be configured from the Application options.
• Default "Skip field indicator" can be set from the Application Options.
• Log header information can be customized from the Header Log Details option.
• "Backup SAP data" option is enabled for Access data source as well.
• Advanced run option "Append timestamp to SAP log messages" appends time stamp to log messages returned in the data file.
• For Direct based TRANSACTION scripts, an additional column has been added in the mapper to specify Table/structure name.
• "Run not posted" setting has been enabled for Cell mapping TRANSACTION scripts.
• Identifier based loops are supported in Direct based TRANSACTION scripts for cell mapping.
• Validation log column is available as a field in the mapper and can be set during script design time and also from the run screen.
• If "Skip screen if not found" property has been set for non-applicable cases e.g., inside a loop or multiple commit codes, a warning message is issued to the user.

TRANSACTION

• Auto mapping is enabled for cell based mapping scripts.
• Writing headers for cell based mapping has been enabled to allow users to create Excel forms in an untitled preview.
• Publish dialog box shows the data file path currently selected and saved in the TRANSACTION script with an option to change.
• Validation error messages for the "Validate" feature appear during design time in addition to Run.
• The detailed line recording values appear at correct row in the untitled preview, next to the line identifier rows.
• A parent category and classification view is provided in the Direct script consumption screen.
• Users are allowed to copy rows from a construct within the same script and to a different script as well.
• Notes can be added to the mapper fields and screens for Direct based scripts.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Users are not able to upload multiline text.
• Some UI strings are not localized in all supported languages.
• If an "If" condition around a loop evaluates to FALSE for a row, all expected transactions after that are not processed irrespective of the result of the "If" condition.
• Validating a protected sheet with extended logging on, results in an error.
• Some BAPIs result in an application termination with SAP GUI 720.
• If two BAPI based TRANSACTION scripts are linked together, the second BAPI goes to an infinite loop in some cases.
• Linking a GUI scripting script with a TRANSACTION script of any other mode and doing a "validate", posts data into SAP instead of validating.
• If a cell is mapped with multiple SAP fields, the Excel file Validation goes for entire loop row range.
• Users are unable to schedule a run in TRANSACTION if Windows is installed in any other location except C drive.
• Space or tab in the header loop identifier results in inconsistent data upload.
• Error on running a published Cell based file with range based loop with End row = 0.
• For a cell based TRANSACTION script with no line items, validation error is written in incorrect log cell.
• Validation is always performed on the active sheet in the Add-in irrespective of "Bind to Sheet" setting.
• TRANSACTION macro does not allow validation on published scripts.
• Fixed errors are not highlighted with prefix or color for Direct based TRANSACTION scripts.
• If TRANSACTION application is installed using Citrix, an error occurs on clicking the "Generate Support information" button.
• The "Log Column/Log Field" row can be disabled by selecting the "Log Column/Log Field" row along with some other rows.
• Validating a data file with line items on erred out records results in inappropriate log messages.
• "Skip screen if not found" does not work with more than screen.
• Authorization check returns wrong values for function group authorizations for some users.
• The naming of log field for Access data source is inconsistent across different screens.

TRANSACTION

• Direct based TRANSACTION script accepts invalid cell name in the "if condition" dialog.
• Not able to put IF condition around the complete recording for log column is empty when Access is the data source.
• "Skip transaction if empty" is available for modification of cases it is not applicable to, leading to user confusion.
• If the Spreadsheet setting is turned off, a wrong dragging icon appears in the preview section for batch mode TRANSACTION scripts.
• Publishing a cell based TRANSACTION script prompts for the modification of the Excel file even though no headers are being written in the file.
• Connection to SAP is not closed on cancelling a recording from the Recording properties screen until the user exits the application session.
• Filter based transactions like ME51N, ME52N result in application error if Non Batch recording mode is used.
• Loops indicator line is not displaying properly if manual additions are done to the mapper screen.
• "Read from SAP not allowed on this row" message is not cleared from the status bar resulting in user confusion.
• Publish icon is enabled for Direct based TRANSACTION script even when none of the fields are mapped.
• Publish option is disabled when a template is downloaded and saved using "Save as" button instead of Save button.
• Warning does not appear while re-mapping a column having its name in lower case in mapper
• Changing the data source of a TRANSACTION script having loops from Access to XML results in syntax error.
• An error occurs on clicking "Bind to sheet" or "OK" button on the publish dialog while the file is getting published.
• Notes are not properly saved for screen fields.
• A "Fill in required fields" error occurs at the beginning of every recording if the SAP GUI size is changed from its default setting.
• UI issues are seen on "Open" and "if" icons on some locales.
• Cell mapping on the first row of the preview fails if the Spreadsheet gear option is turned off.
• A run time error occurs after recording a TRANSACTION script for Tcode VT01N.
• On a Citrix environment, users cannot launch application if the application options file has not been created due to user authorization problems.
• No way of changing loop type on switching from Cell based to Column based mapping.
• Attempting to import an empty DIRECT script in TRANSACTION results in an error.
• On switching data source from Excel to XML and back to Excel, If condition button gets disabled.

RUNNER for TRANSACTION

• If the Data file path contains a non-existent Access data file, it results in an incorrect error in the mapper screen.

Added in Winshuttle TRANSACTION version 10.1 Hotfix 2

New Features

Transaction and RUNNER for TRANSACTION

• "Number of rows to remain empty before Run stops" setting in the Application options can now take a value up to 999

New Features

TRANSACTION and RUNNER for TRANSACTION

• Users can validate data in an infopath/adobe/HTML form before uploading it to SAP.
• DIRECT based transaction scripts can be published as a web service.
• A user can schedule a script and data file on Winshuttle SERVER to run at a pre-specified time.
• Uses can choose to post data into SAP with a form using credentials of a pre-selected System post designer account.
• Disabled fields can be recorded using GUI scripting mode to enable download of these values.
• The loop layout in excel sheets has been improved in case of multiple loops. The loops at same level with different identifier columns do not need to follow row indentation in the excel sheet.
• During consumption of a DIRECT template based script, a user can select/de-select a range of fields.
• Upload time is available in seconds in the exported log to enable analysis of log data based on time to upload.
• After submitting a TRANSACTION script, the user is returned to the home screen.
• A Tcode field is added to the log viewer that provides information on transaction code/BAPI FM on which this transaction script is based.
• If a scheduled task did not run, an email is sent to the users in the notification group stating the cause of failure.
• Application instance closes automatically at the end of a scheduled run.
• Notes section is available for do-while/if constructs to add comments for the loop/if condition applied.
• Total time taken to run column is added to the log viewer.
• ‘No message returned from SAP’ is added to the log column for GUI scripting mode when the message returned from SAP is blank.

TRANSACTION

• User can choose to retrieve descriptions for read-only/disabled fields before recording a script.
• Read from SAP button is available for Cell based mapping TRANSACTION scripts as well.
• Parent MR80 view is provided in the DIRECT template consumption screen for a consolidated view of the classifications.
• A confirmation message is added for ‘Remove published files’ action from add-in to avoid any accidental deletion of published files.
• Undo-All button has been added to the mapper to undo all changes since last save.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Data is not correctly posted in case of a DIRECT template based script in case all the fields in a table have fixed value uploads.
• Tool tip in log viewer does not show full file path in case of linked file, with carry settings.
• Incorrect error message is displayed when user closes the excel application while it is running in addin.
• Incorrect status message is seen when Run is stopped before finishing in German Locale.
• Application crashes if no server is selected in the SAP logon pad and user clicks OK.
• Value for a ‘Read from SAP’ field is being written in the last line item row, even though the field is a header field.
• For Authorization Check, S_TABU_DIS authorization on tables is not checked.
• While running Linked files with carry settings using a secure license and second file run canceled at logon, next file auto runs when opened.
• Error Message occurs after validation when extended log column is ‘As text in column’ and no column name is specified.
• The records in Log Viewer are not sorted correctly if user sorts by any column other than’ Time’ column in descending order.
• Step by Step - Stop on errors is not working correctly for GUI scripting mode.
• User is displayed as disconnected from the server in the status bar, even while the data is being uploaded when the sustained logon timeout limit has timed out.
• 'If on SAP field' and 'Skip Screen' result in improper updates if there are more than one save code
• Validate option does not work for the linked script.
• Application selection bar shows wrong script name on stopping linked file run.
• Error comes when we click on the RUNNER Addin panel bar and no workbook is active.
• Toggle of already mapped fields to workbook to Read from SAP changes field mappings.
• Run Reason not updated in TRANSACTION logs when for a data file submitted from the RUNNER Add-in.

TRANSACTION

• Error occurs in the Mapper when user tries to save Transaction script with any field value = '@'
• Text of Log Column changes to Log Column/Cell in the mapper when user closes syntax error dialog
• An error is encountered when a user repeatedly clicks on the selected sheet in the change sheet option in the excel preview in Mapper
• Mapper: Performing Undo after saving changes in mapper, and clicking back button, doesn't prompt for saving transaction script and changes are saved.
• Application crashes on disabling the loop checkbox in properties panel for a looped field , and pressing Ctrl+z
• Same field in access gets mapped with multiple SAP fields in mapper without any warning

Added in Winshuttle TRANSACTION version 10.0

NEW FEATURES

TRANSACTION and RUNNER for TRANSACTION

• TRANSACTION supports BAPI and other RFMs by allowing the consumption of DIRECT templates created through the distiller application Winshuttle DIRECT.
• Index-based loops are provided for GUI scripting mode to allow appending data into grids and tables without the need of creation of a repeatable pattern.
• In GUI scripting mode, users can specify an if on index field condition to allow users to specify a row for updating other fields based on a key value.
• Users can now switch to cell-based mapping in the TRANSACTION mapper to support Microsoft Excel forms by enabling cell and range based mapping
• The Excel preview now supports more than 256 fields for mapping, and offers performance improvements when loading preview and a cleaner Mapper interface.
• The program can now be completely re-sized, and flickering while navigating between different screens has been reduced.
• GUI scripting is now independent of registry key settings for Windows for SAP GUI.
• When an ALF logon results in error during Run/Validate/F4, a logon dialog is shown to the user to provide credentials directly, after showing appropriate error message
• Changes to the activation process make the process easier.
• A tracing option has been added in the options area to help customers resolve of program issues faster.
• ALF supports AES-128 mode of encryption to provide more robust security.
• All syntax errors with a TRANSACTION script are shown to the user while exiting from the Mapper.
• The log viewer now gives details of scheduled runs that erred out and marks them for easy identification.
• A TRANSACTION script can be opened from the log viewer by double-clicking its corresponding log entry.
• Error handling has been improved for GUI scripting mode to return more descriptive and relevant messages in the log message column.

TRANSACTION

• Online templates are available as TRANSACTION scripts and Excel templates, together with online collateral to assist users with faster adoption of TRANSACTION.
• A1 dataloader scripts can be imported and used in TRANSACTION.
• Default mode of recording for CS01 is changed to Non Batch with Controls
• Bind sheet option is added to the publish process to allow users to lock embedded TRANSACTION scripts to a specific sheet.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Multibyte characters are not correctly uploaded in non-Unicode systems and are shown as ‘?’.
• Scheduler cannot send notification e-mails when case proxy authentication is required.
• If error is encountered during reading/accessing an ALF, an inappropriate message is shown to the users
• Running a script created with a transaction code not present in the current SAP system results in an incorrect error message
• Application does not close automatically after run on choosing Close application after run option if Back up SAP data is also checked, which requires the users intervention to save the file.
• When a French version of a TRANSACTION scripts is run and no records are returned from SAP, the log message appears in German instead in French.
• Working with ALF Management in Application Options creates multiple SAP sessions.
• Using an ALF that was created without a specified logon language, produces error messages in the log messages column when the script run even for successful updates.
• When a password contains a space character, Users receive a "username/password incorrect" error.
• Log column overwrites mapped columns data without issuing a warning in case this column is mapped to line item field or is an identifier column.
• It is not possible to add numbers [0.....9] without the keypad with the AZRTY keyboards
• Skip field indicator does not work for long text field.
• Users cannot use more than 256 fields in their scripts for upload or download.
• Users cannot see log messages, Error message, or Data downloaded messages if Excel spreadsheet is protected.
• Ctrl+Z for Undo does not work for Start and End Row.
• On some Windows 2000-based environments, an entry point error is observed every time users try to access update page.
• Clicking Cancel on non-existent date warning and then scheduling a run with correct specifications does not schedule and results in a Task already exists error.
• On French and German operating systems, an error occurs on specific rows filtered if script is run on Filtered rows.
• The title bar for dialog box to unlock TRANSACTION scripts is incorrectly labelled "Lock TRANSACTION script."
• On screen resolution of DPI 120 Metadata Properties controls are truncated.
• When the network connection has been disrupted, an exception occurs when clicking Save while exporting a log.
• Exception occurs on network failure in between the running of a file.
• Long text field and log field can be mapped to same Excel column value.
• SAP Tcode column appears in log viewer only when the SHUTTLElog.xml has no records.
• Error occurs when we submit a data file whose embedded TRANSACTION script is removed from the RUNNER add-in.

TRANSACTION

• An error occurs on applying IF on SAP condition on table fields using a field from the same table in a script created using GUI scripting mode of recording.
• Unable to remove the ELSE part of a construct by editing the IF-ELSE construct.
• Behavior of Undo differs with auto map after IF construct and auto map after applying Do-Loop.
• An error occurs on editing and clicking on the outer loop of a nested loop or IF construct.
• Notes saved for previously disabled fields, disappear on reloading the file, even though the fields remain enabled.
• If on SAP fields does not work when condition is on the same field on which IF construct is applied.

RUNNER for TRANSACTION

• Skip screen if not found property is enabled for editing.

Added in Winshuttle TRANSACTION version 10.2

NEW FEATURES

TRANSACTION and RUNNER for TRANSACTION

• TRANSACTION supports Office 2010 for both 32-bit and 64-bit versions. TRANSACTION has two versions 32-bit and 64-bit to enable support for 32 and 64-bit of Office 2010.
• TRANSACTION is now localized in Spanish and Dutch.
• "Validate by list" property of a field can be used to restrict set of possible values that this field can have.
• If the "Application trace" setting is ON, the user will get a warning message indicating that the setting can result in a slower run.
• TRANSACTION script will be automatically close after a scheduled run if the Advanced run option - Close application after run is selected.
• "Write headers" button is also available from client to allow users to create Excel templates to upload data.
• GUI scripting supports "Skip screen if not found" property.
• Excel data files can be sent as an email attachment at the end of a scheduled run (desktop scheduling). TRANSACTION scripts can be scheduled to run on console.
• The number of files in the Recent Files list can be configured from the Application options.
• Default "Skip field indicator" can be set from the Application Options.
• Log header information can be customized from the Header Log Details option.
• "Backup SAP data" option is enabled for Access data source as well.
• Advanced run option "Append timestamp to SAP log messages" appends time stamp to log messages returned in the data file.
• For Direct based TRANSACTION scripts, an additional column has been added in the mapper to specify Table/structure name.
• "Run not posted" setting has been enabled for Cell mapping of TRANSACTION scripts.
• Identifier based loops are supported in Direct based TRANSACTIONs scripts for cell mapping.
• Validation log column is available as a field in the mapper and can be set during script design time and also from the run screen.
• If "Skip screen if not found" property has been set for non-applicable cases e.g., inside a loop or multiple commit codes, a warning message is issued to the user.

Transaction

• Auto mapping is enabled for cell based mapping scripts.
• Writing headers for cell based mapping has been enabled to allow users to create Excel forms in an untitled preview.
• Publish dialog box shows the data file path currently selected and saved in the TRANSACTION script with an option to change.
• Validation error messages for the 'Validate' feature appear during design time in addition to Run.
• The detailed line recording values appear at correct row in the untitled preview, next to the line identifier rows.
• A parent category and classification view is provided in the Direct script consumption screen.
• Users can copy rows from a construct within the same script and to a different script as well.
• Notes can be added to the mapper fields and screens for Direct based scripts.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Users are not able to upload multiline text.
• Some UI strings are not localized in all supported languages.
• If an IF condition around a loop evaluates to FALSE for a row, all expected transactions after that are not processed irrespective of the result of the IF condition.
• Validating a protected sheet with extended logging turned on, results in an error.
• Some BAPIs result in an application termination with SAP GUI 720.
• If two BAPI-based TRANSACTION scripts are linked together, the second BAPI goes to an infinite loop in some cases.
• Linking a GUI scripting script with a TRANSACTION script of any other mode and validating, posts data into SAP instead of validating.
• If a cell is mapped with multiple SAP fields, the Excel file Validation goes for entire loop row range.
• Users are unable to schedule a run in TRANSACTION if Windows is installed in any other location except C drive.
• Space or tab in the header loop identifier results in inconsistent data upload.
• Error on running a published Cell based file with range based loop with End row = 0.
• For a cell based TRANSACTION script with no line items, validation error is written in incorrect log cell.
• Validation is always performed on the active sheet in the Add in irrespective of "Bind to Sheet" setting.
• Fixed errors are not highlighted with prefix or color for Direct based TRANSACTION scripts.
• The "Log Column/Log Field" row can be disabled by selecting the "Log Column/Log Field" row along with some other rows.
• Validating a data file with line items on erred out records results in inappropriate log messages.
• "Skip screen if not found" does not work with more than screen.
• Authorization check returns wrong values for function group authorizations for some users.
• The naming of log field for Access data source is inconsistent across different screens.
• Improper error message on running a TRANSACTION script in Excel using macros in the enterprise mode.
• Error for an XML form with no upload fields does not come before the dynamic form is launched.
• For a Direct-based script, the fixed value fields are shown as valid input fields in the dynamic form.
• Read from SAP fields are not shown on the dynamic form as "Read only" fields.
• Canceling an open TRANSACTION script from the add-in results in an inappropriate Validation message.
• Error on downloading a large number (>4000) of rows in the dynamic form.
• Product name in the log header of the Excel file is not consistent when the script is run from Client versus when script is run from the add-in.
• Step by Step run modes are disabled in Excel add-in for the Enterprise mode.

Transaction

• Direct-based TRANSACTION script accepts invalid cell name in the "if condition" dialog.
• Not able to put if condition checking if the log column is empty, around the complete recording when Access is the data source.
• "Skip transaction if empty"" is available for modification when it is not applicable, leading to user confusion.
• If the Spreadsheet setting is turned off, a wrong dragging icon appears in the preview section for batch mode TRANSACTION scripts.
• Connection to SAP is not closed on cancelling a recording from the Recording properties screen until the user exits the application session.
• Filter based transactions like ME51N, ME52N result in application error if Non Batch recording mode is used.
• Loops indicator line is not displaying properly if manual additions are done to the mapper screen.
• "Read from SAP not allowed on this row" message is not cleared from the status bar resulting in user confusion.
• Warning does not appear while re-mapping a column having its name in lower case in mapper
• Changing the data source of a TRANSACTION script having loops from Access to XML results in syntax error.
• Notes are not properly saved for screen fields.
• A "Fill in required fields" error occurs at the beginning of every recording if the SAP GUI size is changed from its default setting.
• UI issues are seen on "Open" and "if" icons on some locales.
• Cell mapping on the first row of the preview fails if the Spreadsheet gear option is turned off.
• A run time error occurs after recording a TRANSACTION script for Tcode VT01N.
• No way of changing loop type on switching from Cell based to Column based mapping.
• Attempting to import an empty Direct script in TRANSACTION results in an error.
• On switching data source from Excel to XML and back to Excel, If condition button gets disabled.

Runner for TRANSACTION

• If the Data file path contains a non-existent Access data file, it results in an incorrect error in the mapper screen.

Added in Winshuttle TRANSACTION version 10.1 Hotfix 2:

NEW FEATURES

TRANSACTION and RUNNER for TRANSACTION

• "Number of rows to remain empty before Run stops" setting in the Application options can now take a value up to 999

Added in Winshuttle TRANSACTION version 10.1

NEW FEATURES

TRANSACTION and RUNNER for TRANSACTION

• Users can validate data in an infopath/adobe/HTML form before uploading it to SAP.
• DIRECT based transaction scripts can be published as a web service.
• A user can schedule a script and data file on Winshuttle SERVER to run at a pre-specified time.
• Disabled fields can be recorded using GUI scripting mode to enable download of these values.
• The loop layout in excel sheets has been improved in case of multiple loops. The loops at same level with different identifier columns do not need to follow row indentation in the excel sheet.
• During consumption of a DIRECT template based script, a user can select/de-select a range of fields.
• Users can use auto-map for XML data source type to automatically map the recorded fields with mapping type ‘XML-SAP’.
• Upload time is available in seconds in the exported log to enable analysis of log data based on time to upload.
• After submitting a TRANSACTION script, the user is returned to the home screen.
• A Tcode field is added to the log viewer that provides information on transaction code/BAPI FM on which this transaction script is based.
• If a scheduled task did not run, an email is sent to the users in the notification group stating the cause of failure.
• Application instance closes automatically at the end of a scheduled run.
• Notes section is available for do-while/if constructs to add comments for the loop/if condition applied.
• Total time taken to run column is added to the log viewer.
• ‘No message returned from SAP’ is added to the log column for GUI scripting mode when the message returned from SAP is blank.

TRANSACTION

• User can choose to retrieve descriptions for read-only/disabled fields before recording a script.
• Read from SAP button is available for Cell based mapping TRANSACTION scripts as well.
• Parent MR80 view is provided in the DIRECT template consumption screen for a consolidated view of the classifications.
• A confirmation message is added for ‘Remove published files’ action from add-in to avoid any accidental deletion of published files.
• Undo-All button has been added to the mapper to undo all changes since last save.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Data is not correctly posted in case of a DIRECT template based script in case all the fields in a table have fixed value uploads.
• Tool tip in log viewer does not show full file path in case of linked file, with carry settings.
• Incorrect error message is displayed when user closes the excel application while it is running in addin.
• Incorrect status message is seen when Run is stopped before finishing in German Locale.
• Application crashes if no server is selected in the SAP logon pad and user clicks OK.
• Value for a ‘Read from SAP’ field is being written in the last line item row, even though the field is a header field.
• For Authorization Check, S_TABU_DIS authorization on tables is not checked.
• While running Linked files with carry settings using a secure license and second file run canceled at logon, next file auto runs when opened.
• Error Message occurs after validation when extended log column is ‘As text in column’ and no column name is specified.
• The records in Log Viewer are not sorted correctly if user sorts by any column other than’ Time’ column in descending order.
• Step by Step - Stop on errors is not working correctly for GUI scripting mode.
• User is displayed as disconnected from the server in the status bar, even while the data is being uploaded when the sustained logon timeout limit has timed out.
• 'If on SAP field' and 'Skip Screen' result in improper updates if there are more than one save code
• Validate option does not work for the linked script.
• Application selection bar shows wrong script name on stopping linked file run.
• Error comes when we click on the RUNNER Addin panel bar and no workbook is active.
• Toggle of already mapped fields to workbook to Read from SAP changes field mappings.
• Run Reason not updated in TRANSACTION logs when for a data file submitted from the RUNNER Add-in.

TRANSACTION

• Error occurs in the Mapper when user tries to save Transaction script with any field value = '@'
• Text of Log Column changes to Log Column/Cell in the mapper when user closes syntax error dialog
• An error is encountered when a user repeatedly clicks on the selected sheet in the change sheet option in the excel preview in Mapper
• Mapper: Performing Undo after saving changes in mapper, and clicking back button, doesn't prompt for saving transaction script and changes are saved.
• Application crashes on disabling the loop checkbox in properties panel for a looped field , and pressing Ctrl+z
• Same field in access gets mapped with multiple SAP fields in mapper without any warning

Added in Winshuttle TRANSACTION version 10.0

NEW FEATURES

TRANSACTION and RUNNER for TRANSACTION

• TRANSACTION supports BAPI and other RFMs by allowing the consumption of DIRECT templates created through the distiller application Winshuttle DIRECT.
• Index-based loops are provided for GUI scripting mode to allow appending data into grids and tables without the need of creation of a repeatable pattern.
• In GUI scripting mode, users can specify an if on index field condition to allow users to specify a row for updating other fields based on a key value.
• Users can now switch to cell-based mapping in the TRANSACTION mapper to support Microsoft Excel forms by enabling cell and range based mapping
• The Excel preview now supports more than 256 fields for mapping, and offers performance improvements when loading preview and a cleaner Mapper interface.
• The program can now be completely re-sized, and flickering while navigating between different screens has been reduced.
• GUI scripting is now independent of registry key settings for Windows for SAP GUI.
• When an ALF logon results in error during Run/Validate/F4, a logon dialog is shown to the user to provide credentials directly, after showing appropriate error message
• Changes to the activation process make the process easier.
• A tracing option has been added in the options area to help customers resolve of program issues faster.
• ALF supports AES-128 mode of encryption to provide more robust security.
• All syntax errors with a TRANSACTION script are shown to the user while exiting from the Mapper.
• The log viewer now gives details of scheduled runs that erred out and marks them for easy identification.
• A TRANSACTION script can be opened from the log viewer by double-clicking its corresponding log entry.
• Error handling has been improved for GUI scripting mode to return more descriptive and relevant messages in the log message column.

TRANSACTION

• Online templates are available as TRANSACTION scripts and Excel templates, together with online collateral to assist users with faster adoption of TRANSACTION.
• A1 dataloader scripts can be imported and used in TRANSACTION.
• Default mode of recording for CS01 is changed to Non Batch with Controls
• Bind sheet option is added to the publish process to allow users to lock embedded TRANSACTION scripts to a specific sheet.

BUGS FIXED

TRANSACTION and RUNNER for TRANSACTION

• Multibyte characters are not correctly uploaded in non-Unicode systems and are shown as ‘?’.
• Scheduler cannot send notification e-mails when case proxy authentication is required.
• If error is encountered during reading/accessing an ALF, an inappropriate message is shown to the users
• Running a script created with a transaction code not present in the current SAP system results in an incorrect error message
• Application does not close automatically after run on choosing Close application after run option if Back up SAP data is also checked, which requires the users intervention to save the file.
• When a French version of a TRANSACTION scripts is run and no records are returned from SAP, the log message appears in German instead in French.
• Working with ALF Management in Application Options creates multiple SAP sessions.
• Using an ALF that was created without a specified logon language, produces error messages in the log messages column when the script run even for successful updates.
• When a password contains a space character, Users receive a "username/password incorrect" error.
• Log column overwrites mapped columns data without issuing a warning in case this column is mapped to line item field or is an identifier column.
• It is not possible to add numbers [0.....9] without the keypad with the AZRTY keyboards
• Skip field indicator does not work for long text field.
• Users cannot use more than 256 fields in their scripts for upload or download.
• Users cannot see log messages, Error message, or Data downloaded messages if Excel spreadsheet is protected.
• Ctrl+Z for Undo does not work for Start and End Row.
• On some Windows 2000-based environments, an entry point error is observed every time users try to access update page.
• Clicking Cancel on non-existent date warning and then scheduling a run with correct specifications does not schedule and results in a Task already exists error.
• On French and German operating systems, an error occurs on specific rows filtered if script is run on Filtered rows.
• The title bar for dialog box to unlock TRANSACTION scripts is incorrectly labelled "Lock TRANSACTION script."
• On screen resolution of DPI 120 Metadata Properties controls are truncated.
• When the network connection has been disrupted, an exception occurs when clicking Save while exporting a log.
• Exception occurs on network failure in between the running of a file.
• Long text field and log field can be mapped to same Excel column value.
• SAP Tcode column appears in log viewer only when the SHUTTLElog.xml has no records.
• Error occurs when we submit a data file whose embedded TRANSACTION script is removed from the RUNNER add-in.

TRANSACTION

• An error occurs on applying IF on SAP condition on table fields using a field from the same table in a script created using GUI scripting mode of recording.
• Unable to remove the ELSE part of a construct by editing the IF-ELSE construct.
• Behavior of Undo differs with auto map after IF construct and auto map after applying Do-Loop.
• An error occurs on editing and clicking on the outer loop of a nested loop or IF construct.
• Notes saved for previously disabled fields, disappear on reloading the file, even though the fields remain enabled.
• If on SAP fields does not work when condition is on the same field on which IF construct is applied.

RUNNER for TRANSACTION

• Skip screen if not found property is enabled for editing.

Added in transactionSHUTTLE version 8.5 Hotfix 1:

BUGS FIXED

transactionSHUTTLE and runSHUTTLE

• Users are not able to use the F4 functionality in Excel if the Excel add-in is enabled.
• If the SAP logon password contains a space character, users are getting a username password incorrect error when trying to log on to SAP using transactionSHUTTLE or runSHUTTLE.

Added in transactionSHUTTLE version 8.5:

NEW FEATURES

transactionSHUTTLE and runSHUTTLE

• An authorization check button has been added in the tools menu to allow the users to check the status of SAP authorizations required for a user to work with transactionSHUTTLE.
• An option for Sustained Logon has been added to allow the users to use same logon between different runs of a SHUTTLEfile.
• Users are allowed to use internal e-mail servers to send scheduled run notification e-mails.
• Users are now allowed to use Extended Log with Validation.
• It is now possible to select multiple values for a cell range using SAP values in the add-in for Excel.

Added in transactionSHUTTLE version 8.2, Hotfix 2

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• If the users on certain Operating Systems (Language) try to evaluate the product by clicking on the Evaluate Button on the transactionSHUTTLE splash screen, an error message is displayed.
• Users face issue with SHUTTLEfiles recorded using certain localized versions of transactionSHUTTLE.

Added in transactionSHUTTLE version 8.2 Update 1:

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• When a user installs transactionSHUTTLE on a Microsoft Vista 64 Bit OS, the evaluation license key is not created correctly.
• An error occurs when GUI scripting is used and the character quotes (") are placed in the data file path.
• Errors are not shown in the Microsoft Excel template (by color/prefix).
• On certain versions of Microsoft Windows operating systems, the font size in the GUI of transactionSHUTTLE becomes too large to fit in the transactionSHUTTLE window.
• A linked script process created in v.7 does not work in the latest version.
• Tooltips are missing in certain areas of the application.
• In the Run screen, an error occurs when 0 is used in the End Row field along with Run on Errors.
• Before closing, transactionSHUTTLE does not prompt users to save changes made in the Advanced Run options or on the Run pane.
• When SHUTTLEfiles are linked with carry on settings, after running the linked script once if any of the linked scripts are opened then they start running automatically.
• Incorrect sorting in the Log Viewer
• When Microsoft Access is used as the template, the mouse pointer changes to "busy" in the Run screen.
• Strings in the French version of transactionSHUTTLE are incorrect.
• During the license deactivation process, an incorrect message appears even if the deactivation information does not reach Winshuttle Support.
• An issue occurs when MS Access is used as a template but the database does not contain any tables
• During License Deactivation, multiple browser windows open if an email client not installed
• An error occurs when uploading data with the Excel Add-in
• When the RUN option Run On Errors is used with the Extended log: as comment in log column option also checked, an error occurs
• Unable to use the Excel Add-in for SHUTTLEfiles with nested loops and Line items IDs other than default

Added in transactionSHUTTLE version 8.2, Hotfix 1

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• A Single Sign On issue occurs when a user switches between different SAP environments.
• Certain licensing scenarios are causing errors.
• The Delay commands used in the Editor are working incorrectly.
• In a Virsa Firefighter environment, there is an error occurring at the end of the recording step.
• transactionSHUTTLE
• An issue occurs when an IF condition to a block of lines in the mapper is saved and opened. The IF condition line values may change
• Keyboard shortcut to save a SHUTTLEfile using Ctrl+S does not work in the Editor
• In the Mapper screen, changing line item IDs of the inner loop affects the outer loop
• In the Mapper screen, end row less than start row is accepted in Do While loop properties
• Publishing a newly recorded SHUTTLEfile without any Mapping attached to the SHUTTLEfile causes an error
• Cut, Copy, Paste options are disabled in the Mapper for GUI scripting recorded SHUTTELFILES

NEW FEATURES

transactionSHUTTLE and runSHUTTLE

• Added Delay Between Transactions in Advanced Run options
• Required Field name changed to Skip transaction if empty in the Mapper screen
• Removed Keep Connection Alive" from advanced run options

Added in transactionSHUTTLE version 8.2:

NEW FEATURES

transactionSHUTTLE and runSHUTTLE

• Users evaluating transactionSHUTTLE will now be provided with a start-up tour consisting of a Quick Start Guide, Video Demonstrations and other resources which will help the user work with transactionSHUTTLE more easily.
• Without the need of saving a license key or file, users will now be allowed to evaluate the software automatically by clicking the Evaluate button on the transactionSHUTTLE splash screen. Please note that the evaluation version is valid for a limited time and has limited functionality (e.g. allowing only 25 records at one time).
• transactionSHUTTLE and runSHUTTLE are now localized in French Language in addition to English and German.

runSHUTTLE

• The runSHUTTLE users can now use Advanced Run options for specifying advanced run time settings like extended log, etc.

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• An error occurs when Back up SAP data is selected in the run time settings for the SHUTTLEfile that consists of fields that read from SAP.
• If a script has mapped fields that go beyond Column Z in Excel, the header data past column Z in not properly displayed.
• Tool tips for some of the buttons and grid columns are missing.
• If user tries to log-off during run, unexpected results are produced.
• The user has to click twice on a task row in the Job List of the scheduler to select that particular task.
• Back up SAP data worksheet in Excel is in the format DDMMYY.
• While setting a loop, if the user specifies start row equal to the end row, the loop is placed in an unexpected format.
• If the user specifies 0 in the start row, end row and the log result column on the run screen, he is given an inappropriate message.

Added in transactionSHUTTLE version 8.0, Service Pack 2 (SP2) Update 1

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• A bug in Back-up SAP data setting under Advanced Run Options. This setting is used for creating a back-up copy of the current SAP data fields using another Excel worksheet just prior to running the SHUTTLEfile.

Added in transactionSHUTTLE version 8.0, Service Pack 2 (SP2)

NEW FEATURES

transactionSHUTTLE & runSHUTTLE

• Users can now use an Excel Macro to load and run published SHUTTLEfiles through excel add-in.
• The excel add-in can now be used to run on selected rows on the active sheet for both contiguous and non-contiguous selections. The users can also run on row sets obtained after applying filters.
• The Back-up SAP data worksheet contains a backup copy of the current SAP data fields using another Excel worksheet just prior to running the SHUTTLEfile. The data is now in the same format as the upload MS Excel worksheet or MS Access table.
• A dialog box to identify the production servers is now provided to the user at the start of the application.
• All the published scripts are now loaded automatically into the Excel add-in. The users can now select a published script from the drop-down list and it’s details are automatically loaded in the excel add-in
• Step-by-Step mode has also been made available in the excel add-in in order to achieve better error management.
• The scheduler now allows the users to send the notification mails of the scheduled tasks to multiple users by specifying different e-mail addresses.
• The Log-viewer now provides additional information to the users – Data template file name, Date and Time in separate columns and SAP System client number.
• The application now allows the users to view and download the user manual from the help menu.

transactionSHUTTLE

• transactionSHUTTLE can now be used with sessions launched through Virsa Firefighter by using GUI Scripting as the recording mode.

runSHUTTLE

• runSHUTTLE users have now been provided with read-only access to the Mapper for viewing the mapping details for their SHUTTLEfiles.

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• If relative paths are given for a data file, the application is not able to locate/save the file at the desired path.
• When a user tries to save an ALF file to a network folder, it shows an error if more than three characters are used for the file name.
• Save dialog appears after a scheduled SHUTTLEfile run if ‘Close Application after Run’ is selected from the advanced run options.
• An error occurs if the scheduling of a SHUTTLEfile is cancelled by clicking cancel button on the Scheduler Wizard.

transactionSHUTTLE

• If relative paths are given for a data file, the application is not able to locate/save the file at the desired path.
• When a user tries to save an ALF file to a network folder, it shows an error if more than three characters are used for the file name.
• Save dialog appears after a scheduled SHUTTLEfile run if Close Application after Run is selected from the advanced run options.
• An error occurs if the scheduling of a SHUTTLEfile is cancelled by clicking cancel button on the Scheduler Wizard.

transactionSHUTTLE

• An error is encountered while using GUI Scripting Mode for recording IB52 transaction
• Default sheet name, as specified in Excel defaults, is not being used while saving the untitled.xls in preview.
• An error occurs when the user tries to modify the text in the Field Description or the Mapping type cell for loop or condition rows.
• When the user tries to put an If – Else condition with two rows, it doesn’t produce desired results
• It is not possible to modify the if condition properties once they have been set up.
• If GUI scripting mode has been used for recording a SHUTTLEfile, the extended log for the file is not properly displayed in the Excel data sheet.
• While using scripts, if condition operator {BETWEEN} doesn’t work properly in all scenarios.
• Screen Name and Screen Number cannot be seen in the properties panel of the Mapper
• While using Vista/Office 2003, an error occurs when update mapping is clicked and both the SHUTTLEfile and the preview are named "untitled."
• An error occurs if an attempt to cut and paste all the rows in the Mapper is made.
• When Create Mapping is clicked for a SHUTTLEfile which has been locked in the process of recording, a prompt to unlock the file is encountered.

Added in transactionSHUTTLE version 8.0, Service Pack 1 (SP1) Update 4:

NEW FEATURES

transactionSHUTTLE & runSHUTTLE

• A message dialog box is provided to the user if the Run not posted option has been checked and there is information already stored in the log column of the data sheet
• New features and bug fixes information in Patch and Service Pack releases will be listed on Winshuttle’s website when the user uses the auto-update feature.
• In MS Excel worksheets used in tandem with SHUTTLEfiles which contains the looping feature, the # symbol can be used in the indicator column to indicate that the row should not be used and is only for information purposes.
• The application now shows the name of the loaded ALF file in the upper portion on the ALF maintenance screen.
• supportSHUTTLE is a new feature designed to provide the Support and R&D teams with key customer information which will help in resolving the customer’s query/issue.

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• If the windows display theme is changed on the workstation, the application’s User Interface is not shown correctly
• An error may occur during the installation when the .NET framework is not installed on the workstation or incorrectly installed through the application installation
• An error occurs when saving a blank Excel template in the Mapper screen
• An error occurs when an invalid number is entered in the End Row field on the Run screen
• Default SAP logon language is not used during recording if on the logon pad the language field is left empty
• A SHUTTLEfile after execution gives the error message TimeSpan overflowed because the duration is too long. This in turn does not produce any log results.
• When switching to the German version of the application, the F1 help file is still in English
• When the application is started on a German OS workstation, the application starts up in the default language English and not German.
• When a SHUTTLEfile is created and mapped, on the Run screen the last blank MS Excel column name is picked instead of the default value that is set in the options screen
• Certain formats of data stored in the MS Excel sheet are not read correctly by the application
• In the ALF management screen, the Test logon button provided inconsistent results if the Logon Group option is previously used

transactionSHUTTLE

• Commands inserted in the Editor are not being saved correctly on exiting the Editor window.
• When putting a loop inside of another loop, no matter what the user enters in the Detail ID field, transactionSHUTTLE adds a 1. If the user uses D1, transactionSHUTTLE makes it D11 after the SHUTTLEfile is saved.
• In the Mapper screen after a new recording, when MS Access is used as the source type and a new column is added to the existing table, upon clicking on the save button to select an existing database an error occurs.
• An error is seen when clicking on Automap in the Mapper when the preview is being generated
• The Extended Log option in the Advanced Run Options is not saved correctly in the SHUTTLEfile

Added in transactionSHUTTLE version 8.0, Service Pack 1 (SP1) Update 3:

NEW FEATURES

transactionSHUTTLE & runSHUTTLE

• Users can now view the EULA - End User License Agreement (HELP->ABOUT)
• When creating an ALF (Autologon file), special characters can now be used in the password area (Tools->Options->ALF Management)

transactionSHUTTLE

• In the Record-Map-Run screen, the create recording from template functionality is now complete. Within the Mapper the user can also now save the SHUTTLEfile as a template SHUTTLEfile

BUGS FIXED

transactionSHUTTLE & runSHUTTLE

• In the log viewer, the time values shown for SHUTTLEfiles created with version TxShuttle 7.x are incorrect
• MS Access data templates used in uploads do not close after the upload has taken place
• When the application is minimized, the tool tip for the icon in the system tray shows incorrect information
• The ‘Launch GUI’ selection is retained for a SHUTTLEfile recorded in ‘Batch Input’ mode if the previous SHUTTLEfile use was recorded in ‘Non Batch Input’ mode
• Through the ‘Log Viewer’ (Tools->Log Viewer) if the ‘Export’ option is chosen and the export started, clicking on any of the icons in the ribbon menu causes the process to stop
• Incorrect ‘error’ messages are shown in the TOOLS->OPTIONS area

transactionSHUTTLE

• GUI Scripting recording mode is giving an error with the SAP system ECC 6.0 when using the transaction code MM02
• If MS Access is used for the data template, rows in the Mapper designated as Read from SAP fields do not work correctly if they are placed in a Loop
• In the Mapper the mapping of the fields is changed if in the Expert view, the Loop option is selected but then closed on pressing the Cancel button
• An error occurs in the application when the source of the data template is changed (MS Excel to MS Access) and a Loop statement is already present in the mapping. Double clicking on the Loop causes the error
• During an upload the changes in the Advanced Run Options for saving the MS Excel file during the upload are not taking effect immediately
• In the Advanced Run Options screen, the Close Excel after Run and Link SHUTTLEfiles options when used together do not close MS Excel after the upload is complete
• When MS Access is used as the source for the data template, if a Loop is used the Header and Line Items tables can be indicated to be the same

Added in transactionSHUTTLE version 8.0, Service Pack 1 (SP1) Update 2:

Bugs Fixed

• In certain instances, Read Only SAP fields which are marked as Read from SAP rows in the Mapper become Fixed Value rows in the Mapper
• An error occurs with MS Access data templates when an IF statement is placed around SAP fields marked as Read from SAP fields in the Mapper
• An error occurs on German OS workstations if Office 2000 is used with transactionSHUTTLE
• runSHUTTLE’s version number does not appear if transactionSHUTTLE is not installed on the workstation
• Upon stopping an upload, the SHUTTLE file halts but the Stop button does not change to the Start button.
• FTE in the Log Viewer (Tools->Log Viewer) is being calculated incorrectly
• SAP 4.6(x) customers running SHUTTLEfiles with previous versions of transactionSHUTTLE with Read from SAP mapped fields are experiencing syntax error messages
• Accented characters are not appearing correctly in Mapper field descriptions, preview and Excel preview filename
• On scheduling a task with the option "run only if logged in" unchecked, the user has to manually close the transactionSHUTTLE instance in the task manager after the upload is complete
• In the Mapper, if an existing MS Excel file is chosen as the data file, in the preview section a new sheet is created instead of displaying the existing sheet names
• Exporting Log Viewer information does not show the data in the format seen in the application’s Log Viewer
• The Blank and Not Blank operators for IF conditions in the Mapper do not function properly
• In the Scheduler (Tools->Scheduler), using the cursor to hover over the scheduled task SHUTTLEfile name does not show the Drive name correctly in the tooltip
• A few strings are not translated into German for the German localization of the application

Added in transactionSHUTTLE version 8.0, Service Pack 1 (SP1):

Bugs Fixed

• When MS Access is used as the Data Source Type in the Mapper, constructing a loop around a line item screen causes the Run to only upload one record correctly
• When MS Access is used as the Data Source Type in the Mapper, constructing a loop around a line item screen and using a non-text field as the join between the Header and Line Item tables causes a problem
• Changing default path locations for data source files, SHUTTLEfiles, Log files and ALF files are not saved correctly (Tools ->Options->Application Defaults->Path Defaults)
• In the Mapper screen, disabled conditions (If/Endif statements) and disabled Loop statements (Do-While) become enabled when re-entering the Mapper

Added in transactionSHUTTLE version 8.0, Service Pack 1 (SP1):

New Features

• Chained or linked SHUTTLEfiles can now be used with transactionSHUTTLE’s Excel add-in feature
• Close Excel file option added in the Advance Run Options

Bugs Fixed

• Unable to place If condition statement over entire recording
• Deleting an If condition statement located within another If statement causes misalignment of icons
• 24 hour Clock users can not schedule pm runs
• Multiple instances of transactionSHUTTLE can not be launched at the same time
• German message related to table entries appearing for SAP standard message No message returned from SAP
• transactionSHUTTLE causes an error on startup when the users Network drive (shown in the default paths – Application->Options) is not connected
• Issues with the Do-While loop when using MS Access as the data template
• On selecting German from the language dropdown option, the About screen under help changes to German and then both English and German are checked in the language dropdown area
• The Advanced Run Option Backup SAP data brings back incomplete data into the source sheet
• Transactions with special characters can not be recorded correctly as these special characters are used within the file name creation
• Installation of transactionSHUTTLE gives an error when .NET framework is not installed correctly
• transactionSHUTTLE Admin Module error message sometimes appears during the recording step
• After completing the recording step, an error appears if MS Access source type is selected and a column added after a table is deleted
• The keyboard shortcuts for Cut, Copy & Paste do not work in the Mapper
• ALF file causing errors
• Print Preview shows a blank screen if the Log Viewer or the Scheduler is selected from within Mapper

Added in transactionSHUTTLE version 8.0, Patch 3:

New Features

• Version and release information details are mentioned on the flash screen

Bugs Fixed

• The word warning is missing under Options->Prod. Svr. Warning->"Enable Production Server"
• On running an upload with the Backup SAP data feature selected, incorrect data is copied from the source sheet
• The same Reason for Run is being used for the next upload
• Transaction codes which use a \ (slash) are causing a syntax error before the user gets a chance to change the file name
• When inserting an IF statement within another IF statement, the images get unaligned
• Options: Trim data not working correctly
• Mapper Do while loop properties - the start row and end row options are not available to edit
• Mapper is not opened if the authorization object S_TABU_DIS is missing
• Transaction Codes ending with N which are recorded in non-batch with controls do not run immediately after saving the SHUTTLEfile.

Added in transactionSHUTTLE version 8.0, Patch 2:

Bugs Fixed

• An error occurs when using Office 2000 with TransactionSHUTTLE
• The Dropdown box for operators when using the IF statement is too small
• On applying a Do while loop in an existing SHUTTLEfile, an extra field is added in the preview section when clicking on the OK, Cancel or the Red Cross button in Do while dialog box
• Editor command #XS and +MT not working
• Scheduled Runs are not working when the user has logged off from windows
• Format of minutes is not correct in the exported log file
• Run is paused when Excel file is in editing mode

Added in transactionSHUTTLE version 8.0, Patch 1:

New Features

• Added Stop button to stop an upload through the Excel add-in.

Bugs Fixed

• ROI details are not generated correctly in the Log Viewer
• Error when running a scheduled task with "close application after run" option is selected

Added in transactionSHUTTLE version 8.0:

• New Graphic User Interface (GUI)
• Embedding SHUTTLEfile(s) in Microsoft Excel
• GUI scripting option for recording
• Automatic mapping (Automatically map SAP data fields to a Microsoft Excel worksheet or Microsoft Access table)
• Enhanced Mapper with Basic and Expert modes
• Microsoft Access preview section in Mapper
• Improved looping and conditional run functionality
• Enhanced log viewer with ROI information (Return on Investment)
• Integrated Scheduler with e-mail notification
• Application language localization (localization applied in German, in addition to English as default)

• Trademarks
• Winshuttle.com
• Back to top
        
• 
• 
• 
•