Skip to main content

Edit tab of Process Runner DB

This section provides guidelines about the groups of Edit tab. The Edit tab in Process Runner DB contains the options related to Run Action, Lock File option, Scripts and Delays options and others.

This section contains the following topics:

Only for a Transaction Process file, you can use the options in the Run Options section to include the Error Processing Run or Test Run options that can be used by a run-only user. Also, only for FB01 and FBV1 transactions, you can also use the Data Validation options.

Run Actions

This topic describes how to use the options in the Edit > Run Actions section to run the file. 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.

Lock File

This topic describes how to use the options in the Lock Settings window to prevent users from making changes to a specific Process file.

Refer to the video to understand how Process Runner DB implements File Locking and Password Protection.

To configure the lock settings,

  1. In Process Runner DB, open the Process file that you want to update.
  2. Go to the Edit tab and select Lock Option > Lock File. The Lock Settings window appears.

  3. In the Lock Basic Operations section, perform the following steps:
    • To ensure that a specific run type cannot be run, in User cannot perform following function, select Run, Test Run, Debug Run, Error Processing Run, Data Governance, and Data Validation depending on your requirements. The Data Validation option is displayed only for Transaction Process files.

      When you run this file and disable the run option, the This operation is disabled error message window appears.

    • To ensure that the password is entered when saving and opening the file, select User cannot Save the file without valid password and User cannot Open the file without valid password; these options are valid only if password-protection is enabled for the Process file as described in step 5.
    • To ensure that the users cannot change the data of iTable, select User cannot change iTable. However, the data can be used to run the Process File. This functionality is often useful when users needs to restrict the changes in the iTable from other user.
    • To ensure that the Mapper is not displayed in the Mapper tab on the Home or Edit tabs when you open the Process file, select User cannot change Mapper.
    • To ensure that schedules cannot be added, edited, or deleted, select User cannot change Scheduler Settings.
  4. In the Lock Advanced Operations section, select the following options:
    • User cannot change Control Parameters: Indicates that the options in the Control Parameter tab in the Logon and Control Parameters window on the Home tab are disabled.
    • User cannot change Logon & Performance settings: Indicates that the options in the Logon and Performance tab in the Logon and Control Parameters window on the Home tab are disabled.
    • User cannot change Start and Delays settings: Indicates that the Start and Delays settings under Advanced tab is disabled.
    • User cannot change Process Connection settings: Indicates that the options in the Process Connection section under Home or Edit tabs are disabled.
  5. To configure a password that must be entered when opening or saving the Process file, perform the following steps in the Add password protection section:
    1. Enter the password, confirm the password, and enter a password hint.
    2. To enter the contact details of the person who can be contacted when the password validation fails, enter the information in the Display this contact information when password validation fails box.

      3. Note: When you enter a password but do not select either User cannot Save the file without valid password or User cannot Open the file without valid password, Process Runner DB asks for a password if you have selected Lock File.

  6. Select OK.The details are updated.

Custom Script and Delays Options

This section contains information about how to configure Process Runner DB to run before or after the run of other programs or scripts.

Process Runner DB allows you to extend its capabilities with external processes using the pre and post-run functionality.

The externally called processes can also receive parameters from Process Runner DB that can be utilized to run its own logic. The called processes can also communicate with Process Runner DB at the end to provide end-to-end integration.

You can also store scripts written in VBScript or JavaScript internally with the Process file using the iScript option.

Some of the examples where you can use pre-run or post-run external processes are as follows:

  • Send automatic email or SMS text message at the end of the each run with status of the run and error count.
  • Look at a mount application server, Unix mount point and move the file(s) to appropriate location before or after each run.
  • Run a macro to calculate, summarize or perform formatting of external data before each run.
  • Downloaded data or report to proprietary software or call third-party importer routine.
  • Trigger another application before or after the run.

Using pre-run and post-run with dynamic skips and dynamic formulas, you can create cross-platform and flexible automation solutions.

The section contains the following topics:

Pre/Post Script

This topic describes how to configure the Pre Script or Post Script options to run an internal script or external file before running the Process file. You can configure both the pre-run and post-run settings at the same time. The external file can be a standard executable file, batch file, a VB Script, JavaScript, or Visual Basic file.

To configure pre-run or post-run script options,

  1. Open the Process file for which you want to include the pre-run or post-run script, select Edit tab, and then one of the following options:
    • Pre Script: Indicates that the script is run before the Process file run.
    • Post Script: Indicates that the script is run after the Process file run.
  2. Select Pre Script or Post Script. The Pre-Run/Post-Run Process Settings window is displayed. Perform the following steps:
    1. On the Pre-Run iScript tab, select Pre-Run Process or on the Post-Run iScript tab, select Post-Run Process and select one of the following options from the dropdown list:
      • Internal Script: Allows you to enter a script written in VB Script, JavaScript, or VB.Net in the Internal Script editor box. Optionally, select Insert Sample Code to use one of the sample scripts provided.

        Note: For VB.Net, you can also select from the predefined libraries depending on your requirement. For example, select Easy Workflow Library to download an EShare file or start a workflow using the Download EShare File or Start Workflow functions. This library is not supported when EShare is configured using the EShare Service URL.

      • External File: Allows you to select an external .exe, .bat, .vbs, or .js file that is on your computer. Optionally, right-click in the parameters text box to view the list of predefined parameters that you can use in the selected external file and ensure that you separate each parameter with a comma.
      • Stored Procedure: Indicates a set of multiple SQL queries. Stored Procedure is already stored in the database and you can also create a new Stored Procedure.

      Predefined parameters

      Variable name

      Description

      #CURPRTYPE#

       

      Displays the type of the current Process file.

      • TX for Transaction
      • BA for BAPI/RFM
      • GS for GUI Scripting
      • DE for Data Extractor

      #CURPROC#

      Displays the name of the process, table, or BAPI used in the current Process file.

      Example: MM02, MARC, BAPI_CREATE_CONTRACT

      #CURPRFILE#

       

      Displays the full path of the current Process file.

      Example:C:\Innowera\MRRC.ite

      #CURSAPSYS#

      Displays the name of the SAP system used to run the current Process file.

      Example:PR1, DEV, QAS

      #SAPUSR#

      Displays the SAP user name used to log onto the SAP system.

      Example: JSMITH

      #SAPLAN#

      Displays the language of the interface of the SAP system.

      Example: EN, FR, DE

      #SAPCLIENT#

      Displays the client number used to log onto the SAP system.

      Example: 101, 800

      #SAPSYSTEMNO#

      Displays the system number used of the SAP system.

      Example: 00, 01

      #NOOFREC#

      Displays the number of records extracted from SAP. This option is available only for Data Extractor.

      Example: 20000

      #NOOFCALL#

      Number of finished calls after a process completed. This option is available only for Transaction.

      Example: 550

      #RUNTYPE#

      Displays the run type. This option is available only for Transaction.

      • 1 for Run
      • 2 for Test Run
      • 3 for Error Processing Run
      • 4 for Debug Run

      #ERRORCOUNT#

      Displays the number of errors. This option is available only for Transaction.

      #ERRORSTAT#

      Displays the status of the current task; 1 if an error occurs and 0 if the task is run successfully.

      #ERRORMSG#

      Displays the error message if the #ERRORSTAT# returns 1.

      Example:

      Specify account number.

      SAP Front end Server: The method got an invalid argument.

      #ISMASTERPROCESS#

      Displays whether the Process file is master file; 1 if it is the master process and 0 if it is not.
    2. In the Process Settings section, select the following options that determine what must be done when an external file is busy or closed:
      • Wait options:
        • 1-No Wait: Indicates that the Process file does not wait for external file if the file is busy or closed.
        • 2-Wait until terminated: Indicates that the Process will waits until the external file gets terminated.
        • 3-Wait until second: Indicates that the Process file waits for specified seconds.
      • Stop on error: Indicates that the Process file stops if the external file or internal script throws an error.
      • Run with normal Run: Indicates that the external file or internal script runs only when you perform a normal run. This option is displayed only for Transaction, BAPI/RFM, and GUI Scripting Process files.
      • Run with Test Run: Indicates that the external file or internal script runs only when you perform a test run. This option is displayed only for Transaction Process file.
      • Run with Debug: Indicates that the external file or internal script runs only when you perform a debug run. This option is displayed only for Transaction and GUI Scripting Process files.
      • Run with Error Processing: Indicates that the external file or internal script runs only when you perform an error processing run. This option is valid displayed for Transaction and BAPI/RFM Process files.
    3. Select OK. The updates are saved.

Start and Delays

This topic describes how to configure the options in the Custom Script and Delays Options window that affects the behavioral characteristics of the post, pre, and ongoing run.

Refer to the video to understand how Process Runner DB implements starts and delays.

To configure start and delay options,

  1. Open the Process file for which you want to configure the start and delay options and click the pop-up icon. The Custom Scripts and Delays Options window is displayed.

  2. In File Option, select the following options:
    • Run on open: Indicates that Process Runner DB runs this file as soon as it is opened.
    • Exit after run: Indicates that Process Runner DB exits automatically as soon as the run is concluded. This option is usually used in cases of periodic scheduled execution.
    • Stop further Processing on first error: Indicates that Process Runner DB stops further processing as soon as the first error is encountered.
  3. In Delay Option, select the following options:
    • Delay before start: Indicates the time duration for which Process Runner DB waits before the run command is applied. You can use this option to implement the run of scheduled processes.
    • Delay between calls: Indicates the time duration for which Process Runner DB must wait between the run of each call or the time interval between two calls. If you select this option, Process Runner DB becomes slow.
    • Delay between lines: [Available only for GUI Scripting] Indicates the time interval that is applicable between the run of each line.
  4. In Other Option, select the following options:
    • Last RunId: Select the last RunId from counter dialogue box.
    • Character Set: Choose appropriate character set.
    • Downloaded File post processing:
      • 0-No Action: Indicates that no action is taken once the file processing is completed.
      • 1-Open and Save as Excel: Indicates that the file is opened and saved as Excel once the file processing is completed.
  5. Select Ok.

Was this article helpful?

We're sorry to hear that.