none
RFC_ERROR_SYSTEM_FAILURE using BizTalk Adapter v2.o for mySAP RRS feed

  • Question

  • I am attempting to update the underlying XML schema used to call a custom SAP function module via BizTalk Adapter v2.0 for mySAP (BTS 2006) and continue to get the error, RFC_ERROR_SYSTEM_FAILURE, after redeploying the solution. When I look in the trace log, I see the following entry:

    **** ERROR file opened at 20080731 123629 Central Daylig, SAP-REL 640,0,78 RFC-VER 3 759904 MT-SL
    T:7636
    >> ERROR: Import parameter length difference detected.
                Read length: 2. Expected length: 0. Type: 6.

    T:7636 <* RfcReceive [10] : returns 19:RFC_INVALID_PARAMETER
    T:7636 <* RfcCallReceive [10] : returns 19:RFC_INVALID_PARAMETER
    T:7636 <* RfcCleanupContext [10] : returns 18:RFC_INVALID_HANDLE
    T:7636 <* RfcCleanupContext [10] : returns 18:RFC_INVALID_HANDLE


    The input parameters appear to be correct and data is getting into SAP as expected, so why does an error get returned to BizTalk?
    Thursday, July 31, 2008 10:18 PM

Answers

  • This error appears to have been due to the custom SAP function module that was being called. Once the function module was corrected, the error no longer presents itself.
    Monday, August 4, 2008 3:00 PM

All replies

  • What version is your target SAP system?

    Friday, August 1, 2008 12:26 AM
  • SAP ERP Central Component 5.0. Release 640 for Basis and ABAP.
    Friday, August 1, 2008 3:15 PM
  • This error appears to have been due to the custom SAP function module that was being called. Once the function module was corrected, the error no longer presents itself.
    Monday, August 4, 2008 3:00 PM
  • I am running into the same issue using the SAP activex objects.  I too am seeing the same error in the trace log.  Can you give any insight as to what caused this in the offending module?

    Saturday, November 8, 2008 4:38 AM
  • In my case, I believe there was an incompatible type coming back from the RFC function module. Once the ABAP developer changed the RFC FM to return a CHAR1 value instead of a NUM1, the problem was resolved. Hope this helps.
    Monday, November 10, 2008 7:16 PM