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

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

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

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

•     Max. Record for Extraction: Specify the maximum record length to be extracted. 0 is for entire table extraction.

•     Skip First: Indicates the number of first records to skip.

•     Block Size: The total block size of the record to extract in one call.

•     Ignore field mapping and write entire output to column: This will ignore all mappings and write entire output to one excel column.

•     Ignore Excel and write output to Text file/MsAccess 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

•     Append to next blank row: Tells Process Runner to extract and append the record in next blank row in MS Access.

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

•     Convert All Data to Upper: This will extract and convert all data to upper after extraction.

•   Launch SAP GUI (available only in Transaction and Data Extractor) : 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.

Settings:

These are the Test Run Settings that user can configure according to the required Run Scenario.

•     Lock Test Run: This will save and lock the test run settings and wont allow to be edited unless the lock is released.

•   Display only following messages: This option allows user to selectively display the messages as required. "P-Process Runner" message will display the user defined message stored in Options-> Transaction tab-> SAP Return Message setting.

Advance option:

Processing preference:

•     Individual Line Level Check: perform line level test and error processing check.

•     Document Level Check: perform test and error processing check for the whole document

•     OK CODE to find: Search an OK CODE to replace with.

•     OK CODE to replace: Replace the OK CODE to find with this one.

•     Add Special Process Runner Routine for the Test Run

•     Soft Exit: normally exit the Transaction

•     Force Exit: forcefully exit the transaction

•     Always display Test Run warning Message: it will always prompt with the below message