Process Mining

DELIVERY:

Last updated Jan 26, 2026

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. Refer to 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.

Extraction Issues With CDPOS for Non-HANA Systems

In some older, non-HANA systems, CDPOS is a cluster table and may result in a “join with pool table” erroras displayed in the following code.

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. An alternative way to limit the number of records without having the join is available when running the script. In the configuration of the script, the variable is_sap_hana should be set to false.

Other Extraction Issues

Parse errors

When the extraction is failing with a parse error (for example

Unexpected
                        ')'

), check the WHERE clause of the extraction that is failing. Ensure that the spacing around brackets and the values inside them are correct. Inconsistent formatting can cause parsing issues.

For example, name in ('a', ‘b', ‘c’) should be updated to name in ( ‘a’, ‘b’, ‘c’ )).

After correcting the WHERE clause and saving the extraction, run it again.

Metadata

You may encounter unexpected errors during extraction. For example:

23,O2C_VBAK,2023-05-16_08:46:54.984,4,FinishedErrors,Error,LiveDataExtraction,Theobald.Extractors.Table.TheoReadTableException: Length of the field VBTYP not valid. Given length is 000002 . Length in SAP is 00000823,O2C_VBAK,2023-05-16_08:46:54.984,4,FinishedErrors,Error,LiveDataExtraction,Theobald.Extractors.Table.TheoReadTableException: Length of the field VBTYP not valid. Given length is 000002 . Length in SAP is 000008

This may be caused by the fact that the properties defined in the template extractions do not match with your SAP system.

In Theobald Xtract Universal, select the Refresh metadata button to update the metadata properties to reflect your SAP system and check if the issue is solved.

Incremental extraction issues

If you encounter an issue with an incremental extraction in Theobald Xtract Universal, you can reset the incremental settings by opening the extraction and selecting Delete CDC Resources.

This removes the record of the last successful extraction. The next time the extraction runs, it will perform a full load of the table. Subsequent extractions will then run incrementally again.

You can also use this option when modifying the extraction configuration (for example, when adding a new field).

Timeout issues

During extraction, you may encounter time-out issues. Refer to the official SAP documentation to check the available time-out parameters.

Duplicate key

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.

The following illustration shows 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.