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.

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” error such as below.

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.

1. Edit the CDPOS extraction in Xtract Universal Designer to remove the CDHDR from the tables.
2. Replace the CDHDR~UDATE between @extraction_start_date and @extraction_end_date with:

   CHANGENR between @CHANGENR_min and @CHANGENR_max

3. 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.

$CDHDR = Import-Csv -Path "$xu_location\<app_template_specific>output\CDHDR.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.

Other Extraction Issues

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

Timeout issues

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