Home Tab

The Home tab displays and allows you to maintain information about the file you are working on. For example, it shows which Excel file will be used and how the Transaction or BAPI should be run in SAP. You can also control how to perform SAP logon and how many parallel sessions to use.

The Home tab and Edit tab have a common set of options in the Excel section. If Process Connection is enabled in the View section of the Home tab, then an additional panel for process connection is displayed in the lower pane of the window.

To configure the options in the Excel section,

1. In Excel File, select the browse icon to browse and select the path of external Excel file on your local system. Alternatively, select the Excel icon to open the Excel file that is in the selected path.

   

2. In Sheet name, select the sheet name from the dropdown list. When the Process file is run, the results are displayed in the selected sheet.
3. In Start row, select the first Excel row from where Process Runner must start the run.
4. In End row, select the last Excel row where Process Runner must stop the run. If there is no data before End Row, Process Runner stops before it reaches the End row.
5. To write the run logs in a specific Excel column, select Turn off auto status and log column and use this column and enter the column value. By default, Process Runner finds the last available Excel column and places the return log in this column.
6. Run the Process file.

This section contains the following topics:

• Run Actions
• Logon and Performance Parameters
• Settings
• Tools
• View

Run Actions

This section contains information about the different run options for the Process files. Some of the run options are available only for some of the technologies.

For information about the different run options, see the following:

• Run
• Error Processing Run
• Test Run
• Debug Run
• Data Validation Run

For information about how to configure the test run settings, see Test Run Settings. For information about how to stop a Process file run, see Stop.

Run

This topic describes how to use the Run option to run a Process file. You can run a file from the Home, Edit, or Mapper tabs.

This section contains the following topics:

• Run process file using SAP GUI
• Run process file using OData
• Run GUI Scripting Process file

Run process file using SAP GUI

This topic describes how to run a Transaction, BAPI/RFM, or Data Extractor Process file using the SAP GUI.

To run a Transaction, BAPI/RFM, or Data Extractor Process file using the SAP GUI,

1. Open the Process file.
2. Select Run in the Run Actions section on the Home tab. Alternatively, select the F5 button from keyboard.
3. In the Connector for SAP window, select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.

   Note: If EP/SSO is configured, use EP/SSO to log on. For information about EP/SSO, see Sign in to Enterprise Portal/SSO.

   

4. Select OK. The Transaction, BAPI/RFM, or Data Extractor Process file is run.

Run process file using OData

This topic describes how to run a Transaction, BAPI/RFM, or Data Extractor Process file using the OData service.

Some of the restrictions when using the OData service are as follows:

• Process Runner supports only the following SAP Tcodes (TX technology) for OData services:
  • Material Master: MM01, MM02, and MM03
  • Sales Orders: VA01, VA02, and VA03
  • Purchase Orders: ME21N, ME22N, and ME23N
  • Bill of Materials: CS01, CS02, and CS03
    • Mandatory fields for CS01: Material, Plant, BOM Usage.
    • Mandatory fields for CS02 & CS03: Material, Plant, BOM Usage, Alt BOM.
    • Mandatory fields for CS02 line items is BOM item node number along with the above.
    • Inserting line items in CS02 is not supported.
• For Sales Orders, Purchase Orders and Bill of Materials Tcodes:
  • All valid line items are updated in SAP.
  • For any invalid line items, the corresponding error message (along with the item ID) is captured and displayed in the Excel output.
  • This ensures that the user is informed about the specific line items causing the issue.
• In VA02-salesorderitem number and ME22N-purchaseOrderItem number are mandatory to update multiline items.
• In VA01, VA02, ME22N, and ME21N, adding or updating sub-entities (conditions, partners, text, and schedule lines) is not supported for multiline items.
• During creation (VA01, ME21N, CS01), common properties shared between the header and line items (with the same field, table, and property name) are mapped to the header by default. As a result, the header values are automatically inherited by all line items.
• During update (VA02, ME22N, CS02), since these common properties are always mapped to the header by default, updating them individually for each existing line item is not supported. This is due to the SAP behavior and OData design limitation.
• OData does not support Error Process Mode, Test Run, Debug Run, and Debug-All Screens features.
• OData does not support mixed mapping types, process files with loops, copy from, or Extended RFM options.
• OData (both read and write) does not support Basic Data Text, Sales Text, Purchase Order text fields, or Multiple descriptions.
• Hyperlink functionality is not supported.

Prerequisites

To run a process file using the OData, the SAP system you are selecting should be configured to OData. To configure OData in an SAP system, see Configure OData in an SAP system.

To run a Transaction, BAPI/RFM, or Data Extractor Process file using the OData,

1. Open the Process file.
2. Select Run in the Run Actions section on the Home tab. Alternatively, select the F5 button from keyboard.
3. In the Connector for SAP window, move through and confirm the status of OData for the SAP system you are selecting is Yes.

4. Select the SAP system. The SAP Logon window appears.

5. Enter the information for Client, User, Password, and Language.
6. Select OK. The Transaction, BAPI/RFM, or Data Extractor Process file is run.

Run GUI Scripting Process file

To run a GUI Scripting Process file in Process Runner, perform the following steps:

1. Open the Process file.
2. Select Run in the Run Actions section on the Home tab. Alternatively, select the F5 button from keyboard.
3. In the Select GUI session where you want to run this process window, select the following options:
   • Warn on Attach: Notifies when a script is attached to a running GUI.
   • Warn on Connection: Notifies when the script opens a connection.

   

4. If you select Start and use new SAP GUI Session, you are prompted to the log onto the SAP system in the Connector for SAP window.
5. If you select an existing GUI Session, the run of the GUI Scripting Process file starts immediately in the selected SAP GUI session.
6. Select OK. The GUI Scripting Process file is run.

Error Processing Run

This topic describes how to use the Error Processing option to troubleshoot the errors that you might have while running a Process file. You can perform an error processing run from the Home, Edit, or Mapper tabs.

Note: The Error Processing option is applicable only for Transaction and RFM/BAPI technologies.

To use the error processing option,

1. Open the Transaction or the RFM/BAPI Process file.
2. Select Error Processing Run in the Run Actions section on the Home tab. The Error Processing Options window appears.
3. Enter the column number where the error must be stored.
4. Select OK. The Connector for SAP window appears.
5. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
6. Select OK. The error processing run of the Process file starts.

   

Test Run

This topic describes how to use the Test Run option to validate the data that must be entered while running the Process file. You can perform a test run from the Home, Edit, or Mapper tabs.

Usually, a test run is done to test the line items to verify that the data entered is accurate. The results of the test run are displayed in the logs in the external Excel.

Refer to the video to understand a test run.

To use the test run option,

1. Open the Process file.
2. Select Test Run in the Run Actions section on the Home tab. The Test Run Warning window appears.

   

3. Select Continue. The Connector for SAP window appears.
4. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
5. Select OK. The test run of the Process file starts.

Test Run Settings

This topic describes how to configure the options in the Test Run Settings window. You can configure the messages that are displayed during the test run.

