Fault Message returning to RFC

Hi all,
follow below my scenario:
R3 <-RFC-> XI <-JDBC-> ORACLE
My interface INSERT data into ORACLE.
I need to get the fault message of JDBC and return to RFC.response.
I made the FAULT MESSAGE TYPE and adjust my Message interface to Synchronous with mey fault message, I also made the Message mapping of Fault Message Type to RFC.response, but I don't know how to configure my interface determinantion to mapping the fault message to return.
Could anyone help-me about this problem.
Thanks,
Regis Ferrato

Hi Ferrato,
Check this links
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Alert monitoring and fault message types
May be helpful for u...
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

Similar Messages

Define fault message type for RFC

Hi,
How can I define the fault message type for RFC so that when I import RFC from another server to XI, I can view this Fault type.
So far I could only see Request and Response type .
Thanks

Hi Rokie,
Acc. to me by default we are having only request and response mesages for RFC and in case some exception/fault is there the RFC will through this in the response under the Return parameter having msg,id number as sub fields which you can map to fault message type.
Sachin

Unable to retreive the fault message returned by web service

Hi,
We are working on Proxy to SOAP synchronous scenario. The WSDL provided by the third party has 3 messages - 1. for request structure, 2. response structure and 3. Error message to track the exceptions, if any. The interface working fine for positive test cases but we are facing issues when trying to capture the error message returned by the web service.
We have configured the error message(provided in WSDL) as fault message in our Inbound interface. In the outbound interface, we have configured standard Fault message type provided by XI. we have mapped the two structure.
Now when error is returned by the web service, we are able to see the blank response structure in the payload in MONI in XI. Also the SOAP Error Message structure is there in XI.
But when we trying to retrieve the same in our proxy, it is giving the blank structure.
Please help how to get the error message returned by the web service in proxy....
Please help..
Thanks in advance.

>>>I am getting the error message as the fault message, in the response from the web service.
>>>Now I want to forward the same message to SAP R/3 system. For this I have configured the standard fault message in the >>>outbound interface and have mapped the same with the web service error message. So if I am not wrong, the transformed >>>>structure according to the rules in message mapping should be sent to SAP R/3 system. But I am unable to see the result >>>>of this mapping in XI MONI. Neither is this passed to Client proxy.
You are consuming the third party webservice. Third party webservice WSDL has request, response and fault message. if the third party application logic capture the exception and pass the response as fault mesg, then the above specified target fault mesg mapping with your Standard fault message mapping will be sent to sender or client proxy.
Suggestions:
Having fault message in WSDL does not mean that target system sends fault message during application exception. Check in the SXMB_MONI whether your response during exception is occuring in the fault message structure publised as WSDL. If not then doing mapping will not help. It gives only blank.
If you notice response in fault message structure from third party in SXMB_MONI, then you need to check that at the client proxy side, are you handling/done coding for fault message methods similar to response strucutre for capturing data.
Hope that helps.

RFC - why is my Fault message tab blank???

Hi,
I'm trying to perform a mapping of a Fault message for my RFC to a structure, however after importing the RFC when I switch to the tab for the Fault page, there is no structure defined. My RFC is defined as throwing exceptions. Could you please explain how I get to see the Fault message structure showing in the imported RFC?
Thanks
Brian

Hi,
In the Integration Builder, double-click on the RFC you have imported (under Imported Objects). You will start in the Structure tab.
At the top of the Structure tab page is a Message Type combobox. Use that to switch between Request, Response and Fault.
In my case the Fault Message Type is blank.
The RFC does raise exceptions which are configured in the appropriate section using tx SE37 (Function Builder)
Regards
Brian

Fault message in BPM process

I have a bpm process with a sync send step. i have a default fault message strcuture and my sync interface ( a proxy) is using this as fault message format. In case of an fault in the proxy i get the fault message returned. In my bpm i have an exception handler installed for the exception. What i would like to do in my process is send the fault message to another step like a send step.
i m not looking to understand sync/async bridges or how to setup a bpm process. I am looking for help in how i can work with the fault message in my bpm process other then only let it trigger the exception routine

Hi Frank,
in the view of your BP an exception at proxy side is no reason to stop processing. The message will be put to your interface and it is your decision to put data into a container and to send it. For using a "global" container for every kind of message have a look to my weblog <a href="/people/udo.martens/blog/2006/04/28/bpm-container-for-any-message-type Container for any Message Type</a>. If your send step is not successful and you want to catch that: Define an exception branch for your block, where you send a senseful message to notice the error. You can refer in the original send step the exception, during runtime the process jumps into the exception branch and is doing that what you defined there.
Regards,
Udo

SOAP Adapter - Using Fault Message

