View run logs and details - Automate_Studio - Latest

Automate Studio with Evolve User Guide

Product type
Product family
Automate > Automate Studio
Product name
Automate Studio
Automate Studio with Evolve User Guide
Topic type
How Do I
First publish date

The Studio Log Viewer displays a list of all successful and unsuccessful Query and Transaction runs.

View the log entries

  1. Click the File tab, and then click Log Viewer.
  2. Click a log entry to see the run details.

At the top of the screen, the Log Viewer shows you the number of records processed through Transaction, Query, and Direct. You can export the logs to an Excel worksheet by clicking Export to Excel.

In the list of log entries, you can see the following:

  • The type of operation
  • The script file name and the data file name
  • The SAP system where the script ran
  • Who ran the script
  • The number of records that were uploaded or downloaded
  • The number of errors
  • When the run started
  • How long the run took

If the run was not successful, the log entry has a red background, and you can click the log entry to see detailed information on the right side of the screen. Run issues, under Run details, refers to problems accessing the SAP system. Number of errors, under Transaction details, refers to errors in the data that was being uploaded.

It can be unclear whether or not an RFC trace file has been generated. If it has been generated, it's location can be unknown. To address this issue, see RFC Trace Files.

Filter and sort log entries

If you do not see the log entry that you are looking for, use the options at the top of the list to filter by data file type, operation, or date. Or you can filter by the t-code, the SAP table, or the Direct that was used for the run.

You can also sort the list by clicking a heading. Some columns contain two headings—for example, Script file and Data file. Click the item you want to sort by.

Log entry details

When you click an entry in the list, more information appears on the right side of the screen under Details. ROI details are at the bottom of the screen.

Script details

Script type: Transaction, Query, or Direct

Script file: The file name

Script path: The script file's location

Data file details

Data type: The program used to make the data file

Data file: The file name

Data path: The data file's location

SAP details

SAP system: The system logged on to for the transaction

SAP user: The person who logged on to the SAP System

SAP client: The client used for the run

Credentials: Evolve or Studio Manager (or Connect if you use Connect)

Run details

Triggered by: Whether the run was triggered manually or scheduled

Started run at: When the run started

Run time: How long the run took

Repeats: For scripts that are scheduled to be run daily, weekly, or monthly

Next run time: For scripts that are scheduled to be run in the future

Run reason: The run reason entered for this script

Run issues: Any problems with the connection to SAP

Transaction or Query details

Transaction code: The code used for the Transaction script

Run mode: Standard, Batch Input, or GUI Scripting

Tables used: The tables used for the Query script

Output fields: The fields for which data was downloaded

Selected fields: The fields used for criteria

Number of records: The number of records processed during the run

Number of errors: The number of errors during the run

ROI Details (Transaction only)

Manual: How long it would take someone to enter the data directly into SAP

Automated (per record): How long it took Studio to enter the data into SAP

Time saved: The difference between Manual and Automated

Total time saved: The time saved for all records in the run


Until version 20.1, the data recorded in Connect and the time savings that is derived and shared with customers, includes both posting and validation runs. From version 20.3, both posting and validate runs are shown in logs. The time savings done is used while posting for ROI calculations. Posting run and Test run are included in ROI calculations and Validate run is excluded from all the ROI calculations. There is a flag for all three: Run, Test, and Validate.

You can filter out Test runs and view only production ROI data. This option is available in Connect UI as well.