Synchronous File- Soap scenario with fault message

Hi!
I have a File to Soap synchronous scenario.
All is right when no exception is returned by the web service.
I want to use fault messages to catch thoses exceptions, so I have added fault message in message interfaces and in the mapping program in the interface mapping.
Now, when the web service return an exception like :
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
 <soap-env:Body>
 <soap-env:Fault>
 <faultcode>soap-env:Client</faultcode>
 <faultstring xml:lang="en">NOT_CREATED</faultstring>
 <detail>
 <n0:Z_WS_CREATE_WAGON.Exception xmlns:n0="urn:sap-com:document:sap:rfc:functions">
 <Name>NOT_CREATED</Name>
 <Text> does not have packaging material type and is therefore not a pack.mat.</Text>
 <Message>
 <ID>HUSELECT</ID>
 <Number>041</Number>
 </Message>
 </n0:Z_WS_CREATE_WAGON.Exception>
 </detail>
 </soap-env:Fault>
 </soap-env:Body>
</soap-env:Envelope>
I get the following error :
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
 <SAP:Category>XIServer</SAP:Category>
 <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
 <SAP:P1>http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon</SAP:P1>
 <SAP:P2 />
 <SAP:P3 />
 <SAP:P4 />
 <SAP:AdditionalText />
 <SAP:ApplicationFaultMessage namespace="" />
 <SAP:Stack>Interface mapping http://www.arcelormittal.com/radis/rad IM_RAD_to_ZWsCreateWagon does not exist in runtime cache</SAP:Stack>
 <SAP:Retry>N</SAP:Retry>
</SAP:Error>
My mapping program for fault message is well defined (I tested it with the exception message received from the web service).
I have also refresh caches, but without success...
Can anyone help me ?
Thanks in advance,
Laurence

Hey Laurence,
A File adapter is aysnchronous u cant use for synchrous because it cant acknwlodge the response it gets or itt sends.
regarding two asynchoronus
1. file to SOAP asychn.
2. triggger the second one if SOAP has exception then pass the error from SOAP to New File.
using BPM we have to use Transportion level acknowledgments
please reward points if it helps
Regards
Sreeram.G.Reddy

Similar Messages

Synchronous Proxy - SOAP Scenario (Error 500 in Response).

Hi
I've built a few Synchronous Proxy -> SOAP Scenarios,
with 'Do Not Use SOAP Envelope' option.
For two of them, I'm facing a common error.
The error is: ADAPTER.HTTP_EXCEPTION (HTTP 500 Internal Server Error).
When I paste the EXACTLY SAME payload picked up from XI, into the SOAP client, it works giving valid response.
Trying to figure out the issue.
R/3 System:
WAS 620 (Level 0041)
XI System:
PI 7.0 (Level 0007)
SOAP System:
BizRights (Approva) 3.0
Any help is appreciated.
Rajendra.

Hi,
Following SAP notes may help you- 804124, 807000
Regards,
Moorthy

XI BPM Collect Meassages Scenario with one Message as an optional

Hi guys,
I need help to implement XI BPM Scenario with Collect Messages Pattern. Here is my Scenario. I am getting four different types of flat files from four interfaces. Using these four files I need to merge using correlation relation and finally have to create One IDoc type to send it to SAP R/3.
But out of these four messages last Message type is an Optional Message. i.e the process has to continue even if forth message is not available by taking first three messages.
Please let me know which pattern is suitable for this scenario.
Thanks.
Siva.

Hi,
I hope u are receiving four different interfaces.Have a local container variable of simple type integer.you put a fork with four branches after the start step.Each branch has a receive step corresponding to one interface. Then after each of the receive step in each branch put a container operation performing some action on the container variable may be incrementing.so in the end condition of the fork check the value of the container variable i.e you can check if that variable is 3(three of the interfaces have been got).so this ensures that ur fork doesnot wait for all the four.hope this works.
Regards,
Sudharshan

I cannot open files in excel with error message "The file name or path contains invalid characters

I cannot open files in excel with error message "The file name or path contains invalid characters

Found the solution. The hardrive name was changed to "/" which is not a recognised file path character. So I changed the name to "Mac" then I was able to already open all files in excel and word

Extended SOAP Scenario with Security

Hi All,
Could anyone send me the step by step procedure for "Extended SOAP Scenario with Security"?
Regards,
Sai.

