cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Parse Error

Former Member
0 Kudos

Hi all

I am doing RFC --XI ---RFC scenario.

I am using the RFC " FI_ACCT_DET_HR " in sender and revceiver . This RFC doesn't have return parameter but its RFC enabled.

we i execute the scenario i am getting dump in the R/3 and system error in XI.

The payload

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Any help will be greatfull.

Thnz

Accepted Solutions (0)

Answers (4)

Answers (4)

dharamveer_gaur2
Active Contributor
0 Kudos

Check this thread have same error

Test Your BAPI function working properly

http://help.sap.com/saphelp_nw04/helpdata/en/a5/3ec9924ac011d1894e0000e829fbbd/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/df/0495dbbd6f11d1ad09080009b0fb56/frameset.htm

Edited by: Dharamveer Gaur on Sep 16, 2008 7:15 AM

dharamveer_gaur2
Active Contributor
0 Kudos

check Remote login from RFC destination.

Former Member
0 Kudos

Remote logon is working fine.

Even the RFC gateway is also checked and it looks good

Any other clues ?

Thnz

dharamveer_gaur2
Active Contributor
0 Kudos

Every RFC is sync,so check its return parameter

Former Member
0 Kudos

This RFC doesn't have return parameter.

Any other clues ?

Former Member
0 Kudos

The parameters u r passing to receiver RFC is not accepting. Need to send valid parameters

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html