SOAP Exception from XI to R/3 via RFC

[shweta_walaskar2]

Hello,

We have a scenario where we are mapping SOAP Exception to RFC Exception.

Message status is application error in SXI_MONITOR and in payload,it shows correctly mapped RFC Exception (SOAP_EXCEPTION) with name and message.

But this message doesn't reach R/3.

Configuration is done as a registered server program in XI using a TCP/IP connection in R/3.

Can anybody please let us know what could be wrong over here?

Thanks.

Regards,

Shweta

[prateek · Accepted solution]

Happened to see this Shweta?

/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi

Regards,

Prateek

[shweta_walaskar2 · Accepted solution]

Hi Prateek,

Thanks for the reply.

We have used this blog to create this scenario and followed the same steps.

We can see this application error message mapped to RFC exception in SXI_MONITOR payload,but it doesn't reach R/3.

Any idea?

Thanks again.

Regards,

Shweta

[Former Member · Accepted solution]

Hi Shweta,

Did you check the queues smq1 in xi and sm58 in sap for any errors?

Regards,

---Satish

[shweta_walaskar2 · Accepted solution]

Hi Satish,

Thanks for the reply.

Yes,there is nothing in SM58 in XI or R/3 as well as in SMQ1 of XI and SMQ2 of R/3.

Regards,

Shweta

[Former Member · Accepted solution]

HI,

In this case your RFC might be getting some kind of response back at least time out exception..!!!

Please can you check the RWB for RFC channel, if thats working fine.

Thanks

Swarup

[shweta_walaskar2 · Accepted solution]

Hi Swarup,

There is no error in RFC communication channel.

The conditions are

sy-subrc 1 for Communication failure

2 for system failure

3 for SOAP_EXCEPTION (passed in name field from XI)

but when I execute the report and this RFC is called,sy-subrc is always 0.

What could be the reason for this?

Thanks for the help.

Regards,

Shweta

[Former Member · Accepted solution]

HI,

As you had said all the settings are done properly....then are you able to see the Request/Response payloads in SXMB_MONI.

Please confirm if everything is on track...

Thanks

Swarup

[Former Member · Accepted solution]

Hi,

Is there any change in the structures of RFC after the import?

Regards,

[shweta_walaskar2 · Accepted solution]

Hi Swarup,

Yes,I am able to see Request/Response in SXMB_MONI which is correct.

Thanks.

Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hi Tarik,

Yes,it might be possible as this scenario including RFC,is still under development.

But Exception SOAP_EXCEPTION was there before as well.

Is there any chance that change in RFC can be the reason for this problem?

Thanks.

Regards,

Shweta

[Former Member · Accepted solution]

Hi,

Yes it is possible, I thing you should reimport the RFC and adjust your mappings accordingly if anything changed..

Regards,

[shweta_walaskar2 · Accepted solution]

Hi,

I reimported the RFC,deleted RFC sender CC and recreated it.

Refreshed cache,problem still exists.

any other options to check?

Thanks.

Regards,

Shweta

[Former Member · Accepted solution]

Hi,

just may be due to application exception, proper commit have not happen. Try to add commit statement at end of RFC.

Thanks

Swarup

[shweta_walaskar2 · Accepted solution]

Hello Swarup,

Thanks a lot for your help.

Unfortunately commit work also didn't help :(((

What to do now?

Thanks again for your support.

Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hello,

A doubt,is it necessary that this RFC has to be exposed as a webservice?

Is this the reason that it is not able to handle this webservice exception?

Kindly reply.

Thanks.

Regards,

Shweta

[shweta_walaskar2 · Accepted solution]

Hello,

Can anybody please let me know if I need to create a service definition for this RFC?

Thanks.

Regards

Shweta

[Former Member · Accepted solution]

Hi,

You dont need it, otherwise you wouldnt be using RFC adapter. After trying that much I think you should trace way.

Try monitoring what is transmitted from PI to R3 using an packet analysing tool like tcpgateway or HTTP Analyser and debug the RFC.. Best luck,

Regards,

[shweta_walaskar2 · Accepted solution]

Hi Tarik,

Thanks for the reply.

I have enabled trace in RFC destination and checked the logs but couldn't find anything relevant.

Its quite strange if a message leaves XI and doesn't reach R/3 ,what can happen in between?

Regards,

Shweta

[Former Member · Accepted solution]

Hi Shweta,

"Its quite strange if a message leaves XI and doesn't reach R/3 ,what can happen in between?" Seeing the message succesfull in SXMB_MONI does not 100% mean the message left XI since you are using an adapter, RFC. It might be stuck in java side.. Go on to dig it...

Regards,

[Former Member · Accepted solution]

Hi Shweta,

It is a long thread, so If i missed can you please tell me whether you are able to see your message correctly (payload) in your Communication Channel monitoring.

Also have you checked the roles and permissions assigned to you RFC user, and whether its locked or not.

Regards,

Rahul

[shweta_walaskar2 · Accepted solution]

Hello Rahul,

Sorry for the late response.

Yes,I am able to see correct payload in SXI_MONITOR and RWB.

Also,RFC user is fine,we use it in other scenarios as well.It is not locked.

Message is successfully sent from XI and is having Application error status.

Thanks.

Regards,

Shweta

[shweta_walaskar2]

Hello,

The solution was,we have added an export parameter to the FM which can hold value of sy-subrc.

Thanks to all for your help.

Regards,

Shweta