Hello,
Please use the search option on SDN.
There are no step by step guides as such and you will have to combine multiple different activities to achieve this, including set up of Server SSL on XI and then set up of the SOAP adapter to use the certificates.
Refer to the guides on SDN for these.
Regards
Bhavesh

Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

Hi,
I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
BR
Holger

1)
you maus define 3 mapping.
1)request
2)response
3)Fault
in Interface mapping define at response boths (2-3) mapping. its clear??
2)
otherwise sometjhing is not clear, why do you want fault?? why dont you get only response message. we implement this kind of response:
<response_MT>
<ID> (error ID)
<system> (target system)
<error> (Error Description)
</response>
by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
Thanks
Rodrigo
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

SOAP adapter engine with system error, problem with fault message.

HI,
I have IDOC -> PI -> SOAP scenario.
Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
The error is at PI -> SOAP.
I have wsdl provided by the receiver webservice. Which I have imported.
And created a service interface against this wsdl. I tried changing it to both sync and async.
I have also provided fault message.
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
action = processDocument. Also provided user id and password.
I have a
Sender Agreement
Receiver determination
Interface determination
Receiver Agreement
I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
How does the receiver know which service interface is it? The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
Service interface name which I created in the ER. Where in the document the Reciever interface name is sent?
Where can I see the generated soap document for the receiver?
Is there some setting/configuration required in PI for this to work?
I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
When I provide the service interface name in the communication channel I get a valid fault message.
Similarly
When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
The fault message what I see in SOAPUI has the below format.
<soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
 <faultcode>axis2ns1:Server</faultcode>
 <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
 database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.</faultstring>
 <detail>
 <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
 - Validation failed when the database default values were set. See the associated message for more information.
 BMXAA4190E - Country NZ is not in the value list.
 /Exception>
 </detail>
</soapenv:Fault>
And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
the above. Is this the problem? Can I change the data type here to be the same as above?
Audit log in the RWB adapter engine.
Time Stamp Type Description
30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
30.09.2011 15:10:57 Information SOAP: completed the processing
30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
30.09.2011 15:10:57 Error MP: exception caught with cause
com.sap.engine.interfaces.messaging.api.exception.MessagingException
30.09.2011 15:10:57 Error Adapter Framework caught exception: null
30.09.2011 15:10:57 Error Delivering the message to the application using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException.
30.09.2011 15:10:57 Information The message status was set to WAIT.
30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
15:15:57 NZDT 2011.

I tried changing it to both sync and async.
I have also provided fault message.
dont feel that you need to do above steps.
I have a
Sender Agreement
ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
When I see the message content, the SOap document shows me the details about IDOC
this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
How does the receiver know which service interface is it?
receiver need not know about the SI created in PI.
The Service Interface which I created in the ER is
different from the WSDL, Does this have to be same?
you should the WSDL (external definition) as the Request Message in your service interface.
Is there some setting/configuration required in PI for this to work?
nothing specific...AFAIK
I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
Things to check:
WSDL structure in PI and in target system is exactly the same.
does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
target system is up and running?

File-to-File/RFC scenario with reading filename

Hi,
i have a File-to-File/RFC scenario which causes some problems in desining it correctly. Maybe some of you has an idea how to do this.
Scenario:
- A file is picked up by a File-Adapter. The files are different: pdf, doc, tiff, jpg, txt, ...
- The file must now go through a business process (not necessary the file, but i need the filename in the business process).
- The process has to contact several backend systems (SAP R/3) to collect some data. To achieve this the filename has to be send to this systems.
- The collected data are send via SOAP to a receiver system
- The file itself has to be stored in a directory via File-Adapter.
Here's my problem:
- Is it possible to transport the binary file content within a message which contains other elements (e.g. filename)?
- Is it possible to do graphical mappings with such a payload (only 1 to 1)? Or must i use Java Mappings only?
- How to generate a Message from the sender File Adapter which contains binary file content AND filename? Is this possible with a Module?
- Is it better to create 2 messages with an adapter module? One with the image the other with the filename. Or is it better to split them later in a Mapping?
Thanks in advance,
ms

