•Use Internal XML Table (iTable): Process Runner DB Supports XML source so you can work even when you are not connected to any database. It provides built in XML table which works the same way as any other database table. You can save and update the data in this internal XML table.

•Use Database: Process Runner DB supports major databases and allows you to upload and download data from connected database table to SAP. It supports following databases.

•     Oracle

•     Sybase

•     My-SQL

•     MS-SQL Server

•     DB2

•     MS-Access

•Table: Select the required table for the selected database.

•Status Column: This can be any column in table with type string. It will contain the status of your current record execution.

•Log Column: This column will retrieve the result of the current record similar to Status column.

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

•Max Row: Sets the maximum Data Source row till where you want to run this file.

•Order By: This option will group similar records based on field specified.

Please note that when working with SAP HANA DB, if the order is not specified with an ORDER BY clause, then the order of the data returned by the database is undefined (not sorted). It is must to use an ORDER BY clause if the order is relevant. Hence select an auto increment numeric field from OrderBy dropdown in Database setting of Home tab  to return a sorted result. The below error message is displayed on execution of process file if the OrderBy dropdown is left blank.

•Start / End Script: Start script is executed before you RUN Process Runner DB process. It can be any Stored Procedure, batch file or an exe. End script is similar to start script but it is executed after RUN.

Click here to know more on Pre-Run and Post-Run Process Settings.

•Use internal XML table (iTable) : Process Runner DB Supports XML source so you can work even when you are not connected to any database. It provides built in XML table which works the same way as any other database table. You can save and update the data in this internal XML table.

•Use Database: Process Runner DB supports major databases and allows you to upload and download data from connected database table to SAP.

•Write entire output to text file: Extract the Data and write entire output to text file instead of iTable.

•Table: Select the required table for the selected database.

•Status Column: This can be any column in table with type string. It will contain the status of your current record execution.

•Log Column: This column will retrieve the result of the current record similar to Status column.

•Block ID Column: This column displays the block Id defined by user for data extraction.

•TimeStamp Column: This column displays the timestamp at what time data is extracted.

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

•Stop Transaction on COMMIT and run in BI mode: Selecting this option will force Process Runner DB to stop the transaction when it encounters COMMIT statement and run the transaction in batch input mode. Unselecting this option will force Process Runner DB to continue the transaction even when it encounters COMMIT statement. You may have to unselect this option for some of the transactions. This check box is usually tied with "Run in batch input mode" check box.

•Convert all data to UPPER: Selecting this check box will force Process Runner DB to convert all the data read from iTable 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.

•Advanced Settings :  

oAuto fix missing screen error: Enabling this option will automatically fix the missing screen error  which occurs with finance transactions.

•Execute COMMIT after Run: Selecting this option will force Process Runner DB 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 DB to wait till SAP returns till COMMIT finishes (i.e. usually when DB writes are done)

•Convert all data to UPPER: Selecting this check box will force Process Runner DB to convert all the data read from iTable/Data Source to upper case before sending to SAP.

•Continue on constrain violation and write to Log: Selecting this checkbox will force Process Runner DB to continue the  process execution if value return from SAP does not match column data type and write  the status in Log.

•Display return message Id and number : By selecting this option ,it will force Process Runner DB 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 DB 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 DB 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 enabled,  this option disables the GUI feature of storing previous entries.

•Close GUI(s) at the end of each run: Process Runner DB automatically closes GUI sessions at the end of each run when you select this option.

•Max.Record for Extraction: Maximum limit of records that can be extracted in Data Extractor.

•Use Data Filters: Customize download from SAP using this option. There 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.

•Logon Shortcut: Select the Logon Shortcut file created by iLogon. This will bypass manual SAP logon prompt instead Process Runner DB will use information stored in Logon Shortcut file you specify here to logon to SAP.

•Refresh logon shortcut file: This option allows you to retrieve Logon Shortcut file list. After clicking refresh button, you can pick up correct logon shortcut file.

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

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

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

Settings: