Liquid UI - WS Reference Library

4.1 Running Scripts

Once a script file is generated, it can be run in Liquid UI WS. However, there are certain actions that must first be executed. In the following sections, we will demonstrate how to run a script generated from each template. The included topics are as follows:

  • Generating Scripts
  • Running Standard Scripts
  • Running Excel Scripts
  • Running PDF Scripts
  • Running Offline Synchronization Scripts
  • Running Offline UI Scripts
  • Running Access Scripts

Generating Scripts

Once a screen is recorded, it is saved as a .GVL file in the Workbench directory. From this file, it is necessary to generate a script file. As auto-mapping will already have been performed, please do the following to generate a script.

  1. In the Workbench, there are six template buttons for the pre-fabricated templates shipped with Workbench located on the left side of the interface directly below the Record button, as shown below. There is also a Custom button, which can be used for any user-created templates as was explained in the Adding Templates section:

  2. Click the icon for your desired template to generate scripts. The available templates are as shown in the above example.

  3. If you choose the Excel or PDF template, a dialog box will open, asking you to select a name for the Excel spreadsheet or PDF form that will be created. The dialog for Excel is shown below:

  4. Once the Excel spreadsheet or PDF form is created, a script will be generated and the progress will be tracked in the Output area immediately below the actual GVL file, as shown below:

  5. For all templates other than PDF and Excel, no dialog appears and the script is generated immediately. If the user is logged into SAP, the generated scripts will be stored in the designated script directory. If the user is not logged into SAP, then the generated scripts will be stored in the Workbench directory. Once the script is generated, go to the correct directory and locate the generated script file. The generated file will be named 'TCODE_template_name.sjs'. So if the recorded transaction was 'VA01', the resulting script files will be named as follows:

    • VA01_standard.sjs
    • VA01_excel.sjs
    • VA01_pdf.sjs
    • VA01_offline_synchronization.sjs
    • VA01_offline_ui.sjs
    • VA01_access.sjs

    The designated script directory with two generated scripts is shown below:

  6. Once a script is generated it must be named correctly for the transaction that is to be run. For all scripts except the Offline UI scripts, the name must be the same as the dynpro name of the screen where the script will originate. So if you recorded a VA01 transaction, then the script will be named 'SAPMV45A.E0101.sjs'. This will be explained more fully in the following sections on running the various generated scripts. Please note that the Offline UI scripts are different and will be covered in the Offline section.