If all that you need is the file name, use adapter specific settings in the sender file adapter. Then you can access the file name in mapping runtime in UDFs. If you want to have content of the pdf, jpg etc images, i do not think there are ready modules available except for reading pdfs ( you might have to research on this).
For look ups etc with R3 systems, you can use the file name that you got from the adapter and store it in mapping fields.
VJ

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

File Sender Scenario - Mapping error message

Hi All
Scenario
I am trying to develop a test scenario where a record is read from the file and sent to R/3 using RFC (Bapi)
So i believe this will involve a file adapter as sender and a RFC adapter as receiver, I have configured data types, message types, message mapping, interface mappings, sender determination, receiver determination etc.
Problem
When i put the text file in the polling directory the file is read, but there is an error,
On checking Processed XML message in SXMB_MONI I see that the following steps listed
1 - Inbound message (CENTRAL)
2 - Receiver Determination
3 - Interface Determination
4 - Receiver Grouping
5 - Message Branch According to Receiver
6 - Request Message Mapping
7 - Request Message Mapping
Step 1 - 6 does not show any error message, step 7 has an error with the following message
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_basic_paycreate_file_to_rfc_map~</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException<;/SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
Additional Information
My Business System Commnication channel has a Sender File adapter, this file sender is configured to read from file system from a certain directory and message protocol is File Content Conversion.
In Content Conversion parameters input fieldname and input separator are configured (does anything else need to be configured in this section?)
My input file is of the structure aaa,bbb,ccc,ddd,eee,fff,ggg
My Data Type is of the structure
<data header>
 <aaa></aaa>
 <bbb></bbb>
 <ccc></ccc>
 <ddd></ddd>
 <branch1>
 <eee></eee>
 </branch1>
 <branch2>
 <fff></fff>
 </branch2>
 <branch3>
 <ggg></ggg>
 </branch3>
</data header>
Questions
First question is why is there 2 instance of Request message mapping showing up in the monitor? Isn't this supposed to show up only once?
Second question it appears that the problem is something to do with Mapping (Message Mapping) but i tried to test the message mapping manually using the data generated in the payload and it passes the mapping successfully.
Third question, how is the input flat file converted to the complex structure of data type (as mentioned in additional information above) is this done by the input.filedNames that assigns the corresponding values from flat file to the data type?
Fourth question - is there a way to run the process step by process (as a step through in other programming IDEs?) so the problem can be more easily identified?
Thanks
Anant

Hi All
I little update - it appears that some of the scenarios developed earlier that were working earlier are now also failing at the same process of mapping with this error message.
So i am suspecting that this is not a problem with the mappings in my scenarios but rather a some technical setting related to how XI invokes this class - com.sap.aii.utilxi.misc.api.BaseRuntimeException.
Does any one have any ideas what i can check to confirm this? Whether the problem is in the technical setting or the scenario configuration?
thanks
Anant
error message attached.
<?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>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_CheckDeposit_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_CheckDeposit_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Synchronous IDoc - SOAP scenario

Hi all,
Our current scenario is like this: SAP (Idoc) -> XI -> SOAP (Idoc). The receiver system will reply with an ALEAUD Idoc as in: legacy (IDoc over SOAP) -> XI -> SAP IDoc).
We have a requirement to wait with sending the next IDoc from XI to receiver Web Service on legacy side until we get an ALEAUD IDoc back for the previous IDoc sent to the Web Service.
How can we implement this?
Is BPM necessary?
As far as I know you can only set the QoS for sender adapters, and the SAP Idoc scenarios are always asynchronous. But we can implement a synchronous send step in a BPM with ALEAUD as response message. This will solve our problem, correct?
Any other way? We would like to avoid using BPM.
Any help with this is highly appreciated!
Br,
Kenneth

