ABAP Proxy Exception / Fault Message

Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
reward points are available.
-Venkat

Hi Venkat,
The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
Regards,
Sumit

Similar Messages

ABAP Proxy and fault messages

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?
The exception CX_AI_SYSTEM_FAULT is neither caught nor is it declared in the RAISING clause of "EXECUTE_ASYNCHRONOUS". 
Any ideas?

Hi SSG,
Check this
Proxy framework: Catch CX_AI_SYSTEM_FAULT
cheers
Prashanth
P.S Please mark helpful answers

ABAP proxy exception to SOAP fault and vice versa not getting mapped

Hi there,
I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
The behavior we are observing is as follows;
When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
2. What can we do in order to change that situation?
3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
Many thanks for your replies.
Edited by: Roberto Viana on Jul 26, 2010 8:30 PM

Problem was caused by some differences in namespaces between source and target.

ABAP Proxy Exception

Hello everybody i have this error in my sxmb_moni of xi for a abap proxy server receiver:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1</SAP:P2>
<SAP:P3>EXECUTE_SYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText>Unable to execute the dynamic application call (kernel error ID UNCAUGHT_EXCEPTION, class ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1, method EXECUTE_SYNCHRONOUS)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any suggestions?
Regards,
Julio Cesar

Hi
Below is the full details of above links
For link 4196517?
Q) Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
Answers : 1) Go to Sproxy .
Select the message interface for which you generated the proxy.
Click on the Structure tab. Do you see any Exception Class generated for fault message ?
2) Just follow all the steps defined in the below Blog and you will find the solution.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
3) I can't find any exception class there in 'Structure' tab. what might be the problem.
4) In SProxy ..under the Message Interface you will see Fault Message Type.
Click on Fault Message Type and check if you can see the fault message type created by xi consultant.
Also ask your xi team to login to IR and re-activate the interface.
5) I can't find any fault message type under Fault Message Type. I will ask my XI consultant to reactivate the interface.
Is this the only problem for this or is htere any other reason for not finding this fault message type in SPROXY.
6) Ideally the fault message type should be visible unless he has defined Software Dependencies and using MT from some other SC.
Even if the fault message type is not visible everything could be all right.
Ask him to check if he selected the fault message type while activating the interface.
Do update us when you get a reply from ur xi team.
7) I have checked with XI admin, he said that he created fault message types in Development Xi but R/3 Development refers to Production XI system in exchange profiles. He asked me to change it to XI development in exhange profile settings. So I am searching info on how to set exchange profiles.
8) The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
II) For Link :4147406?
Q) Hi All,
We have an ABAP Proxy implemented for posting goods movement and it is calling BAPI function module to post good movement. We have got a requirement that if BAPI returns any error, this error message send back to SAP XI.
data call proxy
Legacy -
> XI -
> SAP R/3(call bapi)
<----
error message
Please let me know how to send the message back to XI.
Answers: 1) Refer the following
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
2) you can utilize the fault messages for such an usage -
Ref:
Fault messages -
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
3) You have to do Fault message implementation in this case...
A no. of exception will be there.For any error proxy will catch the exception and will write it in the fault message...so....from r/3 response will go to Xi as Fault message response in case any error/exception occours......
have look here...
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
4) Please go through it is very useful.
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy --Monitoring for Processed XML messages in ABAP Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy --ABAP Proxies in XI(Client Proxy)
/people/sap.user72/blog/2005/12/29/service-enable-your-sap-application-component --- Service Enable Your SAP Application Component
5) the file adapter can work only asynchronous, so you cant have a response. You should build two asynchronous messages. File -> proxy inbound and after the bapi call an outbound proxy is called which is sending a second messge to the file adapter.
6) you can define a synchronous scenario which will include request/response messages.
send the response back to XI.
the file adapter supports BE QoS.
http://help.sap.com/saphelp_nw04s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
7)I have an interface Z_stock_move(message interface(inbound)) and class z_STOCK_MOVE in that. I have clicked exception tab but not able to add exception there as its not enabled for change.
Please let me know how to add the exception to an existing abap proxy.so that i can raise an exception when bapi call to goods movenment returns errors.
Might be useful to U.

Abap Proxy exception Handling

Hi guys,
I've implemented the following scenario:
BPM Process where I've got a async receive (from a file receiver), a sync send (to an ABAP PROXY) and a send async (to a file sender).
The scenario is working great, I've catched 'Communication exceptions', and the proxy contemplates the necessary exception throwers too, but I'm now trying to Handle one specific exception. Imagine you force a dump, with a divide by zero in the proxy code...the proxy will dump and the XI gets a mapping exception (like is supposed to).
The exception is:
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
The thing is, I want to catch this exception on the mapping and handle it, so the bpm process sends the handle response with the file sender.
I've looked to Alessandro Guarneri blog, but it's a little bit different, because I don't want to throw an exception but I'd like to handle it....
Can you guys help me with this question?

