Skip to main content

Create Process Files

This section explains how to create a Process file for the following technologies:

Note: Creation of a process file is not supported with a non-SAPGUI system.

Transaction

This topic describes how to record an SAP transaction flow using Process Runner. The file is saved as an .itf file (Innowera Transaction module File).

To create a Transaction Process file,

  1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.

  2. In the Transaction Code box, enter the transaction code.
  3. To force Process Runner to run the transaction in batch input mode and to stop the transaction when it encounters COMMIT statement, select Run in batch input mode and Stop on COMMIT. When you do not select this option, the transaction runs in non-batch input mode (as you would run normally in SAP GUI) and forces Process Runner to continue the transaction even when it encounters COMMIT statement. Some of the transactions must be run in non-batch input mode.
  4. Optionally, select More... for additional recording options. The Options window appears.

    1. On the Basic Record Options tab, enter the following details:
      • Run in batch input mode and Stop on COMMIT: Allows transaction to run in non-batch input mode (as you would run normally in SAP GUI) and force Process Runner to continue the transaction even when it encounters COMMIT statement. Some of the transactions must be run in non-batch input mode.
      • Record Controls (Static recording only): Allows Process Runner to record the SAP control framework objects, such as ALV grid or tree view, in static mode. You can run the transaction with such control but the input to these controls cannot be changed at runtime. Do not map and change any value that is sent to the control object as it is not effective and your recording might not work. Mapping to values outside of the control object should work as usual and you should perform mapping as required. We recommend that you use this option only when required or suggested by an expert or insightsoftware support engineer.
      • Background Mode: Runs the transaction in background simulation for successful run.
      • File Name (optional): Adds the file name for the Process file before recording. If this field is left empty, then Process Runner automatically generates a name for the Process file.
      • Excel Data file (optional): Indicates that an external Excel file that has data must be uploaded or downloaded to or from SAP. Provide the correct worksheet name of the selected Excel file.
    2. Select OK. The changes to the options on the Basic Record Options tab are saved.
    3. On the Advanced Record Options tab, enter the following details:

      • Get Screen descriptions from SAP: Retrieves the readable screen descriptions from SAP for all the screens were passed during recording. This requires special authorization in SAP; if users do not have required permission, then Process Runner displays a warning message and continue with generating file.
      • Get Field descriptions from SAP(recommended): Allows Process Runner to get descriptive and more readable field information from SAP. If you select this checkbox, the recording might take a little longer, even though there is no impacts on how the transaction runs.
      • For all Active Fields: Instructs Process Runner to automatically generate F4 Help for all the active fields.
      • For all Inactive Fields: Instructs Process Runner to automatically generate F4 Help for all the inactive fields.
      • Automatically map fields that I enter or change: Allows to automatically map input fields.
      • Automatically download all output (display only) fields: Allows to automatically map the output fields. This option automatically enables and assigns Excel column IDs for the output fields found in the recording.
      • Automatically backup fields that I enter or change to another column: Automatically downloads all the input fields; you can keep a record of what the values were before the upload.
      • Automap all check mark ("X") to Excel: Allows the recorded checkboxes to be automatically mapped to the Excel columns after the recording is completed.
    4. Select OK. The changes to the options on the Advanced Record Options tab are saved.
  5. Select Start Recording. The Connector for SAP window appears. For information about how to record different types of transactions, see the tutorials in the Record and Run Transaction File section.

BAPI/RFM

This topic describes how to create a BAPI/RFM template using Process Runner. The file is saved as an .iff file (Innowera Function module File).

To create a BAPI/RFM Process file,

  1. Select File > New Process > New RFM/BAPI or select BAPI/RFM (BA) available on the left side of the New Process window.
  2. In the BAPI/RFM Name box, enter the BAPI/RFM name.
  3. To retrieve the SAP documentation of the BAPI/RFM, select the pop-up icon. A pop-up window appears with the documentation about the BAPI/RFM that you can download and view.

  4. Optionally, select More... for additional recording options. The Options window appears.

    1. On the Basic Record Options tab, enter the following details:
      • File Name (optional): Adds the file name for the Process file before recording. If this field is left empty, then Process Runner automatically generates a name for the Process file.
      • Excel Data file (optional): Indicates that an external Excel file that has data must be uploaded or downloaded to or from SAP. Provide the correct worksheet name of the selected Excel file.
    2. Select OK. The changes to the options on the Basic Record Options tab are saved.
    3. On the Advanced Record Options tab, enter the following details:

      • Automap return fields: Maps the standard BAPI return fields to Excel columns automatically beginning from the specified column ID. Process Runner can automatically detect standard return fields and map them as SAP to Excel downloads.
      • Get BAPI/RFM documentation from SAP: Retrieves and saves the SAP standard documentation for the selected function module in your logon language.
      • Get Descriptions: Retrieves the field descriptions from SAP in your logon language.
      • Get F4 Help Configuration: Allows Process Runner to automatically generate F4 Help for all the fields.
    4. Select OK. The changes to the options on the Advanced Record Options tab are saved.
  5. Select OK. The Connector for SAP window appears. For information about how to record different types of BAP/RFM transactions, see the tutorials in the Record and Run BAPI File in Process Runner DB section.

