Skip to Content

RFC to RFC scenario,how to handle exception,no export parameter in standard RFC

Hi Experts,

We have a standard RFC to RFC scenario (SU_RAUTH_CHECK_FOR_USER) synchronous scenario where we are sending the request from one system and response back.No mapping is required as such, hence we had not created any IR objects

During testing it from RWB we are getting 'Error while sending the message'.

We checked this Standard RFC and found it doesn't have any export parameters and has only exception parameters,therefore the message in PI is going in exception and failing with Application error.

Hence we created 3 mappings - request, response and fault.

We tried using fault message and mapped the exception of the RFC to the fault message but still we are getting an Application error in SXMB_MONI though fault mapping is getting executed successfully.

Please provide your inputs as how to proceed or if anyone of you have encountered a similar issue.

Is it a issue because it is being tested locally or any other issue? Beacuse we have tested similar RFC's with export paramters from RWB and they work perfectly fine.



Add comment
10|10000 characters needed characters exceeded

0 Answers