Hi Vijaya,
I was able to catch the exception like you said, on the proxy side.
I'm trying to conceive some real and feasible dumps scenarios and for that I'm forcing dumps, and catching exceptions. Divisions by zero was one of the examples.
For division by zero I was able to catch it with a cx_sy_no_handler exception, but I've another example which I'm not being able to catch it.
I'm sendind an message e001(zisa), which will exit automatically from the function module. Am I able to catch that message? Meaning, can I catch it and treat it, instead of the system exiting the function and showing the corresponding message?Is there any cx_* ?
Even better, on sxmb_moni I get:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><html> <body> <H1> 500 SAP Internal Server Error </H1> Error message: O centro nao existe ou nao esta preenchido. ( type of termination: ERROR_MESSAGE_STATE ) </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Internal Server Error Error when sending by HTTP (error code: 500, error text: Internal Server Error)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
So, the SOAP adapter receives something. If it's not possible to catch this exception on the abap proxy side, can I catch and map that soap adapter error text on the BPM side?
Thanks a lot for all of your attention

File to Abap Proxy Scenario : No message log in SXMB_MONI

I have a PI Scenario in which a FTP server is polled every 5 minutes, and when it receives any file, file is archieved and abap proxy is called. Few days back it was running perfectly fine. But For last couple of days I am facing strange error.
My File is archived but abap proxy isnot called, neither I get any message in SXMB_MONI.
any guesses what should I do?
Jawed Ali

Hi Jawed,
HOLD means you have given QoS as EOIO in sender channel and the first message got failed and hence all messages are waiting..
Check this thread
Re: PI 7.1 Messages stuck into the Queue of the Adapter Engine
Try resending the messages through runtime workbench->message monitoring->adapter engine
Regards
Suraj

ABAP Proxy - AAE Synchronous message problem.

Hi,
We are using ABAP Proxy -> PI 7.11-> JDBC stored procedure. We are using AAE.
The problem we are facing is identical to the one mentioned in the thread below:
[Re: <SAP:Code area="PARSING">GENERAL</SAP:Code> - Error;]
That is the first call is ok.. and the second call results into exception. When we switch to normal config without AAE, it is working fine.
Any help on this matter would be much appreciated.
PS: Also please note that similar scenario is running for a different customer without trouble...
Thanks and Regards,
Himadri
Edited by: Himadri Chakraborty on Dec 20, 2010 8:45 PM

The link you gave does not open.
Also please note that similar scenario is running for a different customer without trouble...
Compare the SP level of both the systems.....if configuration is perfect, then ensure that SP level of ABAP and JAVA is at same level.
@Baskar: Proxy supports AAE communication from PI7.11....no need to wait for 7.3....more information is available
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true
Regards,
Abhishek.

Abap XSLT Exception block messages in SMQ2

Hello Community,
I have a XSLT ABAP transformation calling some ABAP objects and it's working well. I just need to handle some applications exceptions.
I wrote an ABAP Class that raise an exception in this way:
RAISE EXCEPTION TYPE cx_mapping_fault
EXPORTING
error_text = l_error.
The problem is that the message appears canceled in SMQ2 and I need to show the error status in the Integration Engine
I have tried with the <xsl:message>:
<xsl:message terminate="yes">Error</xsl:message>
But it didn't work. Exception isn't thrown in the Integration Engine. The message status is processed successfully.
Your help would be appreciated.
Regards,
Yuván>

Hello VJ,
Thanks for your answer. I'm not using BPM in this scenario. I don't understand why messages that throw some exception in XSLT ABAP lock SMQ2. Because this doesn't happen when I use an ABAP-CLASS or message mapping as mapping programs. The lock is just using XSLT ABAP.
Is this normal...?....is there anyway to avoid the lock and change the status to error in the integration engine..?
Regards.
Yuvan,

Problem in ABAP Proxy(sometimes XML Messages are not being created)

Hi,
I am trying to send the data from ECC to CRM when post goods issue is done for a delivery from ECC side. I called my proxy method in BADI : DELIVERY_PUBLISH.
And after calling the method, I used commit work also.
But the problem is, some times it is working fine. and some times the XML messages are not getting created. When I go in debug, looks everything is fine.
I am unable to understand why this inconsistency.
Could you please help me out, do I need to take any more precautions.
Thanks,
Sandeep

You mean you can't find any message in SXMB_MONI of your ECC or is it XI where you can't see message?
If you have not checked in SXMB_MONI of ECC then may be messages are created but they are going into error and that's why you are not able to see any message in XI.

DYNAMIC_CALL_FAILURE - ABAP Proxy Inbound

I have the following error when I try to test a proxy interface with the data coming into ECC 5.0 System.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZSMDCL_MI_FUSION_PRODUCT_MAINT</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a function module which sends a message out depeding on the return status of a BAPI. The proxy is giving the above error when it calls this function module.
reg
reg

Hi Naveen
Try to catch exception in proxy itself
Use follwing link

http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
For Catching Exception in Proxy
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
Thanks
Abhishek
***Please Reward points if helpful********

