Error management and trace files

New features in TRANSACTION version 10.6/10.7 > Setting up for use > Error management and trace files

Back to

Error management and trace files

Use Error Management to determine how TRANSACTION processes errors that occur when a script file is run.

On the Main menu, click Tools, and then click Options . In the list, click Error Management.

When an attempted upload produces errors, the rows with errors are not uploaded to SAP and the related error messages from SAP are returned to the log field or column that was specified.

Default indicators for errors in messages

You can use these settings to set a background cell color or prefixed text to flag Excel log column cells that contain error messages. After you correct the data, you can go to the Run screen and select the Run on Errors option to rerun the script file for only those rows marked as erred. When the erred rows run successfully, they are marked as fixed.

Background color of cell for errors: Click this setting to select a background color for the errors listed in the log column specified in the Log Result Column field on the Run screen. The default color used is red. If you select this setting, the Prefix text for log column is left blank.

Background color of cell for fixed errors: Click this setting to select a background color for the errors that are fixed. The default color used for fixed errors is green.

Use Prefix text for errors in the Log column: Click this setting to mark errors by adding a prefix to the error messages stored in the Excel, Access, and Google Log columns or fields. The default prefix text is "Err:". If you select this setting, no background color is used in the cells.

Use Prefix text for fixed errors in the Log column: Click this setting to mark errors by adding a prefix to the fixed error messages stored in the Excel, Access, and Google Log column or fields. The default prefix text is "Fix:". If you select this setting, no background color is used in the cells.

Warning Error Text: Check this option and provide the warning text to appear in a separate column in case SAP returns an error in the log column.

Trace

RFC trace

The RFC trace tool is used by support to help to find the root cause of problems you might experience with the application. When this option is enabled, it traces the remote function calls for all the actions you have taken in the software and writes them to a file at the log folder location set in the application options with a default value: C:\Documents and Settings\<user name>\My Documents\Winshuttle\TRANSACTION\Log.

SAP trace

The SAP trace tool is used by support to help to find the root cause of problems you might experience with the application. When this option is enabled, it traces the SAP calls through the Winshuttle function module for TRANSACTION for all the actions you have taken in the software and writes them to a file at the log folder location set in the application options with a default value: C:\Documents and Settings\<user name>\My Documents\Winshuttle\TRANSACTION\Log.

Enabling SAP trace may slow the script recording process. A message appears before recording starts to remind you of this.

With either trace method, if you experience a software problem, check the trace option and repeat the actions that resulted an in error. A text file is created in the default log folder that you can send to the support team for review.

When you are finished, clear the option. It is important to turn off Trace after you have finished tracing the problem so that you do not fill your file with information that is irrelevant to the next trace.

Also in this section

Production Server Warning (Prod. Svr. Warning)

Client connection settings

Header log details

Restore defaults

GUI scripting and Windows scripting

Enable GUI scripting

Unicode implementation for TRANSACTION scripts