To configure test run settings,

1. Open the Process file.
2. Select Test Run > Test Run Settings in the Run Actions section on the Home tab. The Test Run Settings window appears.

   

3. Perform the following steps:
   1. To restrict the test run execution, enable Lock/Disable Test Run.
   2. In Display only following messages section, select options, such as S-Success, W-Warning, P-Process Runner, and others, to display only the specific kind of messages. P-Process Runner displays the user-defined message stored under Options > Transaction > SAP Return Message tab.
4. In Advance Option section, select the following options:
   • Text to display: Indicates the text that is displayed in log column in the external Excel file.
   • Processing Preference: Indicates how the search behavior for OK CODE to find must be performed. When the selected OK CODE to find is found, it is replaced with the one that you enter in OK CODE to replace. The options are as follows:
     • 1 - Individual Line Level check: Searches in a line-by-line manner for test and error processing runs.
     • 2 - Whole document check: Searches at the end of the call or document for test and error processing runs.
     • 3 - Test Run line level + Whole document: Searches in an line-by-line manner and at the end of the call or document for test and error processing runs.
   • OK CODE to find: Is the code that must be searched for.
   • OK CODE to replace: Is the code that replaces the code selected in the OK CODE to find option.
   • Add special Process Runner routine for the Test Run: Indicates how the run must be exited.
   • Always Display Test Run warning message: Indicates that a warning message is displayed that indicates the warning of test run mode.
5. Select OK. The changes are saved.

Debug Run

This section describes how to use the Debug-All Screens to view the location of errors in a Transaction or GUI Scripting Process file in a step-by-step manner. You can perform a debug run from the Home, Edit, or Mapper tabs.

Note: The Debug-All Screens option is applicable only for Transaction and GUI Scripting technologies.

To use the debug run option,

1. Open a Transaction or a GUI Scripting Process file.
2. Select Debug-All Screens in the Run Actions section on the Home tab. The Debug Options window appears.

   

3. For a Transaction Process file, perform the following steps:
   1. In the Debug Options window, enter the required details and select OK. The Connector for SAP window appears.
   2. Select the SAP system, select Logon, enter the information for Client, User, Password, and Language, and select OK. The debug run of the Transaction Process file is started.
4. For a GUI Scripting Process file, perform the following steps:
   1. In the Select GUI session where you want to run this process window, select the following options:

      

      • Warn on Attach: Notifies when a script is attached to a running GUI.
      • Warn on Connection: Notifies when the script opens a connection.
      • Start debug row: Sets the first Excel row where Process Runner initiates the run on the external Excel file.
      • End debug row: Sets the first Excel row where Process Runner stops the run on the external Excel file.
      • Use external debugger: Indicates that an external script debugger like Microsoft Script Debugger is required. This option runs only one row or one looping row.
   2. If you select Start and use new SAP GUI Session, you are prompted to the sign in to the SAP system in the Connector for SAP window.
   3. If you select an existing GUI Session, the debug run of the GUI Scripting Process file starts immediately in the selected SAP GUI session.

Data Validation Run

This section describes how to use Data Validation for FB01 and FBV1 transactions. You can perform a data validation from the Home, Edit, or Mapper tabs.

Before performing the data validation run, ensure that your SAP user account has read-only permission for the following SAP tables.

To use the data validation run option,

1. Open a FB01 or FBV1 Transaction Process file.
2. Select Data Validation in the Run Actions section on the Home tab. The Connector for SAP window appears.
3. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
4. Select OK. The data validation run of the Process file is started and Process Runner displays the data validation messages in the log column in the Excel file. For example, data validation can continue only if the Company Code column has valid data.

   Data validation run successful

   

   If the Company Code column is empty, then the data validation run is not completed.

   Data validation run not completed

   

Stop

You can use the Stop option to stop the Process file run using Stop in the Run Actions section on the Home, Edit, or Mapper tabs.

Logon and Performance Parameters

This section contains information about how to configure the control parameters options. It also contains information about the logon and performance options.

For information about how to configure the control parameters for the different technologies, see the following:

• Transaction Control Parameters
• BAPI/RFM Control Parameters
• GUI Scripting Control Parameters
• Data Extractor Control Parameters

For information about how to configure the logon and performance parameters, see Logon and Performance Parameters. If you have configured Dashboard, the Dashboard option is also displayed in the Logon and Control Parameters section. For information about how to configure Dashboard notes, see Dashboard.

Transaction Control Parameters

This topic describes how to configure the control parameters for a Transaction Process file.

To configure control parameters,

1. Open the Process file and go to the Home tab.
2. Select Run in batch input mode to record multiple transactions without any interruptions.
3. In the Logon and Control Parameters section, select the pop-up icon. The Logon and Control Parameters window appears.

   

4. Depending on your requirement, perform the following steps:
   • Select Stop Transaction on COMMIT and run in BI mode if you want Process Runner to stop the transaction at COMMIT statement and run the transaction in batch input mode.
   • Select Background Mode to activate background simulation for successful call.
   • Select Run Controls (static run only) to records SAP control framework objects (ALV grid, Tree View etc.) in static mode. The transaction can be executed with such control though any input at these controls cannot be changed at run time. Do not map or change any values that is sent to control object as it will not be effective and the recording might not work. Mapping to values outside of control object should work as usual and mapping should be performed as required.
   • Select Suppress DRS to split the large document into multiple documents without any changes in SAP and implementing ABAP program.
   • Select Suppress all "Copy from SAP to Excel" mappings to suppress the copy of data extracted from SAP to Excel.

     Note: Copy from SAP to Excel is enabled only if mapping type SAP to Excel is selected.

   • Select Display return message ID and number to retrieve the message ID and the number associated with SAP returned message.
   • Select Convert all Data to UPPER to convert the data to upper case before sending it to SAP.
5. Select OK. The changes are saved.

BAPI/RFM Control Parameters

This topic describes how to configure the control parameters for a BAPI/RFM Process file.

To configure control parameters,

1. Open the Process file and go to the Home tab.
2. In the Logon and Control Parameters section, click the pop-up icon. The Logon and Control Parameters window appears.

   

3. Depending on your requirement, perform the following steps:
   • If Process Runner must call BAPI_TRANSACTION_COMMIT in the background for its execution after the ongoing transaction, select Execute COMMIT after Run. If you do not select this option, then Process Runner does not wait for the completion of current execution and instead run the BAPI_TRANSACTION_COMMIT first. Alternatively, you can select Execute COMMIT in the Logon and Control Parameters section.
   • If Process Runner must wait for the completion of execution of BAPI_TRANSACTION_COMMIT after the current execution is completed, select Wait until COMMIT finishes. If you do not select this option, then Process Runner does not wait for the completion of current execution and instead run the BAPI_TRANSACTION_COMMIT first.
   • To lock the transaction while the Process file is being run that helps to prevent simultaneous transactional changes, select Lock/Unlock each record during run.
   • To append the record to the next blank row in the Excel, select Append to next blank row. However, if you have many records to be returned, downloaded records in Excel may not match with the existing Excel records.

     When Append to next blank row is not selected

     

     When Append to next blank row is selected

     

   • To send the data to SAP in uppercase, select Convert all data to UPPER.
   • To dynamically map X indicator for the provided input values as per mapper because BAPI structure requires that we pass X indicator for the provided input values, Select Auto Mark X structures. This helps determine whether the input values exist or not for the corresponding field for that particular field.