Hi all,
I have developed a Synchronous Integration Scenario which receives a SOAP request to the SOAP adapter, calls an ABAP proxy in SAP ECC to post some information and return a response or a fault to the sender.
This all works fine, I am using a fault message in the ABAP proxy to record errors and return them to the SOAP adapter using the fault mapping. Again this all works fine. However when an application error is identified and a fault message returned to thre SOAP adapter, I had expected that the error details in the fault message to be packaged up in a standard SOAP fault and returned to the sender. Instead the fault message details are sent as the payload in the SOAP body of the response.
Can anyone provide information on if it is possible to return the fault message as a standard SOAP fault instead of in the SOAP body of the response.
Thanks
Gary

Dont think this is possible in standard.
As an alternate, maybe you can select option Do not use SOAP Enevlope int he sender SOAP Adapter and thereby the entire SOAP Message will enter the mapping and you would need to use a XSL or Java mapping to strip the SOAP Envlope in the mapping for the request and like wise in the response mapping you would need to add the SOAP Enevlope to the response.
For the fault message mapping you need not add the SOAP Envelope.
Not a standard solution, but can be tried if the requirement is really worth it. Otherwise I think the Fault Message will continue to be sent as the payload in the the SOAP Enevlope as this is how the SOAP adapter works.
Regards
Bhavesh

BPM in CACHE won't activate. Fault message is not defined

Hello All,
After adding fault messages to our RFC scenarios, our BPM will no longer activate from transaction SXI_CACHE. The ReturnCode is 99. When we attempt to do a manual activation, we get an error which reads:
Send step: Fault message '722783b5171311d9881bd5c4c0a8a777' is not defined.
Have any of you seen this before?
We have mappings for the fault messages in interface mappings. Is there something else needed in the BPM itself?
Thanks,
Jimmy

From OSS:
The synchronous send steps define a fault message as exception. In this
case you have to wrap a block around every one or all send steps.
The block catches the exception, in your case the fault message.
The problem is, if no handler is defined, the import of the process fails (SXI_CACHE).
So modify the process, wrap a block with exception
handling around the send step and activate once more.

Fault message mapping

Hello,
I have following scenario.
Synch, RFC Sender -
> XI----
>JDBC receiver.
Also I have defined Fault message data type, message type and also createed Message Interface in which I specified Fault Message type. Now my question is.
When an error occurs I want to get error message to be captured in fault message and map the fault message elements to RFC ---> Rerutn item elements. I was wondering how would I accomplish this?
Thank you,
Balaji

For sender RFC:
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
You must to create a in sm59 in R/3 and XI an R3 conection.
You can see this very interesting blog: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards.

RFC to SOAP fault message not catched

Hi All
I have a scenario where RFC is being send from ECC system I then call a web service, The webservice returns me a fault error messages when for example the order on the webservice system does not exist.
I created a exception in the RFC and created the mapping for the fault message.
When call ing the webservice I get error in comunication chanell:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
I have tried adding:
XMBWS.NoSOAPIgnoreStatusCode = true
In the modules tab but still not getting soap fault.
below is response from webservice if I use other soap client:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <soap:Body>
 <soap:Fault>
 <faultcode>soap:Client</faultcode>
 <faultstring>Unmarshalling Error: cvc-minLength-valid: Value '' with length = '0' is not facet-valid with respect to minLength '1' for type 'nonEmptyExternalReference'.</faultstring>
 </soap:Fault>
 </soap:Body>
</soap:Envelope>

Hi,
I don't think so you can catch 500 internal server errors using falut messages.
Your target system has to capable of sending error messages in valid XML format then only you can catch them.coming too fault message concept we will implement in ABAP server proxies scenarios where we have a opportunity to catch errors in send as response. but i doubt in SOAP receiver scenarios.
Regards,
Raj

RFC - JDBC fault message

Hello All,
Probably this has been discussed before, but i am unable to find a direct solution till now.
I have a synchronous RFC to JDBC scenario, where data is inserted from R/3 to JDBC and JDBC returns with the count of records it inserted in oracle. everything is working fine.
But in case when there is an error in insert, short dump occurs in R/3. i can see the response message has the error that some fields are null and so the insertion failed.
My question is, how to capture this fault and get a exception equivalent in my RFC, so for further processing it can simply be check against SY-SUBRC.
I would appreciate any pointers or help on this.
Regards,
Kinshuk

Hi Kinshuk,
one month ago I implemented also synch JDBC scenario but with call from client proxy (ABAP Proxy <->JDBC). First you ca try is to implement exception in your RFC and then update the metadata in IR. Assign also Fault Message to Inbound JDBC Message Interface and create mapping between RFC exception message and Fault Message.
If it will not help you, try to change your implementation to ABAP Proxy if possible. With Proxy you can use ABAP statement "TRY/CATCH" and catch system error as I do in my implementation.
As far as I know, JDBC adapter does not support Fault Messages. But I never had system with latest SP. For examply in this 1492453 note you can see, that the detail text message of exception in Adapter was not transfered to IS (sxi_monitor) in SP bellow 12. With proxy you should have access to that exception and it might be possible get the "detail text" from exception object.
On my current project I'm still waiting for SP so in my implementation I can catch Proxy exception but I'm not able to tell user what exactly happend. He has to check Comm.Channel monitoring for more info.
If you have SP12 or higher you should be able not only catch system exception but also to get the detail error text from JDBC Adapter back to your proxy implementation.
Martin

