on 08-18-2006 9:31 PM
I am calling a Outbound proxy (Asynchronous) from R/3. Should I catch fault after the call?
When I don't catch fault, I get the following warning message. What should i do about these warning message?
<i>The exception CX_AI_SYSTEM_FAULT is neither caught nor is it declared in the RAISING clause of "EXECUTE_ASYNCHRONOUS". </i>
Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Directly after your proxy call, catch the excpetions.
ie. CATCH CX_AI_SYSTEM_FAULT
....do stuff
This will alleviate your issue.
Cheers
Colin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Colin, What are the scenarios under which the Asynchronous proxy from R/3 to XI will fail? so that I can test 'Exception handling'.
Also from Ravi's blog (1387), I notice that we catch exception after commit work. I presume we cannot catch exception before commit work.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Hi,
The proxy will fail if the link between R/3 and XI cannot be established or the configuration in R/3 for XI is incorrect. A prime example is if the SLD cannot be reached in XI from R/3
The catch exception should be directly after your proxy call - this is the way I have coded it in the past and it works fine.
Kind regards
Colin.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.