4. Select OK. The changes are saved.

GUI Scripting Control Parameters

This topic describes how to configure the control parameters for a GUI Scripting Process file.

To configure control parameters,

1. Open the Process file and go to the Home tab.
2. In the Logon and Control Parameters section, select the pop-up icon. The Logon and Control Parameters window appears.

   

3. Depending on your requirement, perform the following steps:
   • Select Direct Execute Mode to stop the GUI Script at COMMIT statement and run it in batch input mode. When recording a GUI Scripting file, COMMIT is triggered at the completion of a single GUI Script. COMMIT is an interruption of a running program, such as screen processing, message output, or RFC call. If you do not select this option, then the GUI Script is continued even when it encounters a COMMIT statement.
   • Select Disable GUI History to disable the capturing of history of the GUI transaction. If you do not select this option, the values that were entered in the field earlier is displayed as dropdown options.
   • Select Auto Correct Warning Message to handle run-time warning messages of SAP during the GUI Scripting Process file run, which leads to an uninterrupted run of the file.
   • Select Convert all data to UPPER to send the data to SAP in uppercase.
4. Select OK. The changes are saved.

Data Extractor Control Parameters

This topic describes how to configure the control parameters for a Data Extractor Process file.

To configure control parameters,

1. Open the Process file and go to the Home tab.
2. In the Logon and Control Parameters section, select the popup icon. The Logon and Control Parameters window appears.

   

3. Depending on your requirement, perform the following steps:
   • In Max. Record for Extraction, enter the number of records that must be extracted. If you enter 1000, only the first 1000 records are extracted. Enter 0 to extract all the records.
   • To extract the data and write the entire output to a text file or Microsoft Access database, select Ignore Excel and write output to Text file/MsAccess table.
   • To send the data to SAP in uppercase, select Convert all data to UPPER.
4. Select OK. The changes are saved.

Logon and Control Parameters

This topic describes the Logon and Performance tab of the Logon and Control Parameters window.

To configure logon and performance parameters,

1. Open the Process file and go to the Home tab.
2. In the Logon and Control Parameters section, select the popup icon. The Logon and Control Parameters window appears.
3. Select the Logon and Performance tab.

   

   • To assign a logon shortcut to the Process file, select Logon Shortcut and select a shortcut from the dropdown list. The Process file uses the assigned logon shortcut when it is run. Usually, this option is helpful in cases when the scheduler is used to schedule the Process files.
   • To prevent Process Runner from logging off SAP after transactions and BAPI calls are run, select Do not close SAP Connection after each run.
   • To set the number of parallel threads that can be processed simultaneously when a Process file is run, select the number of threads in Parallel threads. When you run a Process file, you can monitor the external Excel file; by default, each row is processed serially.

     Note: The parallel processing functionality can improve the overall load time, but using more threads lead to consumption of more dialogue threads in SAP. By default, only three threads are possible; extension for the number of parallel threads in Process Runner requires a special license from insightsoftware. Also, if you are using the DRS functionality, you cannot use the parallel thread mode more than once. Refer to the video for information about parallel processing in Process Runner.

   • To make the RFC connection by launching SAP GUI, select Launch SAP GUI. This option avoids SAP dump or connection timeout.
4. Select OK. The changes are saved.

Dashboard

This topic describes how to configure the Dashboard notes and reference information for a Process file that can be used to identify the run in the Stat window.

Caution: The Dashboard option appears on the Home tab only if you have selected Enable Dashboard in the Tools > Options window > Enterprise Settings > Dashboard tab.

To configure Dashboard parameters,

1. Open the Process file and go to the Home tab.
2. In the Logon and Control Parameters section, select Dashboard. The Dashboard Notes window appears.

   Note: The first time you run a Process file that has not been saved, the Dashboard Notes window appears automatically so you can enter project data. After the file is saved, the window does not appear automatically on subsequent runs.

3. Enter the following information:
   • Project ID: Indicates the ID that is displayed in the Project column in the grid of stat records.
   • Ticket ID: Indicates the ID that is displayed in the Ticket/Issue ID column at grid of stat records.
   • Notes: Indicates the notes or comments that is displayed in the Notes column of stat records.
4. Select Confirm on Every Run. The Dashboard notes and configuration details are confirmed on every run of the Process file and are displayed in the Stat window.

   

Settings

This section contains the following topics:

• Message
• Advanced
• Data Filter
• Join Condition
• Export Data to Text File or Microsoft Access

Message

This topic describes how to configure the SAP message settings.

Note: The Message option is available only for Transaction, BAPI/RFM, and GUI Scripting technologies.

To configure message settings,

1. Open the Process file for which you want to configure the message settings, and select Home > Message. The SAP returned messages setting window appears.

   

2. To configure the display messages, go to the Basic Setting tab and perform the following tasks:
   1. Select the following options from the SAP-returned messages dropdown list:
      • 1-Display only first: Displays only the first message that is returned from SAP to Excel. All other SAP-returned messages are avoided.
      • 2-Display only last: Displays only the last message that is returned from SAP to Excel. All other SAP-returned messages are avoided.

      Note: We recommend that you do not implement 1-Display only first and 2-Display only last options because of the limitations.

      • 3-Display all: Displays the messages depending on the suboptions you select. For example, select P-Process Runner to display all the messages related to Process Runner. This option is useful for complex transactions that require implementing various security levels.
   2. (Only for GUI Scripting) Select the following options in the What to do when ERROR is encountered section:
      • Continue current transaction: Allows you to select the Ignore 'control not to be found' messages checkbox. If you select this option, the transaction continues irrespective of the warning messages.
      • Stop current transaction: Stops the ongoing transaction.
   3. Select OK. The changes are saved.
3. (Only for Transaction and BAPI/RFM) To modify the message text, go to Message Text transformation and select the Transform SAP message as per following settings checkbox. The following SAP message modification settings are enabled:
1. Select the Id and No for which changes must be made and modify the default message and status.

   Note: If the message you want to modify is not listed in the table, you can manually add it by entering the ID, number, return message, and status. You can find the messages in the log column of the Process file after the file is run.

2. Select OK. The SAP message text and status are configured for the file.

   Note: You can customize message for four SAP parameter values.

   Refer to the video to understand the functionality of SAP Message Text Transformation.

