DeltaQ Troubleshooting Guide
This article lists common errors, pitfalls and problems when setting up or running DeltaQ.
This article is extended on a regular basis.
------------------------------------
Error:
When using NW RFC library you get the following error during DeltaQ extraction:
ERPConnect.CommunicationException:
RfcListenAndDispatch failed(RFC_SERIALIZATION_FAILURE): Incompatible parameter
type RFCTYPE_BYTE for parameter I_S_HEADER, type RFCTYPE_STRUCTURE is expected.
When using Classic RFC library, the extraction log shows entries like "No progress for n seconds, but
data is not complete yet. Waiting…" which eventually results in a
timeout.
Reason:
On newer SAP releases such as S/4 2023, the default serializer setting for the RFC destination is not set to Classic serializer.
On RFC level, data is transmitted in a way the DeltaQ component can't handle.
Solution:
Go to SAP transaction SM59.
Edit the RFC destination, e.g. XTRACT01, that you created during DeltaQ customizing.
Go to Special Options tab. Find the Select Protocal setting at the bottom and change the Serializer setting to Classic serializer.
------------------------------------
Error:
The extraction log shows entries like "No progress for n seconds, but data is not complete yet. Waiting…" which eventually results in a timeout.
Reason:
This happens, when the extraction job on the SAP side is finished (SM37) but IDocs and/or tRFC data packages get stuck on the SAP side or were sent to a different RFC destination.
Solution:
List of possible causes and solutions:
- You are running DeltaQ extractions on the same RFC destination in parallel. Go to transaction SMQS and increase the Max.Conn. value to at least 10. With single DeltaQ extractions, that value should be at least 2.
- You are running DeltaQ extractions on the same RFC destination (e.g. XTRACT01) in parallel from different computers. In this case IDocs and data packages are sent to the wrong computer.
- If only data packages are coming through but no IDocs, go to transaction WE20, select your RFC destination (under Partner Type LS), double click on RSINFO and RSSEND and change the output mode to Transfer IDoc Immed.
- The gateway host / gateway service settings in SM59 are not maintained properly. If you have a message server try to insert the message server details there, if not, put in the application server. Check carefully that these settings fit to the entries in the DeltaQ dialog.
- You are running SAP’s auxiliary test program called “rfcexec”. This program intercepts outgoing IDocs/tRFC calls. Stop this program.
- Check SAP note 2556150 - "Transaction Recorded" status in transaction SM58
------------------------------------
Error:
The output contains crippled characters, especially non-latin characters, e.g., Chinese, Czech, etc.
Solution:
Go to transaction SM59 and change the unicode flag from non-Unicode to Unicode.
------------------------------------
Error:
The extraction log shows a number of "No job found in SAP" entries.
Solution:
Go to transaction WE20, select your RFC destination (under Partner Type LS) and check the Part. Status on the Classification tab. The status needs to be Active.
------------------------------------
Error:
I get an “Error in Data Selection” from SAP
Solution:
If you use selection values, check if the values are formatted properly. If this error only happens during delta updates, check if your OLTP source is able to handle delta updates (see transaction RSA2 for details). If this doesn’t help, check the log output of the job in transaction SM37.
------------------------------------
Error:
During extraction the error “Not Authorized for XXX” appears even though all authority objects listed in the knowledge base article Authority Objectst are applied.
Solution:
Some extractors add additional authority checks within the extractor that are not foreseeable. So the missing authority objects must be added.
------------------------------------
Error:
SSIS Project Connection Manager vs. Package Connection Manager with parallel DeltaQ extractions.
Solution:
When running DeltaQ extractions within one SSIS package in parallel, we recommend using a package connection manager for each DeltaQ component. A single project connection manager may work, as well. However, with short interval scheduling and heavy parallelism, dedicated package connection managers will add to extraction stability.
------------------------------------
Error:
When doing the DeltaQ Customizing Step 3 (RSAP_BIW_CONNECT_40 ) a PORT_CREATION_ERROR pops up in transaction SE37.
Solution:
Refer to the knowledge base article DeltaQ Customizing - PORT_CREATION_ERROR.
------------------------------------
Error:
The customizing check shows red indicators that are not related to missing authority objects.
Solution:
- The steps of customizing a DeltaQ are not done properly in SAP. Start from the beginning and do exactly what is written in the documentation. If an error occurs during a step don’t consider the step as done.
- Registration of RFC server program is not allowed on the SAP gateway. Refer to the knowledge base article Registering RFC Server in SAP Releases in Kernel Release 720 and higher.
------------------------------------
Error:
The RFC connection check in SAP transaction SM59 fails.
Solution:
Refer to the knowledge base article SM59 RFC - Connection Test fails.
------------------------------------
Error:
Error after SAP system upgrade
Solution:
If the error message is similar to "Error while trying to obtain information about source and destination in table RSBASIDOC..Object ERPCLN800 / XTRACT01 inactive", refer to Customizing for DeltaQ and perform step 5 (execute RSAS_RBWBCRL_STORE).
------------------------------------
Error:
RFC server test failed: Error when opening an RFC connection (CPIC-CALL: ‘ThSAPOCMINIT’, communication rc: CM_ALLOCATE_FAILURE_RETRY (cmRc=2)).
Solution:
Make sure, the RFC server program, e.g. XTRACT01, is allowed to register on the SAP gateway, see Registering RFC Server in SAP Releases in Kernel Release 720 and higher.
In some SAP Releases asynchronous communication between external partner e.g., Xtract Universal and/or Xtract IS and RFC-Destination can lead to above mentioned error message, although all customizing steps have done properly. Make sure to either use the full-qualified-name (FQN) or IP address of the SAP Gateway Host in all involved systems.
------------------------------------
Error:
Error "ISOURCE_NOT_EXIST or GENERATION_ERROR" appears when activating a DataSource.
Solution:
Re-run the function module RSAS_RBWBCRL_STORE as described in the DeltaQ customizing guide.
------------------------------------
Get help for this page
Jitbit HelpDesk