Runs

Updated 4 months ago by Stephanie Krenz

The execution of a task is called a run. Depending on the settings made in the task schedule, one or more runs can be executed.

Overview

After successfully completing the task creation, you will be taken to the overview of the runs in the corresponding task. You can also get this overview by clicking on Workspaces -> Workspace name -> Task name. You will then also see an overview of the runs that have already been executed or are currently running.

Here you can see the following information:

  • Name of the tasks
  • Interval -> Here Hourly
  • Deactivate Schedule -> You can deactivate scheduling here so that the next run does not start automatically
  • Three Dots next to the button Deactivate Schedule -> Here you can change the scheduling of the task (Change Schedule), copy the task (Clone Task) or delete the task together with the runs (Delete Task & Runs) -> you will be asked whether the associated data should also be deleted

In the list of runs you can see more detailed information about the individual runs:

  • Run -> This includes the consecutive number
  • Status
  • Duration -> Describes how long the run took
  • Start Time & End Time -> Start and end of the run with date and time

All settings made in the task are listed in the area on the right-hand side, with the time of the next run at the top.

Procedure

Note
Not all of the steps shown here have to occur in a run. For example, if a workspace is created that only extracts, the Analysis step is missing here. If no Third-Party Services are defined, the Third-Party Services step is not included.

With a click on the run number in the overview previous (here the run #1), you will get another detail oberview (here the overview of a run during execution).

Step SAP Tables - Extract
  1. Task-Name and Run-Nummer with an indicator for the status (here running)
  2. Amount -> Here you can see how many tables are extracted from your SAP-system and how many of them have already been completely extracted (here 0 of 34)
  3. Table-List -> Exact list with the SAP table names, the status of the extraction of this table, the lines already extracted (these are usually extracted in packages of 15,000 in order not to cause an overload on the SAP system), the duration of the extraction of this table and the start and end time of the table extraction.
  • Here you can also see that two tables are extracted at the same time -> This was defined with the slots
  1. Sequence path -> Here you can see which step of the run has already been completed, which is currently running and which steps are still to follow -> Below this, the exact parameters of the task are shown again

You also have the following options at the top right:

  • Reanalyze -> This button appears as soon as the run has been completed - you can use it to restart the run
  • Logs -> There you can filter for information, warnings and errors and download the whole log
  • Three Dots -> You can cancel a current run (Cancel Run) or delete a run (Delete Run)

Step Analysis
  1. Here you see the Result Tables and their status (here Waiting)
  2. You can see, that this run is currently executing the Analyse

Step Third Party Services
  1. Status of the Exports (here Excel) -> How many tables have already been extracted with more detailed information per table in the table below
  2. Status of the Runs -> All steps were completed
  3. Results -> The run was completed successfully (SUCCESS)

Results

You can take a look at the results as soon as the run has been completed.

Excel-Files
  1. Due to the settings above (integration of the third-party service Excel), you can view the Excel files via the specified path.

SQL-Tables
  1. dbo -> Tables with the configured settings with all elements linked to the run
  1. ExtractedData -> Tables with the data from the respective SAP table
  2. Results -> Result Tables
  1. First Result Table
  2. Tableentries of the Result Table
  1. Second Result Table
  2. Here you can see the pseudonymization of the usernames -> Same usernames have the same encryption string here


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)