4. (Only for Transaction and BAPI/RFM) To view the message variable values, go to Return value(s) mapping , and select the Map transaction return values to Excel column checkbox. The return value mapping settings are enabled.
   1.  Select the following options:
   • Auto write to next Excel Column: Places the next value in the next Excel column.
   • Write to Excel column as defined below: Places the next value in the column as per the defined configuration for the Excel value for Value 1 through Excel value for Value 4 fields.
   • Do this only for the last message record: Displays the configured settings for only the last message record.
   • Turn off auto status and log column and use this column: Enables you to specify the Excel column in which Process Runner writes the log.
   2. Select OK. The message variable values are displayed in the selected and Excel-mapped column.  

Note: This feature is useful when message variable values are processed in different connected processes.

5. (Only for Transaction and BAPI/RFM) To configure the success messages with a hyperlink, go to Hyperlink and select the Add Hyperlink to the success message on each run checkbox. Perform the following steps:
1. In Transaction Code, enter the transaction code and in Parameter Command, enter the SAP field names for the transaction code and enter the parameter command to get the SAP return message or Excel column value.
   • %IRETVALUE<SAP message number>% returns value from SAP message, such as %IRETVALUE1%.
   • %IVALUE@A% returns value of current row from Excel column.
   • %IVALUE@A2% returns value of Excel cell A2.
   • %IVALUE@A.YEAR% fetches the year from value of current row from Excel column.
   • %IVALUE@A.MONTH% fetches the month from value of current row from Excel column.
   • %IVALUE@A.DAY% fetches the day from value of current row from Excel column.
   • %IVALUE@A.HOUR% fetches the hour from value of current row from Excel column.
   • %IVALUE@A.MINUTE% fetches the minutes from value of current row from Excel column.
   • %IVALUE@A.SECOND% fetches the second from value of current row from Excel column.
   • %IRETURN<SAP message number>.MID(Start Index, Length)% fetches the middle characters value from SAP message, such as %IRETURN1.MID(1,10)%.
2. To add the SAP User ID to the hyperlink, select the Add SAP UserID to Hyperlink checkbox.
3. Select OK. A hyperlink is added on each success message that redirects you to the saved data in SAP for the particular run.

Advanced

The Advanced option is available only for Transaction, BAPI/RFM, and Data Extractor technologies.

This section contains the following topics:

• Transaction
• Data Extractor Settings
• BAPI/RFM

Transaction

This topic describes how to configure the advanced settings for Transaction Process files.

To configure advanced settings for Transaction Process file,

1. Open the Process file for which you want to configure the settings, and select Home > Advanced. The Advanced Settings window appears.

   

2. On the FI Company Code Settings tab, to handle finance transactions in SAP where a single vendor has more than one unit (company codes), select the following options:

   • If more than one company code is present in a single financial transaction, select the following options in Inter-Company Transaction:
     • Automatically Handle inter-company scenario: You must enter Header company code field and Detail company code field to compare them.
     • If enter-company screen error is detected during run, prompt user to Auto-Fix this error
     • Do not prompt to Auto Fix

   For example, if in FB01 Transaction, the line item company code and header company code are different, then SAP modifies the screen number for different company codes.

   • If the company codes are changed after each SAP call or if two documents have different company codes, select the following options in Multiple Company Code Settings:

     • Automatically handle company code changes across multiple documents
     • If company code screen error is detected during run, prompt user to Auto-Fix this error
     • Do not Prompt to Auto Fix

   For example, in FB50 Transaction, SAP displays the company code for the first call only, and you must enter the same company code for the subsequent calls. If the company code must be changed for any of the subsequent calls, Multiple Company Code settings are configured to dynamically change the company code.

3. To dynamically change the screen numbers based on a key value, select the Enable Dynamic Screen Mapping checkbox on the Dynamic Screen Mapper tab, and select a value from the Key field from mapper option. The screen name and number in the mapper are changed at runtime based on the value present in Excel.

   

4. To configure the Auto fix settings for updating rules during runtime, select the following options:

   

   • To configure the error check for BDC_cursor field during runtime, select the following options in BDC Cursor Settings: 
     • Always prompt for fixing incorrect BDC_CURSOR field error
     • Do not prompt for fixing incorrect BDC_CURSOR fields while running
     • Always disable all BDC_CURSOR fields while running
   • To configure the missing OK code related settings, select the following options in Missing OK Code Settings:
     • Always validate "Missing OK_CODE" before run
     • Never validate "Missing OK_CODE"
   • To stop the central address management check at runtime, select the Disable "Central Address Management" check at runtime option in Central Address Management Settings.
   • To automatically fix the missing screen error occurring during finance transactions, select the Auto fix missing screen erroroption in Missing Screen Settings. Select the following suboptions:
     • Retry Count: Indicates that you enter the required retry count before the screen error is fixed.
     • Attempt to auto fix missing screen error (E:00-344) - for all subsequent calls:Auto fixes the missing screen error for all the calls.
     • Attempt to auto fix missing screen error (E:00-344) - checking each calls: Auto fixes missing screen error after checking each call.
5. To configure Control Framework settings, select the Run Controls (static run only) checkbox. The SAP control framework objects, such as ALV grid and tree view, are recorded in the static mode. Select the following sub options:

   

   • Perform standard operation: Automatically configures the inter-company code settings for finance transactions.
   • Remove unnecessary records: Fixes the errors occurred during runtime.

   Note: You can select Run Controls (static run only) only if Record Controls option was selected during recording transaction.

   Note: You can run the transaction with these settings enabled; however, they cannot be modified at runtime.

6. Select OK. The changes are saved.

Data Extractor Settings

This topic describes how to configure the advanced settings for Data Extractor Process files.

To configure advanced settings for Data Extractor Process file,

1. Open the Data Extractor Process file for which you want to configure the settings, and select Home > Advanced. The Data Extractor Settings window appears.

   

2. Enter the following information in the 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. Therefore, the number of calls made to SAP depends on the block size to extract the total number of records For example, if the maximum record for extraction field in the Home tab is set to 1000 and block size is set to 500 records, then only two calls are made to SAP and 500 records are extracted in each call.
3. To configure the Excel Setting, select the following options:
   • Append to next blank row: Appends 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.
   • Append to next blank row when this process is child process connection chain: Appends data after the last row of the previously processed call. Select this option if the current file is a child process of the previous run.
   • Ignore field mapping and write entire output to column: Extracts the data in the specified column.
4. To configure Extended RFM Setting, select the following options:
   • Execute Fields Exits: Converts the SAP internal value to display value.
   • Reverse Server block execution: Avoids the extraction of duplicate or missing records. To use this option, ensure that you implement the custom RFM version 2.5 in the SAP system while running the Data Extractor Process file. For more information about how to configure the Data Extractor advanced settings, see Data Extractor.

   Note:

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

   • 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 are fetched.
5. Select OK. The changes are saved.

BAPI/RFM

This topic describes how to configure the advanced settings for BAPI/RFM Process files.

To configure advanced settings for BAPI/RFM Process file,

