Skip to main content

Home tab of Process Runner DB

The Home tab displays and allows you to maintain information about the file you are working on. It contains the commands related to file operations, file actions, tools, view and more.

This section contains the following topics:

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:

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, Mapper or iTable tabs.

To run a Process file,

  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. For a Transaction, BAPI/RFM, or Data Extractor Process file, perform the following steps:
    1. 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 EP/SSO.

    2. Select OK. The Transaction, BAPI/RFM, or Data Extractor Process file is run.
  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.
    2. 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.
    3. If you select an existing GUI Session, the run of the GUI Scripting Process file starts immediately in the selected SAP GUI session.

    4. Select OK. The GUI Scripting Process file is run.

Debug-All Screens

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, Mapper, or iTable 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 first field of the table where Process Runner DB initiates the run on the database.
      • End debug row: Sets the last field of database where Process Runner DB stops the run on database.
      • 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.

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, Mapper or iTable 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 at the iTable or External Database whichever is selected in the settings.

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.
  3. Select OK. The Process Runner 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 is started.

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 dialogue box 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 DB, and others, to display only the specific kind of messages. P-Process Runner DB 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 at iTable or external Database.
    • 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.

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, Mapper or iTable tabs.

Note: The Error Processing option is applicable only for Transaction technology.

To use the error processing option,

  1. Open the Transaction Process file.
  2. Select Error Processing Run in the Run Actions section on the Home tab. The Error Processing Options window is displayed.
  3. For a Transaction, perform the following steps:

    1. 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 EP/SSO.

  4. Select OK. The error processing run of the Process file is displayed.

Debug-Go to Error

This section describes how to debug the error directly in the SAP GUI and troubleshoot it. When the error is displayed, the SAP GUI is launched directly at the point where the error has occurred. You can perform a debug run from the Home, Edit, Mapper, or iTable tabs.

Note: The Debug-Go to Error option is applicable only for Transaction technology.

To use the debug run option,

  1. Open a Transaction or a GUI Scripting Process file.
  2. Select Debug-Go to Error 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.

Data Governance

To know about data governance feature of Process Runner DB, see Data Governance.

Stop

You can use the Stop option to stop the Process file run using Stop in the Run Actions section on the Home, Edit, Mapper, or iTable 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:

For information about how to configure the logon and performance parameters, Logon and Control 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:
    1. In the Run Option section:
      • Select Stop Transaction on COMMIT and run in BI mode if you want Process Runner DB 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.
    2. In the Other Option section:
      • 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.
    3. In the "Copy from SAP to DS" Option section:
      • Select Suppress all "Copy from SAP to DS" mappings to suppress the copy of data from SAP to iTable/Database. This functionality is used in case if the user requires to restrict the entry of download data in DS
      • Select Stop transaction on COMMIT and run in BI mode for Process Runner DB to stop the transaction at COMMIT statement and run the transaction in batch input mode for "Copy from SAP to DS".
  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, select the pop-up icon. The Logon and Control Parameters window appears.

  3. Depending on your requirement, perform the following steps:
    • If Process Runner DB 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 DB 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 DB 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 DB does not wait for the completion of current execution and instead run the BAPI_TRANSACTION_COMMIT first.
    • 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 pop-up icon. The Logon and Control Parameters window appears.

  3. 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.
  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 pop up icon. The Logon and Control Parameters window appears.

  3. Select Logon and Performance.
    • 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 DB from logging off SAP after transactions and BAPI calls are run, select Do not close SAP Connection after each run.
    • 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.

Important: The Dashboard option is displayed on the Home tab only if you have selected Enable Dashboard in the 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.
  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.

    inwdashboardstat

Tools

This section has the SAP Shortcuts features explained below:

SAP Shortcuts

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

To configure SAP logon shortcut,

  1. In Process Runner DB, on the Home tab, in the Tools section, select 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 in the Connector for SAP window.

Settings

This section contains the following topics:

Message

This topic describes how to configure the SAP message settings.

Note: The Message option appears 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 > Settings > Message. The SAP returned messages setting window appears with the following tabs:
    • Basic Settings
    • Message Text Transformation
    • Return Value(s) Mapping
  2. To configure the display messages, go to Basic Setting 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 DS. All other SAP-returned messages are avoided.
      • 2-Display only last: Displays only the last message that is returned from SAP to DS14569. 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 sub options you select. For example, select P-Process Runner DB to display all the messages related to Process Runner DB. 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 Table column checkbox. The return value mapping settings are enabled.
    1. To configure a column with a field, select the Select Column for Value <X> option, and then select the Field <X> from the list. As per your settings, the transaction message appears.
    2. Select OK. The message variable values are displayed in the selected and table mapped column.  

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

Advanced

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