AQ Adapter Not Returning Fault Message even if the Enqueue is disabled

Hi....
i am using Oracle SOA 10.1.3.5 and we are trying to catch the error/fault returned by the AQ Adapter...
to create the scenario i have disabled the Enqueue on the Adapter and put the message...but the we are not receiving the fault message (the control is not going to CatchAll Block defined for the scope...)
the message we are getting is witht eh fault tag and not a exception....
i also tried to add the pick activity after invoke...but can someone provide any link to configure the pick for fault callback...
<fault>
-<exception class="com.collaxa.cube.ws.WebServiceException">
EJB Transaction Error.
EJB exception happened while invoking the partner.
Please verify partner service.
-<stack>
<f>com.collaxa.cube.ws.WSIFInvocationHandler.invoke#647
</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke2#538
</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#286
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke#832
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements#413
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform#200
</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#4330
</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1837
</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#77
</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#240
</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#345
</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#6464
</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1908
</f>
<f>com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem#415
</f>
<f>sun.reflect.NativeMethodAccessorImpl.invoke0
</f>
<f>sun.reflect.NativeMethodAccessorImpl.invoke#39
</f>
<f>...
</f>
</stack>
</exception>
-<root class="org.collaxa.thirdparty.apache.wsif.WSIFException">
file:/u01/oracle/product/10.1.3.1/OracleAS/bpel/domains/default/tmp/.bpel_InterfaceCustomerToBillingEBF_1.0_9da16e94dedd6d829b47b8d4b4a5ab53.tmp/EnqueueCreatePortalAccountMessage.wsdl [ Produce_Message_ptt::Produce_Message(CreateCustomerPartyEBM) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
; nested exception is:
ORABPEL-12165
ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
Please examine the log file to determine the problem.
-<stack>
<f>oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation#644
</f>
<f>oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation#739
</f>
<f>com.collaxa.cube.ws.WSIFInvocationHandler.invoke#474
</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke2#538
</f>
<f>com.collaxa.cube.ws.WSInvocationManager.invoke#286
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke#832
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements#413
</f>
<f>com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform#200
</f>
<f>com.collaxa.cube.engine.CubeEngine.performActivity#4330
</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1837
</f>
<f>com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal#77
</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage#240
</f>
<f>com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory#345
</f>
<f>com.collaxa.cube.engine.CubeEngine.endRequest#6464
</f>
<f>com.collaxa.cube.engine.CubeEngine.handleWorkItem#1908
</f>
<f>com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem#415
</f>
<f>...
</f>
</stack>
</root>
</fault
regards
\Sanju03

I have found problem. My application name in iStudio was different from adapter. Once they are same it is ok
Regards Robert

Error message:- java.rmi.RemoteException: Unexpected fault was returned by

Hi All,
When we trying to fetch documents from plum tree portal using a java api, we are getting below error message. please can anyone guide us,
error message:- java.rmi.RemoteException: Unexpected fault was returned by the server (faultcode: Server.userException, faultstring: org.xml.sax.SAXParseException: Content is not allowed in prolog.)
thanks in advance
Srinivas

Cross-posted:
error message:- java.rmi.RemoteException: Unexpected fault was returned by

How to create Fault Message Type when developing RFC (se37)

Hi,
I am working on importing a RFC into XI but am seeing only the Request and Response message structures. The Fault Message structure is blank. I need this to trap .Exception errors like when the connection to partner is broken etc. which look like system errors but they appear in XI as Application errors and the RFC_Name.Exception message is sent back to XI.
Question is: what needs to be done in the RFC so that when I import into XI, I get the Fault Message structure as well.
Thanks in advance
ram

Hello Ram,
You can look into this post as to how to handle [RFC exceptions|RFC Destination Catch Exceptions;.
Hope this is of some help.
BR,
Suhas

Fault Messages (RFC)

Hi experts,
If my RFC function haven't defined exeptions, can i using fault message?,
very thanks,
regards,

Hi Silvia
Did you tested the payload executing at R/3. if the RFC is providing the expected results. If not then you need to debug the FM with the payload at R/3.
Its always a good practice to have exception raise by FM. make life easier
Thanks
Gaurav

A sample web service to return SOAP fault message for application error

Hi,
I need to test behavior of XI, in case of application error (using <detail> tag in soap:fault) from web service in nosoap mode.
If any one is aware of a free web service, which can raise application soap fault message, Kindly provide the details.
Thanks in Advance,
Rahul..

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as ,&QualityOfService=ExactlyOnce appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

Fault Message returning to RFC

Similar Messages

Maybe you are looking for