1. Open the BAPI/RFM Process file for which you want to configure the settings, and select Home > Advanced. The Advanced Settings window appears.
2. To configure the advanced settings, select the following options:
   • Convert SAP date to Excel system date on BAPI/RFM receive: Converts the SAP date as per Excel date and format upon data receipt.
   • Format SAP time on BAPI/RFM receive: Converts the SAP time as per Excel time and format.
   • Auto truncate width fields (CHAR, NUM, BYTE) to match with required width AND continue to SAP: Truncates fields and moves to SAP automatically, if the field width in Excel is longer than that of SAP.
   • Auto Skip Missing field and continue running the process: Skips missing fields in Excel and continues running.

Data Filter

This section describes how to configure the data filter settings for Data Extractor Process files.

The Data Filter option is available only for Data Extractor technology.

To configure the data filter options:

1. Open the Data Extractor Process file that you want to update, select Home tab > Data Filter in the Settings section.
2. To filter the data at field level without writing any ABAP code, select Data Filter Builder. The Data Filter Builder and Join Condition (<NameOfTables>) window appears. Perform the following steps:
   1. In Field Name, select the name of the field that must be extracted.
   2. Update the operator in the Compare Operator column and values in the other columns, such as Dynamic Skip and Dynamic Formula.
   3. Update the Source Value to indicate that the material numbers starting with the specified source value or string pattern must be extracted. If the Source Type is Excel to SAP, you can also select the Source Value from the dropdown options, which are the Excel column headers. For information about how to work with the different source types available in Data filter builder, see Work with Different Source Types.

      

   4. To add, delete, go to next, or go to previous rows, use the options in the lower-left of the window.
   5. Select OK. The changes are saved.
3. To extract data through custom ABAP code, select ABAP. The ABAP window appears. Perform the following steps:
   1. Enter the custom ABAP program.
   2. Select OK. The changes are saved.
4. To filter data using the ABAP query that is mentioned in the cell or column of the external Excel file, select From Excel Column. The From Excel Column window appears. Perform the following steps:
   1. Enter the address of Excel column or cell name where the ABAP query is located in the external Excel file.
   2. Select OK. The changes are saved.
5. Save the Process file and select Run. The Excel file appears with the data extracted.

Review the installed sample BSEG-Accounting Document extract for listed accounts only.ite in the Data Extractor folder for an example.

Work with Different Source Types

This topic describes how to use the different source types in the Data Filter Builder and Join Condition window to filter and download selected pattern of data from an SAP System.

To configure the source type in the data filter builder window,

1. Open the Data Extractor Process file that you want to update, select Home tab > Data Filter in the Settings section. The Data Filter Builder and Join Condition (<NameOfTables>) window appears.
2. In Field Name, select the name of the field that must be extracted.
3. In the Source Value column, select one of the following options:
   • Excel To SAP: Extracts the data for the Source Value column from the external Excel file. For example, consider the MARA table to extract the material details using the MATNR field. If you enter the source value as A1, then Process Runner extracts the data for that particular value from SAP.

     

     Runtime behavior

     

   • Fix Single Value: Extracts the data for the Source Value column you entered. or example, consider the MARA table to extract the data for material number, enter the fixed value as 100-100, and run the Process file. Process Runner extracts the data from SAP for that particular material number.

     

     Runtime behavior

     

   • System Value: Uses the system value selected in the System Values window. System values contain control information for the Process file that must be run. For example, consider MARA table to extract the data for material numbers that are created on the current date. Set Current System Date system value from the list and run the Process file. Process Runner extracts the data from SAP for the materials created on the current date.

     

     Runtime behavior

     

   • Excel Cell Value: Places the value received from SAP during the run into the Excel cell specified as the source value in the Data Filter Builder window. For example, if you enter source value as A50 and run the Process file, Process Runner extracts the data from SAP for this specific cell.

     

     Runtime behavior

     

   • Fix Multiple Values: Extracts the data for the multiple values entered in the Fix Multiple Value pop-up window. For example, consider the MARA table to extract the data for material numbers. If you enter the multiple values as 100-100, 100-200, 100-300 and run the Process file, Process Runner extracts the data from SAP for the values you have entered.

     

     Fix Multiple Value window

     

     Runtime behavior

     

   • Excel Row Range: Extracts the data for the Excel range entered in the Excel Range window. For example, enter the Excel Range as A to B and run the Process file. Process Runner extracts the data from SAP for the values given in columns A and B.

     

     If ACS is enabled, it handles the length of the where condition by splitting the where condition internally and keeping the length within the specified limit. The number of calls made to SAP are the number of slices made by ACS of the where condition. For information about ACS, see Automatic Condition Splitter.

     If you select Skip Blank value, Process Runner skips the row in which the field MATNR is blank.

     Runtime behavior

     

   • Fix Excel Range: Extracts the data for the Excel range provided in the Data Filter Builder window. For example, enter the Excel Range as A2 to A6 and run the Process file. Process Runner extracts the data from SAP for the values given in the range A2 to A6.

     

     If ACS is enabled, it handles the length of the where condition by splitting the where condition internally and keeping the length within the specified limit. The number of calls made to SAP are the number of slices made by ACS of the where condition. For information about ACS, see Automatic Condition Splitter.

     If you select Skip Blank value, Process Runner skips the row in which the field MATNR is blank.

     Runtime behavior

     

   • Start Bracket and End Bracket: Caters to the filtering conditions that simulate the where clause in SAP ABAP select statements with nested OR or AND. For example, consider the following SELECT statement:

     SELECT kschl FROM nast WHERE kappl = 'EF' AND ( kschl = 'NEU1' OR kschl = 'NEU2') AND spras = 'E' AND vstat = '1'

     

4. Select OK. The changes are saved.

Automatic Condition Splitter

This topic describes how to use the automatic condition splitter functionality for a Data Extractor Process file with a large where condition that might result in an issue if the length of the where condition exceeds the limit specified by the SAP database. You can use the Automatic Condition Splitter (ACS) functionality of Process Runner to split the where condition internally to ensure that the length is within the specified limit. ACS is designed especially to work with the SAP standard delivered function modules. The number of calls made to SAP are the number of slices made by ACS of the where condition. Note that no changes in SAP are required to use ACS.

Let us consider an Excel file with a list of 5000 material numbers extracted from the MARC table. To extract the description from the MAKT table for each material number, perform the following steps:

1. Create a new Process file for MAKT table.
2. On the Home tab, attach the Excel file containing the list of material numbers for which the description must be extracted.

   

3. On the Mapper tab, map the fields that must be downloaded from SAP.
4. On the Home tab, select Data Filter Builder option from the dropdown options. The Data Filter Builder window appears.

   

5. Select Range in the Compare Operator column and select Fix Excel Range in the Source Type column.

   

6. In the Excel Range window, enter the Excel cell range from which the data for the where condition must be extracted and sent to SAP, select the Activate Automatic Condition Splitter (ACS) option, enter the length of where condition in the text box, and select OK.

   

7. Add language filter if the description of specific language is required. In the example, description is filter for English language.

   

8. Select OK. The changes to the data filter builder are saved.
9. Select Run. The Excel file with the description of material number appears.

