Debug Run

This section describes how to use the Debug-All Screens to view the location of errors in a Transaction or GUI Scripting Process file in a step-by-step manner. You can perform a debug run from the Home, Edit, or Mapper tabs.

Note: The Debug-All Screens option is applicable only for Transaction and GUI Scripting technologies.

To use the debug run option

  1. Open a Transaction or a GUI Scripting Process file.
  2. Select Debug-All Screens in the Run Actions section on the Home tab. The Debug Options window is displayed.
  3. For a Transaction Process file, perform the following steps:
    1. In the Debug Options window, enter the required details and select OK. The Magnitude Connector for SAP window is displayed.
      MAT-DF-S&PLT (5)
    2. Select the SAP system, select Logon, enter the information for Client, User, Password, and Language, and select OK. The debug run of the Transaction Process file is started.
  4. For a GUI Scripting Process file, perform the following steps:
    1. In the Select GUI session where you want to run this process window, select the following options:
      • Warn on Attach: Notifies when a script is attached to a running GUI.
      • Warn on Connection: Notifies when the script opens a connection.
      • Start debug row: Sets the first Excel row where Process Runner initiates the run on the external Excel file.
      • End debug row: Sets the first Excel row where Process Runner stops the run on the external Excel file.
      • Use external debugger: Indicates that an external script debugger like Microsoft Script Debugger is required. This option runs only one row or one looping row.
    2. If you select Start and use new SAP GUI Session, you are prompted to the sign in to the SAP system in the Magnitude Connector for SAP window.
    3. If you select an existing GUI Session, the debug run of the GUI Scripting Process file starts immediately in the selected SAP GUI session.