Validate before the run - Automate_Studio - Latest

Automate Studio with Studio Administrator User Guide

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio
Version
Latest
Language
English
Product name
Automate Studio
Title
Automate Studio with Studio Administrator User Guide
Copyright
2024
First publish date
2018
Last updated
2024-07-22
Published on
2024-07-22T13:07:07.564657

To ensure that anyone who runs your script first validates the data in the data file before posting it, you can turn on validation.

For transactions, GUI for HTML, and the Easy Access menu, use the SAP profile date formatting matching the user's set format (example - dd.MM.yyyy).

Validate

When data validation is turned on, you do not need a separate validation sheet.

Turn on data validation

  • On the Map tab, click Allow Validation.
  • Studio automatically adds the Validate Log field to the Mapper and maps it to the data file.

Validate the data against the script's rules

Click Check Data to check that the data meets all the script's requirements for required fields and allowed values. You do not need to be logged on to SAP.

Validate the data against SAP

Errors are returned against the entire document, and the results are written back to the Header cell.

You must be logged on to SAP. You can log on from the lower left area of the status bar on the Run tab.

Next, validate the line items against SAP.

  1. On the Run tab, click Validate.
  2. Correct any errors or make changes.
  3. Click Run to upload the data.

Studio gives you additional validation options. Click the arrow below the Validate button to do any of the following:

  • Validate Specified Range
  • Validate First 5 Transactions
  • Validate Only Error Rows
  • Validate Only Unprocessed Rows
  • Validate Error Rows and Unprocessed Rows
    Note: When you click Validate Only Unprocessed Rows, the setting can be changed only by the script developer. Runners cannot change this setting.
    When recording a script on the ECC6 Server - SAP GUI for HTML, the Transaction Code script property may intermittently fail to capture data. As a result, only the first record runs successfully, while subsequent records log "No message received from SAP" and fail to update data in SAP. To resolve this issue, manually enter data in the Transaction Code field property or provide the App ID while recording the script.

    When running a script on an SAP server different from the one where it was recorded, the script may get stuck on the SAP logon screen if the App ID is different on both SAP servers. To resolve this issue,

    1. Click the X icon on the left side of the SAP logon pad to cancel the script run.
    2. Return to the Automate Studio application.

    This will stop the script and allow you to make necessary adjustments.

Validating data in loops

In an Excel data file, validation checks all line items, and the validation log messages appear on header cell for the individual line items.

Validating linked scripts

You can run validation on linked scripts in the following configurations:

  • Column-based mapping in Excel.
  • Linked scripts with same types of data files