Join Condition

This topic describes how to extract data from multiple tables using a single Process file. You can add a new table to the existing table joins without recording the entire process again.

The Join Condition option is available only for Data Extractor technology and it appears in the Settings section only if the Process file contains at least two tables.

Process Runnersupports custom data extraction using an extended remote function module (RFM) that extends the Data Extractor technology allowing you to extract data from different tables or views. To create a join between tables for custom data extraction, configure the Data Extractor settings in the Tools > Options > Data Extractor tab and select Use Extended RFM. For more information, see Data Extractor.

To add a new table and create joins,

1. Open the Data Extractor Process file that you want to update, select Home tab > Tables in the Settings section. The Tables (<TableNames>) window appears.
2. On the Tables tab, select Add. The Add Table window appears. Perform the following steps:
   1. Enter the table name in Table Name. If you are entering multiple tables, separate the table names with a comma. For example, LTAK,LTBK.
   2. To automatically map all SAP fields to Excel columns, select Automap all fields.
   3. To retrieve the field descriptions from SAP in your logon language, select Get Descriptions.
   4. Select OK. The Connector for SAP window appears. Perform the following steps:
      1. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
      2. Select OK. The table is added to the list and Process Runner automatically creates joins between the tables based on the primary keys under the Join Condition tab.
   5. Optionally, on the Join Condition tab, edit the default join condition and select OK.
3. Save the Process file and select Run. The Excel file appears with the data from the three tables, LTAP, LTAK and LTBK.

   

For information about how to extract data from three tables using the dynamic table join condition functionality, see Extract Data From Three SAP Tables Using Dynamic Table Join Feature.

Export Data to Text File or Microsoft Access

This topic describes how to extract the contents of an SAP database table to a text file or Microsoft Access table without sending it to Microsoft Excel.

Note: The option Export To Text File/MS Access Settings is available only for Data Extractor technology.

Refer to the video to understand how to export data to a text file in Process Runner.

To export data to a text file,

1. Open the Data Extractor Process file whose data you want to export, select Home tab > Write to text file in the Settings section. The Export To Text File/MS Access Settings window appears.

   

2. Select Ignore Excel and write output to Text file/MS Access table. The Text File and MS Access options appear.
3. To export data to a text file, perform the following steps on the Text File tab:
   1. In the Text Output File, select the folder where you want to save the text file.
   2. Select the following options depending upon how you want to overwrite the records in the text file:
      • Fixed Width: Indicates that the records are separated with an equal width regardless of field contents.
      • Delimited: Indicates that a special character will be used to delimit each field of the record. You can choose from the given set of delimiters or enter a custom character as a delimiter.
      • Overwrite output file if already exists: Indicates that the exported data will overwrite the contents of an existing output file.
      • Append to output file if already exists: Indicates that the exported data will append to an existing output file.
      • Launch text file in notepad when extraction is finished: Indicates that the exported data is launched using a notepad.
      • Write a separate field layout file in same location: Indicates that you can create a text file in the same location that contains field information such as map value, mapping type, and so on.
      • Write output fields in same sequence as Excel mapping sequence in mapper: Indicates that the fields in the output file are written in the same order in which they are mapped in Mapper. For example, if MATNR is mapped as column B and DATEUV is mapped as column A, then the DATEUV be written as first field and MATRN as the second field.
      • Add field names to same file as a header: Indicates that you can choose to have two field names or field descriptions in the first row of the output file.
   3. For text transformation, select Perform following text transformation and select the following options:
      • Bring negative sign in front: Indicates that the (–) sign for negative numbers is moved to the beginning of the figure by default.
      • Change decimal sign as per current regional settings: Indicates that you can change the decimal signs according to your current regional settings.
      • Format SAP date fields as per regional settings: Indicates that you can change the date fields in the SAP system according to your current regional settings.
      • Format SAP time fields to HH:MM:SS: Indicates that you can change the time fields in the SAP system according to HH:MM:SS.
      • Skip and write overflow data to error file: Indicates that the overflow data (data starting with an asterisk) is not written into a text file. Such records are exported into a separate error log file.
      • Remove extra space(s) for each field: Indicates that the field values in the exported data are displayed without the trailing space(s).
4. To export data to a Microsoft Access table, perform the following steps on the MS Access tab:
   1. In the MS Access database, select the database into which you want to write the data.
   2. If the database is password-protected, enter the password and select Verify.
   3. Under Table Options, enter the following:
      • MS Access Table Name: Indicates the table name to which you want to send the data.
      • Action: You can select any one from four actions to consider while writing the data into it.
        • Stop execution if table exists (default): Indicates that the data is written to a table if it does not exist; else, the run is stopped after the text file is generated.
        • Overwrite existing table: Indicates that the table is created if it does not exists; else, all records are erased and new records are written.
        • Create a new table (timestamp) if exists: Indicates that the table is created if it does not exist; else, a new table is created with name you that you have selected followed by timestamp in yyyymmdd_hhmmss format.
        • Append data to the table: Indicates that the table is created if it does not exist; else, records the records are added to the table. The structure of the existing table must match with the new data columns to be written.
   4. Under Import Text Options, select the following:
      • Use Schema Method: Indicates that the data is imported without any import specifications. It is required that you have performed text transformation.
      • Use Transfer Text Method: Indicates that the data is imported using the import specifications selected by the user. It is required that you have performed text transformation.
5. Select OK. The changes are saved.

While exporting data from a .txt file into a Microsoft Access table, ensure the following:

• The space character must not be used as delimiter.
• Decimal character, date separator, time separator must not be used as custom delimiters.
• Maximum output text file name length must not exceed 63 characters.

Also, note the following:

• You can extract large data with this option as a text output, which is not constrained by Excel row limits.
• Process Runnerwrites to Excel quickly in Turbo mode (default). However, writing  to text is about 600% faster as compared to writing to an Excel. In our benchmark, we were able to extract half million records to text file in 4 minutes that took 25 minutes to write to Excel 2007. (SAP extract time was about only 1:20 minute in both the cases. SE16 attempts timed out with short dump).
• If you use the Delimited option, total output length is slightly reduced. (1 character X number of fields selected).

Tools

This section contains the following topics:

• SAP Shortcuts
• Generate Template
• Generate Excel Add-in Ready file

SAP Shortcuts

This section describes how to add a non-SAP GUI system to run process file without SAP GUI and how to create SAP logon shortcuts in Process Runner.

• Add non-SAP GUI System
• Add SAP Shortcuts

Add non-SAP GUI System

This topic describes how to add a non-SAP GUI system in Process Runner to run process file without using SAP GUI. Before you add a non-SAP GUI system, following are some of the restrictions when using a non-SAP GUI system:

• Recoding a new process file not supported.
• To apply data governance rule, you need to enter System ID and Instance number while adding a non-SAP GUI system.
• Update fields info is not supported.
• Launch SAP GUI is not supported.
• Generate Hyperlinks to open SAP GUI is not supported.
• F4 lookup is not supported.