Thanks for your reply, Udo:)
I am currently building the BPM now.
So, you are saying that I cannot create an inbound sync MI with input message IDOC and response message ALEAUD?
We want to send ACC_GL_POSTING IDoc (or identical structure) to a Web Service and receive the ALEAUD from the legacy system through a Web Service published on XI. We want to relate these two so that the BPM finishes when it receives the ALEAUD, and can then send the next ACC_GL_POSTING IDoc.
I have created the following objects in repository:
MI_ACCGLPOSTING_ASY_ABS (in receive step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_ABS (in send step in BPM)
MI_ACCGLPOSTING_ALEAUD_SYN_IN (used for receiver interface towards legacy SOAP adapter)
MI_ALEAUD_ASY_ABS (used for send step in BPM)
I believe no mappings are necessary since we are not doing any conversions.
Can you please confirm that this looks correct, and also provide what settings I need in Directory?
Thanks a bunch!
-Kenneth

Automizing error message with Fault Message Type

(Request F6) (Request F6)
System -
> XI -
> SAP (Doesn't have F6)
 <-- XI <--
 SAP (Doesn't have F6)
 (Respons: error) (Respons. error)
(Problem) When the request message doesn't content sufficient information that is required for respons then the XI team will get the message error and the responsibility to solve the problem. In this scenario it is the XI team that sends the error respons to the System.
(Request (eg. F6) ) (Request (eg. F6))
System -
> XI -
> SAP (Doesn't have F6)
 <-- XI <--
 SAP (Doesn't have F6)
 (Respons: error) (Respons. error)
(Solution) We want to automatize the process so that the error message goes directly to the System via XI. In other words we only want an acknowledgment of the error in XI, we don't want to solve the error since we believe that it is the sender System that is responsible.
We have seen that there is a Fault Message Type in the Message Interface and we are wondering if that is the way to do it? And it that case, how?

Hi,
Fault message is a error meesage. Its like an exception in simple terms. The fault message is used to
store a log for application error. Fault messages is defined in IR.
To give a overview on Fault messages it is mostly used in synchronous communication. When an error
occurs at the inbound side instead of sending the response message back it sends a fault message back
to the sender system to handle error.
Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get
the exception or error mapped which has occured while execution of Application at the sender/receiver
end....
One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at
r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the
default)..
Fault messages are used to propogate / send back the error message to the calling application. This is
used when there is a failure and the sending system needs to know what the error was. This is more of
catching Application Errors
check this nice blog also
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
Asynchronus RFC exception handling
XI Alerts are not getting triggered from proxy servers
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
a258cf083bca
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Fault Message
Regards
Seshagiri
Edited by: N V Seshagiri on Feb 29, 2008 12:19 PM

Sync/Async bridge via JMS with FAULT messages

Hello all, 
I set up a sync/async bridge scenario with using of JMS communication channel (SAP - JMSReceiverCC - JMSServer and application - JMSSenderCC - SAP). The normal communication works fine. 
But what we can not solve is the Fault Message handling. If there is a application error behind the JMS, a fault message is generated instead of proper application response and sent back to XI. Without any additional setup of JMS Sender CC the processing of the message ends with "MAPPING - EXCEPTION_DURING_EXECUTE", because normal "response mapping" is executed instead of "fault message mapping". This is correct behavior without any discussion. 
[SAPhelp|http://help.sap.com/saphelp_nw70/helpdata/en/45/202845de34072ce10000000a155369/frameset.htm] says that there are 2 module parameters to be set : fault, faultNamespace. The description is rather vague, so let's see, what the "NotifyResponseBean" does, when parameters fault/faultNamespace are filled: 
<pre>if(fault != null && faultNamespace != null)
if(faultNamespace.equals("http://sap.com/xi/XI/System"))
 ((XIMessage)message1).setMessageClass(MessageClass.SYSTEM_ERROR);
 ((XIMessage)message1).setError(fault, "no additional information");
} else
 ((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_ERROR);
 ErrorInfo errorinfo = message1.createErrorInfo();
 errorinfo.setAttribute("ApplicationFaultInterface", fault);
 errorinfo.setAttribute("ApplicationFaultInterfaceNamespace", faultNamespace);
 errorinfo.setAttribute("ErrorCode", fault);
 errorinfo.setAttribute("AdditionalErrorText", "no additional information");
 message1.setErrorInfo(errorinfo);
} else
((XIMessage)message1).setMessageClass(MessageClass.APPLICATION_RESPONSE);
}</pre> 
The code is pretty straight forward so one could assume, that it's the name and namespace of inbound synchronnous message interface what is supposed to be filled in the values of each parameter. And from that kind of information SAP XI can evolve how to handle the response, actually the fault. 
Unfortunatelly the real situation is different - every time the fault message is generated and sent back to XI, the response is correctly corelated with the request message, "WaitResponseBean" and "NotifyResponseBean" are finished correctly and the processing crashes in messaging class on following exception: 
java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:592) at
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
com.sap.aii.adapter.xi.ms.XIMessage.updateHeaders(XIMessage.java:4244) at
com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.java:570) at
com.sap.aii.af.ra.ms.impl.ServerConnectionImpl.request(ServerConnectionImpl.java:212) at
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(MessagingServlet.java:337) at ...
 
Is there anyone, who can put more light on JMS sync/async bridge fault handling ???
 
Thank you ... 
Regards
Tomas

Hello again,
I proceed in investigation little more, but the main problem has not been solved. I found that the problem is not even in WaitResponseBean (placed in JMCReceiverCC). This bean is woken up properly on base of proper CorrelationID. See the log:
2009-10-15 11:00:33 Success WRB: entering WaitResponseBean
2009-10-15 11:00:33 Success WRB: retrieving the message for f1ea1fc0-b96d-11de-9b68-00144f4acd86 ...
2009-10-15 11:00:46 Success WRB: retrieved the message: ApplicationError
2009-10-15 11:00:46 Success WRB: leaving WaitResponseBean
I think, that the problem is somewhere within main messaging functionality. I suppose that on base of exception message:
com.sap.aii.messaging.mo.MessageContext.setAttribute(MessageContext.java:140) at
which is generated.
Any ideas or comments ?
Thank you in advance.
Regards
Tomas

Exception handling with fault message type not working

Hi,
I have a sync proxy to proxy scenario and I have created a fault MT and specified in the outbound and Inbound service interface...
*In Inbound proxy I have the following code--*......
RAISE EXCEPTION TYPE z_cx_test_fault
EXPORTING
standard = l_standard_data.
In the sender side abap code which calls the outbound proxy I have the follwing code -
CATCH cx_ai_system_fault INTO lo_cx_ai_system_fault.
txt = lo_cx_ai_system_fault->get_text( ).
WRITE txt.
CATCH z_cx_test_fault INTO lo_cx_test_fault.
txt = lo_cx_standard_message_fault->get_text( ).
WRITE txt.
CATCH cx_ai_application_fault INTO lo_cx_ai_application_fault.
txt = lo_cx_ai_application_fault->get_text( ).
WRITE txt.
when i test the inbound proxy separately I get the custom fault message properly...
however when i run the proxy to proxy sync scenario and the custom exceptionz_cx_test_fault is raised inside the receiver proxy .......control goes to CATCH cx_ai_application_fault and not CATCH z_cx_test_fault .
I understand that cx_ai_application_fault is the super class of all the exception class but why does control go to its exception handling when a custom exception is raised...
Edited by: hema T on Feb 26, 2012 1:16 PM
Edited by: hema T on Feb 26, 2012 1:17 PM

Hi
I tried changing the sequence also but it did not work...
I can see an appropriate response coming from the receiver in SXMB_MONI of PI...this response has the "fault response "
"fault detail" data that I want.....however when the control goes to the sender why does it go to CATCH CX_AI_APPLICATION_FAULT and not not my CATCH z_cx_test_fault .
My observation - If I change the scenario to SOAP to Proxy sync..then the sender SOAP client gets the appropriate custom fault message back.
Edited by: hema T on Feb 27, 2012 1:17 PM
Edited by: hema T on Feb 27, 2012 1:17 PM

Synchronous process integration scenario with PI 7.1

Hi all,
Iu2019m trying to create a process integration scenario which contains two actions. Both actions use the same synchronous interface to a web service which takes some parameters and returns a value. When I check the configurability it displays the errors:
Connection from Action1 to Action2 has no outbound interface
Connection from Action1 to Action2 has no inbound interface
and the warning:
Connection from Action1 to Action2 has no mapping
I first assigned the service interface as outbound interface to Action1 and inbound to Action2. Next I tried to assign the interface in- and outbound to both actions, but this didnu2019t change anything on the message. The same scenario with the interface set to asynchronous seems to be valid (but looses the return value of course).
Can anyone give me a hint what Iu2019m doing wrong? Is there any special consideration for synchronous communication which doesn't apply for asynchronous services?
Regards,
Tarik

Deleting and recreating the actions and service interfaces exactly the same as they were before solved the problem. Seems as if changes in the interface objects sometimes are not activated correctlyu2026

Synchronous File- Soap scenario with fault message

Similar Messages

Maybe you are looking for