Skip to main content

Create Process Files in Process Runner DB

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

Transaction

This topic describes how to record an SAP transaction flow using Process Runner DB. 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 Transaction Code, enter the transaction code.
  3. To force Process Runner DB 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 DB 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 DB to continue the transaction even when it encounters COMMIT statement. Some of the transactions must be run in non-batch input mode.
      • Background Mode: Runs the transaction in background simulation for successful run.

      • Get Fields from SAP Mode: This controls if Process Runner DB should get the fields from SAP or not and if so, what type of method should it use.

      • File Name (optional): Adds the file name for the Process file before recording. If this field is left empty, then Process Runner DB automatically generates a name for the Process 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 DB displays a warning message and continue with generating file.
      • Get Field descriptions from SAP(recommended): Allows Process Runner DB 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.
        • Skip deactivated fields: Instructs Process Runner DB to skip the fields which are deactivated from the application.
        • Skip output (read) only fields: Instructs Process Runner DB to skip the output fields which are read-only ones..
      • Auto map visible input fields: Allows to automatically map all the visible input fields..
      • Enable and auto map all output (read) only fields: Automatically maps all output only - read from SAP fields.
      • Defaults: Restores the default settings.
    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 Record and Run Transaction File in Process Runner DB.

BAPI/RFM

This topic describes how to create a BAPI/RFM template using Process Runner DB. 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 BAPI/RFM Name, enter the BAPI/RFM name.

  3. 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 DB automatically generates a name for the Process 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: Maps standard BAPI return fields to Database table starting from the table ID mentioned. Process Runner DB can automatically detect standard return fields and map them as SAP to DS downloads.
      • Get BAPI/RFM documentation from SAP: Retrieves and saves the SAP standard documentation for the selected function module in your logon language.
      • Get fields description: Retrieves the field descriptions from SAP in your logon language.
    4. Select OK. The changes to the options on the Advanced Record Options tab are saved.
  4. Select OK. The Connector for SAP window appears. For information about how to record different types of BAPI/RFM transactions, see Record and Run BAPI File in Process Runner DB.

SAP maintains documentation of each BAPI/RFM which can be downloaded and viewed by the user. Enter the RFM/BAPI name at the field and select the doc icon to retrieve the SAP documentation of corresponding RFM/BAPI as shown in the image below.

GUI Scripting

This topic describes how to record a GUI Scripting SAP transaction flow using Process Runner DB. 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 Transaction Code, enter the transaction code.
  3. To refresh the list of current active GUI Scripting enabled SAP sessions, select 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 DB automatically generates a name for the Process 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 DB must use.
      • Context Menu: Tells Process Runner DB 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 Record and Run GUI Scripting File in Process Runner DB.

    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.

Important: If GUI Scripting is enabled and you still cannot use GUI Scripting with Process Runner DB, 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 DB. The file is saved as an .ide file (Innowera Data Extractor File).

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

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 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 appear.

    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 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 DB automatically generates a name for the Process 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 Database tables.
      • Get fields description: Retrieves the field descriptions from SAP in your logon language.
    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 Record and Run Data Extractor File in Process Runner DB.

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.