To add a non-SAP GUI system,

1. In Process Runner, on the Home tab, select Tools> SAP Shortcuts. The Connector for SAP window appears.
2. On the Server/Group tab, select Add Server. The SAP System window appears.

   

3. Enter the following SAP connection details:
   • Name: Enter a name for the SAP system.
   • Protocol: Select either http or https from the drop-down list.
   • Host: Enter the IP Address.
   • Port: Enter the port details
4. Select the OData or SOAP radio button to choose the connection type.
   • If you select OData, the Base URL pre-populates.
   • If you select SOAP, enter the following:
     • Base URL: Enter the base URL for the Financial Accounting (FI) module connection.
     • TCode: Enter the transaction code. To enter multiple transaction codes, use commas. for example: FB50, FB01.
       

       Note: Process Runner currently supports the FB50, FB60, and FB70 transaction codes.

5. System ID: Optionally, enter the system ID of the server.
6. Instance Number: Optionally, enter the instance number of the server.

   Note: To apply data governance rules, you should enter the System ID and Instance Number.

7. Select OK. The non-SAP GUI system is added. In the Connector for SAP window, check the OData Enabled or Soap Enabled column to verify the status of the newly added system.
8. If the newly added system is not appear in the Connector for SAP window, select Refresh to update the list.

Add SAP Shortcuts

This topic describes how to create SAP logon shortcuts in Process Runner. The logon shortcut enables you to bypass manual SAP logon prompt; instead, Process Runner uses the information stored in the logon shortcut file.

To configure SAP logon shortcut,

1. In Process Runner, on the Home tab, select Tools> SAP Shortcuts. The Connector for SAP window appears.
2. On the Logon Shorcut tab, select Create. The Logon Shortcut window appears.
3. Enter the required information for the logon shortcut and select Test.

   

4. If the authentication details are correct, select Save. By default, the shortcut file is saved in the \\MyDocuments\Innowera\iLogonFiles path and is displayed in the list of logon shortcuts.

Generate Template

This topic describes how to generate a template of the Process file that can be used with other users who have Process Runner Excel Add-in; the users do not have to install Process Runner on their computers.

Note: Users having Process Runner designer license can generate Process Runner Excel Add-in file and users with Process Runner run-only license cannot generate or save the Process file. Also, multiple Process files can be connected in Process Runner and run in Process Runner Excel Add-in.

To generate template,

1. Open the Process file for which you want to generate the template and select Home > Generate Template. The Generate Excel Template window appears.
2. In the Generate Excel Template window, enter the following information:
   • Create New Worksheet: Creates a new worksheet in the existing workbook and generate the template.
   • Existing Worksheet: Creates the template in the worksheet that you select in the dropdown list. You can either insert the rows or overwrite the existing data.
   • Header Line: Configures the header line settings as follows:
     • Technical Field Name: Allows Process Runner to retrieve the Technical Field Name at the header of the columns from SAP.
     • Field Description: Allows Process Runner to retrieve the Field Description Name at the header of the columns from SAP.
     • Both: Allows Process Runner to retrieve both Technical Field Name and Field Description at the header of the column from SAP.
3. Select Insert sample data from recording. The sample data that was entered during the recording of the Process file is inserted in the template file.
4. Select Insert "Run with Process Runner" button to worksheet. A Run with Process Runner button is added to the worksheet.
5. Select OK. The template is created and is opened in Excel.
6. To run the file, select Run and enter the valid SAP logon credentials.

Generate Excel Add-in Ready file

This topic describes how you can share the Excel Add-in Ready file generated in Process Runner with other users who can run the file in Process Runner Excel Add-in; the users do not have to install Process Runner on their computers.

Note: User having Process Runner designer license can generate Excel Add-in file and users having Process Runner run-only license cannot generate or save the Process file in Process Runner Excel Add-in.

Refer to the video to understand how to generate Excel Add-In Ready file in Process Runner.

To generate Excel add-in ready file,

1. Open the Process file for which you want to generate the Excel Add-in Ready file and select Save as Excel Add-in Ready File... option. The Generate Excel Add-in Ready file window appears.
2. Select the Process file and select Generate.

   

3. Save the Excel file with .xlsx extension and select OK.
4. Close Process Runner.
5. To run the file in Process Runner, perform the following steps:
   1. Open Excel and from the Process Runner tab, open the saved Excel file.
   2. Click Run and enter the valid SAP logon credentials.

You can also connect multiple Process files in Process Runner and run in Process Runner Excel Add-in.

View

This section contains the following topics:

• Show/Hide Side Panel
• Process Connection
• Stat
• Log

Show/Hide Side Panel

This topic describes how to enable the visibility of the side panel in Process Runner. You can monitor the process, status, and progress of the Process file and the connected processes, if any. By default, the visibility of the side panel is in the hide mode.

To enable the visibility of the side panel,

1. Open the Process file.
2. Select Show/Hide Side Panel in the View section on the Home tab. The side panel appears.
3. To rename the name of the parent process in a connected Process file, perform the following steps:
   1. Right-click the Process file and select Change.The Change Process Name [<NameOfTechnology>] window appears.
   2. Rename the Process file and select OK. The updated Process file is displayed in the side panel.

Process Connection

This topic describes how to use the Process Connection functionality to join multiple Process files and run them as a single-chain of Process files or a connected Process file. You can connect more than one Process file and it can be Transaction, BAPI/RFM, GUI Scripting, or Data Extractor. You can select the Process file either from a local machine or from the EShare server.

Consider a scenario in which the data set contains a list of material numbers and other fields for which you want to download data from SAP. If more than one Process file must be used to download the material data for all the fields, you can connect the required Process files and download the data from SAP using Process Connection. To build and run a chain of Process files, you first have to select a master Process file, append the required number of child Process files to the master Process file, and then run the connected Process files.

Refer to the video for information about Process Connection in Process Runner.

To run multiple Process files using Process Connection,

1. In Process Runner, open the Process file in which you want to connect other Process files and select the external Excel file that is mapped.

   

2. Select Process Connection. The Process Connection section appears.

   

3. Under Process Connection, select one of the following options:
   • Local: Indicates that you want to select a Process file from the local computer.

   • EShare: Indicates that you want to select the Process file from the EShare Server.
     

     1. If you have selected Local, browse to the location and select a Process file to append it to the master file.
     2. If you have selected EShare, browse to the EShare server and select a Process file to append it to the master file. Alternatively, you can enter the EShare ID of the Process file.
4. Alternatively, you can use the drag-and-drop functionality to select a Process file and append it to the master Process file.

   

5. Under Use following Excel settings for ALL downstream connections, select one or more of the following master Process file settings that must be applied to all the appended Process files during the run or clear the selection if the settings configured in the respective appended Process files must be used during the run.
   • Current Excel
   • Current Sheet
   • Current start row value
   • Current end row value
6. Under Use following SAP logon settings for ALL downstream connections, select one or more of the following options:
   • Current Logon/Shortcut information
   • Current "Launch SAP GUI" information
