process-mining
2023.10
false
- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
Troubleshooting
Process Mining
Last updated Oct 17, 2024
Troubleshooting
The data run also creates a log file that can help in case of unexpected results or if the data upload with the data uploader
fails. The file
extraction.log
contains the logs of the last data run. For each extraction that failed, a return code is displayed. See the official Theobald
Software documentation Call via Commandline for more information. When something with the setup is incorrect, this is mentioned in the error message.
In some older, non-HANA systems, CDPOS is a cluster table and may result in a “join with pool table” error such as below.
ERPConnect.ABAP RuntimeException: RfcReceiveEx failed(RFC_SYS_EXCEPTION) RFC_ERROR_SYSTEM_FAILURE - Join with pool table, cluster or view.
ERPConnect.ABAP RuntimeException: RfcReceiveEx failed(RFC_SYS_EXCEPTION) RFC_ERROR_SYSTEM_FAILURE - Join with pool table, cluster or view.
The extraction of the
CDPOS
table includes by default a join with the CDHDR
table to limit the number of records that need to be extracted. Follow these steps to overcome this error.
- Edit the CDPOS extraction in Xtract Universal Designer to remove the CDHDR from the tables.
- Replace the
CDHDR~UDATE between @extraction_start_date and @extraction_end_date
with:CHANGENR between @CHANGENR_min and @CHANGENR_max
- In the
extract_theobald.ps1
, replace&"$xu_location\xu.exe" -s "$xu_server" -p "$xu_port" -n "CDPOS" -o "extraction_start_date=$extraction_start_date" -o "extraction_end_date=$extraction_end_date"
with the code displayed below.
&"$xu_location\xu.exe" -s "$xu_server" -p "$xu_port" -n "CDHDR_CSV" -o "extraction_start_date=$extraction_start_date" -o "extraction_end_date=$extraction_end_date"
CheckExtractionError('CDHDR_CSV')
$CDHDR = Import-Csv -Path "$xu_location\<app_template_specific>output\CDHDR_CSV.csv" -Delimiter "`t"
$CDHDR_sorted = $CDHDR | Sort-Object -Property CHANGENR
$CHANGENR_min=$CDHDR_sorted.GetValue(0).CHANGENR
$CHANGENR_max=$CDHDR_sorted.GetValue($CDHDR_sorted.Count-1).CHANGENR
&"$xu_location\xu.exe" -s "$xu_server" -p "$xu_port" -n "CDPOS" -o "CHANGENR_min=$CHANGENR_min" -o "CHANGENR_max=$CHANGENR_max"
&"$xu_location\xu.exe" -s "$xu_server" -p "$xu_port" -n "CDHDR_CSV" -o "extraction_start_date=$extraction_start_date" -o "extraction_end_date=$extraction_end_date"
CheckExtractionError('CDHDR_CSV')
$CDHDR = Import-Csv -Path "$xu_location\<app_template_specific>output\CDHDR_CSV.csv" -Delimiter "`t"
$CDHDR_sorted = $CDHDR | Sort-Object -Property CHANGENR
$CHANGENR_min=$CDHDR_sorted.GetValue(0).CHANGENR
$CHANGENR_max=$CDHDR_sorted.GetValue($CDHDR_sorted.Count-1).CHANGENR
&"$xu_location\xu.exe" -s "$xu_server" -p "$xu_port" -n "CDPOS" -o "CHANGENR_min=$CHANGENR_min" -o "CHANGENR_max=$CHANGENR_max"
Note: this is a generic example, the tables names can be different for your app template.
Note: Replace the output folder <app_template_specific> with the output folder specified for you app template in
extract_theobald.ps1
.
When uploading data using Theobald Xtract Universal, the following error message can occur:
Possible cause
A field used for the primary key on the table is not retrived in the extraction.
Solution
To solve this, you need to check if all the fields used for the primary key on the table are retrieved in the extraction.
Below is an example from the
EKKN
table. For this table, the primary key is not complete, because the field ZEKKN
is not retrieved. The issue can be fixed by making sure this field is also used in the extraction.
Tip:
Primary keys in SAP tables can be recognized by the key symbol displayed in front of the field name.