Home Tab

•Use Internal Excel Book (iBook): Use internal iBook provided by Process Runner as a data source.

•Use External Excel File: Use any external Excel File as a data source.

•Sheet Name: Select the Sheet which contains the data for processing in iBook (internal) or external Excel file.

•Refresh Sheet Name: Refresh button will get list of all the sheets in Excel File or iBook. Once refreshed you can pick up the correct sheet.

•Start Row: Sets first Excel row where Process Runner will start from when you run this file.

•End Row: Sets the last Excel row where Process Runner must stop executing the run. If there is no data before End Row, process runner will stop even before it reaches the End Row.

•Turn off auto log column and use this column: By default, Process Runner automatically finds last available Excel columns and places return log in this column. If you rather want to have a log in specific Excel column, check the box and provide the column you want Process Runner to write a log.

Click here  to know about SAP returned Message Settings

•Display Return Message ID and Number: Selecting this option will force Process Runner to write Message Id and Message number returned by SAP along with usual descriptive message.

•Stop Transaction on Commit and Run in batch input mode:  Selecting this option will force Process Runner to stop the transaction and run the transaction in batch input mode when it encounters COMMIT statement. Unselecting this option will force Process Runner to continue the transaction even when it encounters COMMIT statement.

•Convert all data to upper: Selecting this check box will force Process Runner to convert all the data read from Excel to upper case before sending to SAP.

•Background Mode: Some transactions require you to turn on Background simulation for successful execution. You can set this option before recording in Process Runner New wizard.

•Copy from SAP to Excel Settings: This settings are automatically displayed if you have manually/forcibly set a field to "SAP to Excel" mapping type.

•Suppress all "Copy from SAP to Excel" mappings: This will suppress and run the transaction without considering SAP to Excel mapping type.

•Stop transaction on COMMIT and run in BI mode: This option similar to explained earlier but exclusive only for "SAP TO Excel" mapping type fields.

Click here to know about transaction Advance Settings

•Execute Commit after RUN: Selecting this option will force Process Runner to execute COMMIT BAPI after each run. Many new BAPIs do not have COMMIT statement inside them. Turning on this option will force those BAPIs to execute COMMIT.

•Wait till Commit finishes:  This option is available only when your turn on "Execute Commit after RUN" option. Turning on this check box will force Process Runner to wait till SAP returns till COMMIT finishes (i.e. usually when DB writes are done)

•Convert to upper case:  Selecting this check box will force Process Runner to convert all the data read from Excel to upper case before sending to SAP.

•Lock/Unlock each record during run: Selecting this check box will en-queue/de-queue employee records during run.

•Append to next blank row: Selecting this check box will force Process Runner to append the text to next row.

•Add values sent to SAP while downloading table values: By enabling this option it will write values sent to SAP via "upload to SAP" tab to be added to downloaded table records. This will enable to connect table records to original requested key and other fields and would be useful when downloaded table does not include originally requested key fields.

•Auto mark X structures: Selecting this check box will automatically automap the X structure values.

•Execute Save/Close BAPI: This option is used when you need to execute _SAVE or _CLOSE BAPI to save the objects successfully. Enabling this option forces Process Runner to execute the corresponding BAPI after executing the main BAPI.

•Display return message Id and number : By selecting this option ,it will force Process Runner to write Message Id and  Message number  returned by SAP along with usual descriptive message.

•Convert all Data to UPPER: By selecting this option , it will force Process Runner to convert all the data read from Excel to upper case before sending to SAP.

•Run in direct execute mode: By enabling this option , it will force Process Runner to run the script file in direct execute mode in which "Find value or Suppress field " option is selected in Mapper.If you run process file in “Run in direct execute mode” then debug option is not available.

•Disable GUI History: When this option is enabled, data entered during run time is not cached in field history. This improves the performance. If you wish to see all the records entered then uncheck this option, bu doing so SAP GUI takes longer time to execute the transaction.

•Max. Record for Extraction: Specify the maximum record length to be extracted. 0 is for entire table extraction. You can also use value from Excel cell to indicate how many records to be extracted.

    Example: C2 (If cell C2 has value of 200 specified, it will extract 200 records only).

•Ignore Excel and write output to Text file/MS Access table: Extract Data and write entire output to MS Access database instead of Excel/iBook. For more information on this refer Export to Text and Import to Microsoft Access from Process Runner

•Use Data Filters: These are the various filters users can use to filter their data.

•Data Filter Builder: Specify field level filters with this option.

•ABAP: Write custom ABAP code to filter your data extraction.

•From Excel Column: Pick up a filter defined in an excel column.

•Logon Shortcut: Select the Logon Shortcut file created by iLogon. This will bypass manual SAP logon prompt instead Process Runner will use information stored in Logon Shortcut file you specify here to logon to SAP. You can also refresh the Logon shortcut file list by clicking on Refresh button beside.

•Do not close SAP connection after each RUN: This option will force Process Runner not to log off from SAP after it's done running all the transactions or BAPI calls.

•Number of Parallel Processing threads to use: Tells how many threads should Process Runner divide work in. Process Runner will automatically start number of threads you select in parallel and send them to SAP in those many threads. This could dramatically improve the overall load time.Care should be taken as using more threads means consuming more Dialogue threads in SAP.  By default maximum 3 threads are possible. If you need more threads, you must have special license from Innowera.

•Launch SAP GUI: This option will launch SAP GUI session as well. Some transaction requires that you Launch SAP GUI as well. This is particularly true if you are downloading a file to your desktop. Usually Process Runners sets this flags automatically but in some cases you may have to set it manually.

•Error Processing Run: Run, Debug with Error Processing Run flag On.

•Test Run: Run, Debug with Test Run flag On.

Click here to know about Test Run Settings