This section contains the following topics:

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. To configure the Auto fix settings for updating rules during runtime, select the following options:
    • 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 sub-options:
      • Retry Count: 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.
  3. 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.

    • Convert all blank or zero values to null: Auto-trims the blank/zero values and assigns them to a null value state.

    • Continue on constrain violation and write to log: Select this field if suggested by Innowera Support Team.

    • Convert all data to UPPER: Downloads the data from SAP and converts it to UPPER case.

    • Delete XML Data before run (iTable): Deletes the existing data of the iTable before every run (execution).

    • Allow less than 1753 Year in "datetime2" datatype Field: Allows 'datetime' datatype field to precede A.D. 1753 year of the calendar. Usually this is not allowed in the SAP until it is opted to. Users can directly alter the settings from here.

    • Insert iTimeStamp field value in "UTC" datetime format: Inserts the Date and Time (of data extraction) at the iTimeStamp field in UTC datetime format.

    • Remove extra space(s) from value: Eliminates any extra space(s) from the value.

    • 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 Process Runner 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.
  3. Select OK. The changes are saved.

Data Filter

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

Note: 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, go to 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 from the drop-down list. The Data Filter Builderwindow appears. Perform the following steps:
    1. In Field Name, select the name of the field that must be extracted.

    2. Select the appropriate option from the Compare Operator column.

    3. In the Source Type drop-down field, select the source type as per requirement.

    4. In the Source Value field, enter the desired source value/String pattern. This looks for the material numbers starting with the specified source value/string pattern.

    5. Add values in the other columns, such as Dynamic Skip, Dynamic Formula and others.

    6. To add, delete, go to next, or go to previous rows, use the options in the lower-left of the window.
    7. 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. Save the Process file and select Run to download the selected data from SAP system to iTable.

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

Activate ATS

This topic describes how to configure the ATS settings. Automatic Table Splitter (ATS) allows configurable slicing of tables into multiple parts resulting in improved performance for large table extraction with slicing on the indexed key fields. Sliced table parts are extracted internally as individual requests but appended to the one output table or a text file. ATS is designed to improve performance of large extracts, works with SAP standard delivered function modules and does not require any adapter or ABAP installation.

To activate ATS settings,

  1. Open the Data Extractor Process file that you want to update.
  2. Select Home tab > Activate ATS in the Settings section. The ATS window appears.

  3. Select Active ATS check-box.

View

This section contains the following topics:

Show/Hide Side Panel

This topic describes how to enable the visibility of the side panel in Process Runner DB. 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.

Stat

This topic describes how to view and configure stat details in Process Runner DB.

To configure stat details,

  1. Select Home > Stat. The Stat Detail window appears.

  2. 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 is displayed.
    2. Select Yes. The selected file is opened.

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

  3. 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.
  4. 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.
  5. 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.
  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 appears.
    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 DB. The logs record each activity from the start to the exit of a session in Process Runner DB.

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 select Open Process File. The Open Process Runner File dialog box is displayed.
    2. Select Yes. The selected file is opened.

    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 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.
  6. To upload the logs to Dashboard server that is configured in the Tools > Options > Enterprise Settings > Dashboard tab, 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, deselect Upload New Records Onlyand select Upload Now. All the log records are uploaded to the Dashboard Server and a success message is displayed.
  7. 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.
  8. Select Print. A print preview of the existing logs is displayed.

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

  9. To export the logs 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 log file is exported in the selected format.

Manage Data Source

This topic describes how to obtain the connectivity with major databases. It allows you to upload and download data from connected database table to SAP.

Manage Data Source supports following databases/database connections:

  • Oracle
  • SQL Server
  • MYSQL
  • MS Access
  • SAP HANA
  • ODBC
  • OLED

Note: You require client side prerequisites to connect to some databases like Oracle, MySQL.

To manage data source,

  1. Open the Process file.
  2. Select Manage Data Source in the View section on the Home tab. The Data Source Configuration dialog box is displayed to configure the data source settings.

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 DB. In this case we will create a Chain Process where a master process file will have two chained processes- one from local machine and one from EShare.

To run multiple Process files using Process Connection,

  1. Open the Process file in which you want to connect other Process files and activate the visibility of side panel.
  2. Select Process Connection. The Process Connection section appears below the Database section.

  3. In the Process Connection section, 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. Select Current Logon/Shortcut information in all the downstream processes.

  6. Unselect Stop all downstream processing if current process has zero record to connect downstream process to execute even if current process has zero records.

  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 Allow Run-Only user to make changes to allow Run-Only user to make the changes in this particular process file.
  10. From the side panel, open the second file that is chained to the master file through a double-click.
  11. Activate the visibility of side panel and process connection in the opened process file and select the EShare.
  12. Enter the EShare ID of the file in the field after activating the EShare checkbox at Process Connection configuration.

  13. Save the chain process file.

Was this article helpful?

We're sorry to hear that.