7. Select Stop further processing on first error in any of the connected file to stop the processing when the first error is encountered. Clear the selection if you want to continue the process even if one of the connected Process files has an error.
8. Select Re-open current file after run process is finished. The master Process file is displayed after all the Process files are run.
9. Select File > Save > Run. The SAP Logon at <SAP System> window appears.
10. Enter the login credentials, and select OK. The MARA Process file downloads the material data for all the fields and chained Process file downloads the Material Description.

Stat

This topic describes how to view and configure stat details in Process Runner. The stat feature records all data related to each run performed from Process Runner in a single row.

To configure stat details,

1. Select Home > Stat. The Stat Detail window appears. To open an existing stat file, perform the following steps:
   1. Select the Stat1.xml file that must be opened and select Open Process File. The Open Process Runner File dialog box appears.

      

   2. Select Yes. The selected file opens.

   Note: The stat file that is to be loaded should be necessarily renamed as Stat1.xml.

2. To update the background changes that took place after opening the Stat Detail window, select Refresh. The stat list changes are appended to the grid in the Stat Detail window.
3. To save an existing stat file and initiate the session for a new stat file, select the New File option. The existing stat file is saved with an auto-generated name in the default Stats folder. The saved stat file name is displayed in the grid of the Stat Detail window.
4. To modify the grid view based on the available filter options, select one of the sub-options under Filter option. The records are displayed as per the selected date range. The sub-options are as follows:
   • All: Displays all the records.
   • Today: Displays the records for the current day.
   • Yesterday: Displays the records for the previous day.
   • Last 2 Days: Displays the records for the last two days.
   • Last 10 Days: Displays the records for the last 10 days.
   • Last 20 Days: Displays the records for the last 20 days.
   • Last 30 Days: Displays the records for the last 30 days.
   • Custom: Displays the Custom Date window. Select date from From Date and To Date options and select OK. The records are displayed as per the customized date range.
5. To open an Excel file from the Stat Detail window, perform the following steps:
   1. Filter Excel File Name from the filter list of Type column header. All the Excel files are listed.
   2. Select the required stat record with the Excel file path in message column and select Open Excel. The Excel file is opened only if it exists at the mentioned path.
6. To open a Process file from the Stat Detail window, perform the following steps:
   1. Filter Process Name from the filter list of Type column header. All the Process files are listed.
   2. Select the required log record with the Process file path in message column and select Open Process File. The Process file is opened only if it exists at the mentioned path.
7. To upload the stats to the configured Dashboard server, perform the following steps:
   1. Select Upload. The Upload to Dashboard Server window is displayed.
   2. To upload just the new records, select Upload New Records Only > Upload Now. The previous records are not uploaded.
   3. Optionally, cancel selection for Upload New Records Only and select Upload Now. All the stat records are uploaded to the Dashboard Server and a success message is displayed.
8. To modify the grid layout, perform the following steps:
   1. Select Customization. The Customization window is displayed.
   2. Drag the column headers available in the Customization window to the grid header. The details are grouped under the added header.
   3. Optionally, drag the columns already present in the grid to the Customization window. The columns are deleted from the grid. Therefore, the Customization window serves as a storage of columns that can be used to customize the grid layout view.
9. Select Print. A print preview of the existing stats is displayed.

   Note: You can configure the print settings by using the available options.

10. To export the stats to an Excel (.xls or .xlsx) or a Text (.txt) file format to your local drive, select Export. A dropdown list is displayed.
    1.  Select one of the following options:
    • Export to XLS
    • Export to XLSX
    • Export to Text
    2. Browse to the folder in the local drive and select Save. The stat file is exported in the selected format.

Log

This topic describes how to view the logs in Process Runner. The logs record each activity from the start to the end of a session in Process Runner.

To configure log details,

1. Select Home > Log. The Log Detail window appears. To open an existing log file, perform the following steps:
   1. Select the Log1.xml file that must be opened and then select Open Process File. The Open Process Runner File dialog box appears.
   2. Select Open. The selected file opens.

      

   Note: The log file that is to be loaded should be necessarily renamed as Log1.xml.

2. To update the background changes that took place after opening the Log Detail window, select Refresh. The log list changes are appended to the grid in the Log Detail window.
3. To save an existing log file and initiate the session for a new log file, select the New File option. The existing log file is saved with an auto-generated name in the default Stats folder. The saved log file name is displayed in the grid of the Log Detail window.
4. To modify the grid view based on the available filter options, select one of the sub-options under Filter option. The records are displayed as per the selected date range. The sub-options are as follows:
   • All: Displays all the records.
   • Today: Displays the records for the current day.
   • Yesterday: Displays the records for the previous day.
   • Last 2 Days: Displays the records for the last two days.
   • Last 10 Days: Displays the records for the last 10 days.
   • Last 20 Days: Displays the records for the last 20 days.
   • Last 30 Days: Displays the records for the last 30 days.
   • Custom: Displays the Custom Date window. Select date from From Date and To Date options and select OK. The records are displayed as per the customized date range.
5. To open an Excel file from the Log Detail window, perform the following steps:
   1. Filter Excel File Name from the filter list of Type column header. All the Excel files are listed.
   2. Select the required log record with the Excel file path in message column and select Open Excel. The Excel file is opened only if it exists at the mentioned path.
6. To open a Process file from the Log Detail window, perform the following steps:
   1. Filter Process Name from the filter list of Type column header. All the Process files are listed.
   2. Select the required log record with the Process file path in message column and click on Open Process File. The Process file is opened only if it exists at the mentioned path.
7. To upload the logs to Dashboard server that is configured in the Tools > Options > Enterprise Settings > Dashboard tab, perform the following steps:

   Note: If you have selected Process Runner Cloud in the Connection Type under the Tools > Options > Enterprise Settings > Dashboard tab, you cannot upload the logs manually. Select OK to close the Error while uploading dialog.

   1. Select Upload. The Upload to Dashboard Server window appears.
   2. To upload just the new records, select Upload New Records Only > Upload Now. The previous records are not uploaded.
   3. Optionally, deselect Upload New Records Only and select Upload Now. All the log records are uploaded to the Dashboard Server and a success message is displayed.
8. To modify the grid layout, perform the following steps:
   1. Select Customization. The Customization window is displayed.
   2. Drag the column headers available in the Customization window to the grid header. The details are grouped under the added header.
   3. Optionally, drag the columns already present in the grid to the Customization window. The columns are deleted from the grid. The Customization window serves as a storage of columns that can be used to customize the grid layout view.
9. Select Print. A print preview of the existing logs is displayed.

   Note: You can configure the print settings by using the available options.

10. To export the logs to an Excel file format (.xls or .xlsx) or a Text (.txt) file format to your local drive, select Export. A dropdown list is displayed.
    1.  Select one of the following options:
    • Export to XLS
    • Export to XLSX
    • Export to Text
    2. Browse to the folder in the local drive and select Save. The log file is exported in the selected format.