Settings in Process Runner

The advance settings section of Process Runner varies among various technologies i.e. advance settings available at Transaction, BAPI/RFM and DE are different from each other. Expand the following toggles to acquire precise knowledge of Advance settings for each technology.

The message settings of SAP can be altered by the user according to the requirement. The message displayed at every transaction will be according to the message settings configured at the user-end. Following toggles will explain the effects of each message settings.

Usually FI Company Code Settings are used for finance transactions in SAP where single vendor has more than one unit (company codes). In such circumstances, user can configure the settings from FI Company code settings.

Module	Option	Description/Sub Option
Inter Company Transaction	Automatically Handle inter-company scenario	'Inter Company Transaction' settings are implemented in scenarios when more than one company codes are there in a single financial transaction. Example: In Transactions like FB01; If the Line Item company code differs from the Header company code, then the screen number is changed for different company code by SAP. Hence 'Inter Company Transaction' settings of Process Runner are used to handle such scenario dynamically. Process Runner user needs to provide Header Company Code Field name and Line Item Company Code Field Name to verify and handle inter company code scenario.
	If enter-company screen error is detected during run, prompt user to Auto-Fix this error	Enabling this radio button will prompt user to Auto fix the error encountered during run.
	Do not prompt to Auto Fix	Enabling this radio button will automatically handle inter-company scenario and will not prompt Auto Fix pop-up during execution.

Multiple Company Code Settings	Automatically handle company code changes across multiple documents	'Multiple Company Code' settings are implemented in events when company codes are changed between each SAP call (or between two documents). Example: In Transactions like FB50; SAP displays Company Code pop-up for the first call only and the same company code entered by user is considered for subsequent calls. In such event, if change in company code is required for any of the subsequent calls, the Multiple Company Code settings of Process Runner are configured to dynamically change the company code.
	If company code screen error is detected during run, prompt user to Auto-Fix this error	Enabling this radio button will prompt user to Auto fix the error encountered during run.
	Do not Prompt to Auto Fix	Enabling this radio button will automatically handle multiple company code scenario and do not prompt Auto Fix pop-up during execution

Following are the generic steps to configure the FI Company Code Settings

1.Go to 'Advance Setting' command from 'Settings' group at Home ribbon tab.

2.At 'FI Company Code Settings' tab of 'Advanced Settings' dialogue box, configure relevant settings using the above described table.

Use this setting to dynamically change the screen number based on key value. This feature changes screen name/number in mapper at the run time based on value you have in Excel. use cases are Finance, HR transactions where screen number changes based on posting key, organization values etc. You can use this feature when screen changes based on same key value and such value is coming from Excel.

Auto fix settings refer to expert settings that are used to configure several rules that play an important role during runtime. Following table describes influence of each option stationed at Auto Fix tab in Advance Settings.

Module

Option

Description/Sub Option

BDC Cursor Settings

Always prompt for fixing incorrect BDC_CURSOR field error

By enabling this radio button Process Runner will prompt the user to auto fix the incorrect BDC_CURSOR field error.

Do not prompt for fixing incorrect BDC_CURSOR fields while running

By enabling this radio button Process Runner will prompt the user to fix the BDC_CURSOR field error.

Always disable all BDC_CURSOR fields while running.

By enabling this radio button Process Runner will disable all BDC_CURSOR fields while running.

Missing OK Code Settings

Always validate "Missing OK_CODE" before run

By enabling this radio button Process Runner will always validate the Missing OK_CODE before running.

Never validate "Missing OK_CODE"

By enabling this radio button Process Runner will never validate the missing OK_CODE.

Central Address Management Settings

Disable "Central Address Management" check at runtime

Enabling this radio button will not allow "Central Address Management" check at runtime.

Missing Screen Settings

Auto fix missing screen error

Enabling this option will automatically fix the missing screen error occurring with finance transactions.

Sub-Option	Description
Retry Count	Specify the retry count before fixing the screen error
Attempt to auto fix missing screen error (E:00-344) - for all subsequent calls	Enabling this radio button will auto fix the missing screen error for all the calls
Attempt to auto fix missing screen error (E:00-344) - checking each calls	Enabling this radio button will auto fix the missing screen error after checking each calls

Run Controls (static run only): This option can be changed only when 'Record Controls' option is enabled during recording transaction. When you activate this option, Process Runner records SAP control framework objects (ALV grid, tree view etc.) in static mode. You can run the transaction with such controls but any input to these controls cannot be changed at run time.

Module	Option	Description/Sub Option
Run Controls (static run only)	Perform standard operation	This setting is applicable for finance transactions. By enabling this option Process Runner will automatically handle the inter company code scenario.
	Remove unnecessary records	Enabling this radio button will prompt user to Auto fix the error encountered during run.

The following table represents various options at Advance Settings of BAPI/RFM process file.

Option	Description
Convert SAP date to Excel system date on BAPI/RFM receive	Enabling this option will always convert the SAP date according to Excel date and format upon data receipt.
Format SAP time on BAPI/RFM receive	Enabling this option will convert SAP time retrieved from SAP according to the Excel time and format.
Auto truncate width fields (CHAR, NUM, BYTE) to match with required width AND continue to SAP	If the field width in Excel is longer than that of SAP, then this option will automatically truncate fields and continue to SAP.
Auto Skip Missing field and continue running the process	Enabling this option will automatically skip missing fields in Excel and continue running.

The Advanced Settings in Process Runner varies among various technologies i.e. Advanced Settings available for Transaction, BAPI/RFM and DE are different from each other.

To configure advanced settings for Data Extractor

1.In Process Runner, select Advanced from Home tab. The Data Extractor Settings window appears.

2.Enter the following information in Settings Details section:

•Skip First: Indicates the number of records to be skipped while extracting the data from SAP.

•Block Size: Indicates the number of records to be extracted as a block at one time. So the number of calls made to SAP will depend on the block size to extract the total number of records specified. For example, if the Max. record for extraction field in the Home tab is set to 1000 and block size is set to 500 records, then only two calls will be made to SAP and 500 records will be extracted in each call.

3.Optionally, perform the following steps in Excel and Extended RFM Settings section:

•Select Append to next blank row to append the record to the next blank row in the Excel file. However, if you have more than one record to be returned, downloaded records in Excel may not match with the existing Excel records.

•Select Append to next blank row when this process is child process connection chain if the current file is a child process of the previous run. If selected, the data is append after the last row of the previously processed call.

•Select Ignore field mapping and write entire output to column and specify the column to ignore the mapping field and extract the data in the specified column.

•Select Execute Fields Exits to convert the SAP internal value and extract them as display value.

•Select Reverse Server block execution to overcome the extraction of duplicate or missing records. To use this option, make sure to implement the Innowera Custom RFM version 2.5 in the SAP system that you use while running the Data Extractor process file. For more information about how to configure the Data Extractor advanced settings, see Data Extractor Settings.

Note: If you select Reverse Server block execution, error messages similar to the following may appear:

•"Stopped due to time limit exceeded"

•"Stopped due to CPIC-CALL: 'CMRCV: rc=19...".

In such cases, you can increase the value of the "rdisp/max_wprun_time" parameter in the SAP system from which the data will be fetched.

Data Filter Settings