During the installation of RUNNER, the RUNNER add-in for Excel is installed automatically on your computer as an add-in in Excel.
NOTE: When you run an embedded TRANSACTION script, the data is uploaded from the active Excel sheet or from the sheet to which the script is bound, and not any other sheet specified in the embedded TRANSACTION script or any other TRANSACTION scripts linked to it.
The add-in allows you to run only data files. With the add-in, you can run multiple scripts that are attached to the data file and the carry settings are respected. The scripts run on the active sheet of the active data file. However, only the initial script will appear in the Runner window and does not update when each subsequent script in the script chain runs.
To view the RUNNER add-in pane
The bind script functionality has the following behaviors:
Select TRANSACTION script: Available only if no published file exists in the Excel file. Click Browse and select the TRANSACTION script to open. You cannot type in the file path. See Loading an Existing Recording.
Select Published TRANSACTION script: If at least one published file exists in the Excel file, the list of the published TRANSACTION scripts appears. Select a file and its details appear automatically.
As specified below: Runs the rows as specified by the run settings below.
On Selected Run: Runs on rows that are currently selected in the active sheet. You can select multiple ranges of rows. Rows can be contiguous and non-contiguous selections.
On Filtered Run: Runs on rows that are obtained after applying filter on columns. This feature takes the data from the filtered rows only and not from the whole active sheet.
Start row and End row: Type the start row and end row. This is a run time setting and is not saved in the Excel sheet or in the published TRANSACTION script.
No. of rows: Displays the number of rows selected according to the start row and end row values you enter. This is a run time setting and is not saved in the Excel sheet or in the published TRANSACTION script.
Log Column: Type the Excel column where error messages are returned. The default is E. For more information, see Error Management.
Run Reason: Type a reason for the run. This is a run time setting and is not saved in the Excel sheet or in the published TRANSACTION script.
Run Now: Use this option to execute the TRANSACTION script manually.
Run Later (Scheduling a Run): Use this setting to schedule an automated upload into SAP. For more information, see Scheduling a Run.
Run on Errors: Select this setting to re-run the TRANSACTION script for those rows of data (records) marked as errors only. After you correct any errors identified on the initial run, you can use Run on Errors to run the TRANSACTION script for the marked records only. When the TRANSACTION script is run initially, the errors are marked using the background color or a text indicator (default text is "Err:") for the Log column cells that contain messages returned from SAP. For more information, see Error Management.
Run Step-by-Step (Stop on All Screens): Select this option to execute the transaction by launching SAP GUI. When you select this option and click Run, a confirmation message is displayed. This troubleshooting selection stops at every screen in the TRANSACTION script. A dialog box containing the OK code and the Enter button appears on each screen. You click Enter in the dialog box to move from screen to screen. In this mode, you can view all of the values being uploaded and pinpoint the exact location and reason for the error you are encountering.
Run Step-by-Step (Stop on Errors only): Select this setting to execute the transaction by launching SAP GUI. When you select this option and click Run, this troubleshooting mode stops at the point where the error is occurring in order to allow you to view what is occurring and to take corrective action to fix the problem.
Run Step-by-Step on Errors: Select this setting to run on the rows that returned an error and stop on the screen where the error occurs
Key considerations for using the Step-By-Step Run Options: You need appropriate authorization to run these troubleshooting modes. Most people do not have authorization to run the step-by-step modes in a production environment. If you do not have the proper authorization, you can simulate the transaction manually by using data from the Excel sheet to determine why and where the error is occurring. RUNNER allows you to troubleshoot all rows or just one row. If you want to troubleshoot only one row, insert the row value in the Start Row field and select troubleshooting mode that you want.
You can validate data to ensure that there are no errors before you upload it.
To validate a data file
Correct any errors or make changes, and then click Run to upload the data.
Run Now: Use this option to execute the TRANSACTION script manually. If you are logged onto a system when you click Run or Validate, you’ll be logged off from the currently system and are required to log on again to a system to run the file.
Stop the run.
If no TRANSACTION scripts are published, you can open a .TxR file, and then click Write Headers write the header information for the mapped columns from the TRANSACTION script currently loaded in the add-in.
Select a cell, and then click SAP Values. F4 help, similar to one used in SAP, appears. In the SAP Values dialog box, use the check boxes to select multiple values. If the cell column is not mapped to any field or if no F4 help is available for the field, a message appears to tell you that no help or mapping is available.
If you are not already logged on to an SAP system, you are asked to log on to a system for which you want the F4 help. For subsequent F4 searches, you do not need to log on.
This bar provides the logon information. It can also be used to log off from the currently logged in system.
Also in this section