Build delay in messages to abap proxy without BPM / mapping

Hi everyone,
The abap proxy is receiving messages from PI, is having errors when receiving big loads of messages via PI.
The proxy lock's a table causing the next message to run in error.
The interface is not using BPM or a mapping.
My question is:
What are the possibilities to configure a delay in PI ? (not using a mapping or BPM process)
The abap proxy need some time to process a message before it receives the next one.
Br,
Roy

Hi,
>>>The proxy lock's a table causing the next message to run in error.
if you use async messages with fault messages correcty you can
restart those abap proxies just like IDOCs - and you can schedulerestarting that too
so this is nothing bad - just schedule the restarting and they will get processed
Regards,
Michal Krawczyk

Fault Message Mapping for SOAP Scenario

Hi ,
I have configured a Proxy to SOAP synchronous scenario. The scenario is working fine. Now I need to map the fault message and display the message in SAP in case of any errors. I have used the standard Fault message. But I dont have any message from the WSDL which I can map to the standard fault message. Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same.
Thanks
Amit

>>> Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same?
Fault message is to provide meaningful message to the other end if there is a validation error or business exceptions or so...
a) You are importing WSDL of the third party and using it in soap receiver target side.
b) Normally it is best practice to create a WSDL which contains request, response and fault message. if your wsdl has fault message type declared then you can map the wsdl fault message with your proxy side fault message(which you can create). Please note you rely on the third party wsdl. Third party WSDL must have application logic coded to support fault message in case of application error occurs. Example if there is a validation that does not go through then their application logic must populate data in the fault message of wsdl. Then only if we map the wsdl fault msg to our proxy fault msg, we get meaningful fault details.
If your target WSDL does not support fault mesg, it is not going to be helpful at all.

Interface-Mapping with a Fault Message Type

Hi,
we have an abap-proxy and some messages generated errors. The errors can be displayed via sxmb_moni. The proxy raises an "Application Error (Restart possible)".
Now I wanna transform the generated fault message (of the proxy) with a message mapping and send the output to a file.
My problem is, that it is not possible to define an interface mapping with the fault message as well as it is not possible to define a receiver determination.
Any ideas?
Thanks a lot
Regards
Wolfgang Hummel

Hello
As far as I know you can propogate the application error back to the calling application only in case of a Synch Interface? Are you making a Synch call where the proxy triggers a fault message, if yes then all you need to do is to make the change in XI to have the fault message for both the outbound and inbound message interfaces and then a corresponding fault message mapping and select this in the Interface Mapping and then the fault message will be sent to the source / calling application.
In the case of Asynch calls I don't think this is possible until you use a BPM. Have not tried this myself though.
Regards,
Bhavesh

Problems in ABAP Proxy Generation

Hi All,
I tried to generate an ABAP proxy for outbound message interface "Interface_ABC", which is under software component "DEF".
In our development system, I had successfully created ordinary function modules and structures under the package "/XYZ/UVW" using the prefix "/XYZ/".
When I began the proxy generation, the system asked me to specify the package and prefix. So I specified the package to be "/XYZ/UVW" and prefix to be "/XYZ/".
Then a warning window pops up. It reads "Package /XYZ/UVW does not belong to DEF". I clicked "OK". The "Create Proxy" screen shows up. Then I clicked the "Save" button. This time an error window pops up. It reads "Cannot extend package /XYZ/UVW". The action is thus cancelled by the system.
Does anybody know what is the reason for this problem and how to solve it?
Best Regards
Jerome

Please check the properties of the package in which you are tyring to save the PROXY.
In your case it looks like the property PACKAGE NOT EXTENDABLE is switched on. Once you uncheck you should be able to save the proxy in that package.
Regards,
Ravi
Note : Please reward points if you find the answer useful.

ABAP Proxy To XI

Hi All,
I hope i can get an answer to lingering problem that we have currently.
We manage to configure to have XI --> ECC 5.0 (through Proxy / XI Adapter)
We have another scenario where we are using ECC 5.0 through ABAP proxy to send messages to XI. However, we are facing the following error message :
<SAP:Code area="INTERNAL">DESTINATION_NOT_FOUND</SAP:Code>
<SAP:Stack>HTTP Destination_Receiver missing (system , transaction SM59)</SAP:Stack>
1. SM59 ECC --> XI HTTP Connection Test is Ok
2. SCIF T-Code. XI services all activated
3. SM59 XI --> ECC HTTP connection test was ok
4. XI --> ECC (via XI Adapter Scenario --This is ok)
5. SM59 - Deleted and recreate the connection
6. Regeneration of the Message Interface in ECC
Thank you
Sulaiman

hi asari,
ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.
The proxy generation retrieves the WSDL description of the interface from the Integration Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 u2013 see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).
Example configuration for accessing
interfaces in the Integration Repository (exchange profile)
check link
http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/frameset.htm
reward points if helpfull
regards
kummari

ABAP Proxy Exception / Fault Message

Similar Messages

Maybe you are looking for