Runs
Updated 5 days ago
by
Stephanie Krenz
The execution of a task is called a run.
Run 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.
- Name and Type of the Task
- Tabs Runs and Configuration: in the tab Runs you'll see all runs for this Task. In Configuration, you will be able to access all the settings that were set at the time the task was initiated.
- Run: shows the Run number (automatically sequential), the Variant in the package (here Initial) and indicates whether it is the last run (Current)
- Status / Duration / Finished ... & Started at ...: result of the Run (Completed, Running, Failed, Canceled), the time required, and when the run was completed and started
- Bin: one or more Runs can be deleted from the overview here
- Status-Filter: filter the Runs by their status (Completed, Running, Failed, Canceled)
- Notifications: activate specifically for this Task whether and when you want to be notified by email (you can find all the necessary settings in this article). Receive an email when the next Run ends, when it fails or is canceled, or receive no notification (default).
- Clone or Delete: with a click on this button you can clone or delete the Task
Run Details
Clicking on the Run number will show you all the details about the Run. If you click on the button with the three dots, you can delete this Run.
Overview
The overview shows you all the steps that the Run has gone through. The respective tabs next to it provide you with more detailed information about each of these steps. The number of steps, and thus tabs, may vary. Depending on the Task Type, selected settings, etc., there may be more or fewer tabs.
In the Progress section, you will find information on how many steps the Run has completed in total (the number may vary depending on the Task Type).
The selected SAP systems (one or more) are listed in the SAP Systems section.
In the Analytic Steps section (only for Analytic Tasks), you will see the Custom Analytics used and the Analytic Steps per module.
On the right-hand side, you will see detailed information about the Connection. This can be to a SQL Server, a Fabric Mirrored Database, a Fabric Lakehouse, Azure Data Lake Storage or even a Snowflake Connection. Depending on the Connection you have selected, you can be redirected to the respective target system directly via the button below.
SAP Systems
All selected SAP systems are displayed on the left. A status icon shows you whether everything went smoothly. If several SAP systems are listed here, you can view detailed information by clicking on one of the systems on the right-hand side.
There you can see which steps the system has gone through, how long each step took, and whether there were any problems or whether it was completed successfully.
Below that, you will see a list of the tables that were accessed. You can see whether the access was successful, how many entries were found for the selected parameters, and how long it took to access this table.
Analytic Steps (only available for Analytic Tasks)
The modules of the Analytic Steps are displayed on the left. Click on one of these to see more detailed information on the right.
You will see the module, a status icon, how many tables were used in this module, and how long it took to access the entire module.
Below this, you will see the Result Table, the status, the number of entries found, and the duration of this step for each Analytic Step.
Third-Party Services (only available if Extraction has been defined in a Third-Party Service)
On the left side, you can see all configured Third-Party Services (called TPS). You can see more detailed information about each TPS on the right.
The status icon, the number of tables whose data is written to the TPS files, how long this process took in total, the export path for the TPS files, and a Download Files button.
The table below shows you the Analytic Steps, their status, the number of entries found, and the duration.
Health-Checks
Using Health Checks, dab Nexus checks whether the basic requirements for successful analysis and, if necessary, extraction are met before data analysis in SAP.
The following checks are performed:
- License: checks, if the license is valid
- SAP Connections: checks whether the SAP systems are accessible and whether the specified user has the necessary permissions for Data Extraction
- SQL Server / Snowflake / Azure Data Lake / Fabric Mirror / Fabric Lakehouse: checks whether the connection can be established and whether the login details of the stored user are valid
- Third-Party Services: checks whether the stored path is available and the necessary write permissions are set
- Extraction Package (only for Extraction- and Replication-Tasks): checks whether the selected Packages can be merged into one Package
- Analytic Steps (only for Analytic-Task): checks whether all selected Analytic Steps are licensed
- Machine Learning Services (only for Analytic Steps with AI): check whether Machine Learning Services and the R Environment are installed on the SQL Server - only then can AI analyses be performed! Find more detailed information here: Requirements for Machine Learning Services, Installation R Environment
Configuration
In this section, you can see all the parameters that have been set, the Extraction Package or Analytic Group, and the Data Strategy.
On the right-hand side, you can see all the relevant details.
Logs
The log can provide you with information if something went wrong during the Run. You can search it, filter it by status (Information, Warning, Error), and download it.
If an error occurs that you would like to report to our Support Team, please always send a complete Support Package. You can find out how to get it here.