GUI Scripting

This topic describes how to record a GUI Scripting SAP transaction flow using Process Runner. The file is saved as an .isf file (Innowera Script File).

To create a GUI Scripting Process file,

  1. Select File > New Process > New GUI Script or GUI Script (GS) available on the left side of the New Process window.
  2. In the Transaction Code box, enter the transaction code.
  3. To refresh the list of current active GUI Scripting enabled SAP sessions, click Refresh/Get GUI Session.
  4. Optionally perform the following steps:
    • To get notified if a script is attached to a running GUI, select Warn On Attach.
    • To get notified if a script opens a connection, select Warn On Connection.
    • To close the current active running GUI Session after the recording operation is concluded, select Also close GUI Session.
  5. Optionally, select More... for additional recording options. The Options window appears.
    1. On the Basic Record Options tab, enter the following details:

      • File Name (optional): Adds the file name for the Process file before recording. If this field is left empty, then Process Runner automatically generates a name for the Process file.
      • Excel Data file (optional): Indicates that an external Excel file that has data must be uploaded or downloaded to or from SAP. Provide the correct worksheet name of the selected Excel file.
    2. Select OK. The changes to the options on the Basic Record Options tab are saved.
    3. On the Advanced Record Options tab, enter the following details:

      • Script Language: Indicates the script language that Process Runner must use.
      • Context Menu: Tells Process Runner how the mouse right-clicks must be recorded.
      • Automap: Performs mapping automatically based on the recording performed and eliminates the need for manual mapping activity. You can change the mapping from the Mapper tab.
    4. Select OK. The changes to the options on the Advanced Record Options tab are saved.
  6. Select Start Recording. The Connector for SAP window appears. For information about how to record different types of GUI Scripting transactions, see the tutorials in the Record and Run GUI Scripting File section.

    Note: The GUI Session is displayed and a 'barbershop pole' icon is displayed in the lower half of the SAP GUI to let the you know that GUI Scripting is active.

If GUI Scripting is enabled and you still cannot use GUI Scripting with Process Runner, it is possible that your SAP GUI installation did not install SAP GUI Scripting interface. Go to Control Panel, Add or Remove Program options and find SAP GUI front end. Select Change and ensure that SAP GUI Scripting is selected. If not, select and install that component.

Data Extractor

This topic describes how to create a Data Extractor Process file using Process Runner. The file is saved as an .ide file (Innowera Data Extractor File).

You can extract existing table data from SAP into an Excel File. Use the custom Data Filter conditions for data extraction to get the relevant data.

Refer to the video to understand how to create a Data Extraction automation script.

To create a Data Extractor Process file,

  1. Select File > New Process > New Data Extractor or Data Extractor available on the left side of the New Process window.
  2. In the Table/View Name, enter the SAP table or view name.
  3. If you do not know table name or if you want to find out table joins, select DD Explorer. A list of all tables and views as found in standard ECC6 system is displayed.

    The following screenshot illustrates the steps to find a table joins between VBAK and VBAP. Refer to the video to understand how to use the SAP Data Dictionary Explorer functionality.

  4. Optionally, select More... for additional recording options. The Options window is displayed.
    1. On the Basic Record Options tab, enter the following details:

      • File Name (optional): Adds the file name for the Process file before recording. If this field is left empty, then Process Runner automatically generates a name for the Process file.
      • Excel Data file (optional): Indicates that an external Excel file that has data must be uploaded or downloaded to or from SAP. Provide the correct worksheet name of the selected Excel file.
    2. Select OK. The changes to the options on the Basic Record Options tab are saved.
    3. On the Advanced Record Options tab, enter the following details:

      • Automap all fields: Maps automatically the return fields to Excel columns.
      • Get fields description: Retrieves the field descriptions from SAP in your logon language.

        Screenshot: Advanced recording options

    4. Select OK. The changes to the options on the Advanced Record Options tab are saved.
  5. Select OK. The Connector for SAP window appears. For information about how to record different types of Data Extractor transactions, see the tutorials in the Record and Run Data Extractor File section.

Note: You can also use custom Z or Y tables and table joins that are not displayed in the SAP Data Dictionary Explorer window; you can directly enter the Z or Y table name in the New Process window.

Note: The list is based on ECC6. If you are using a different system, the selected table or view may not be available in your system; however, you can directly enter the table or view name in the New Process window. Process Runner dynamically validates this table or view after you log on to the SAP system.

Note: While SE16 or SE17 access may not be required, you must have a table-level authorization to use any table or view. If you do not have the required access, an authorization error is displayed.

Was this article helpful?

We're sorry to hear that.