ERROR in SOAP scenario

Hi,
I am doing SOAP to FILE scenario. In SXMB_MONI, the error is coming as follows:
either no channelID specified or no channel found for the specified party, service, and channel name
Thanks,
Anup

Anup Says..
either no channelID specified or no channel found for the specified party, service, and channel name
The error lies in the way your URL is specified. Please check the following your URL:
1) The name of the CC and Business Service is exactly the same...as given in ID....there should be no difference....not even of the case (lower/upper).
2)Whenever you copy your URL, some spaces get introduced...not your fault...check for it and remove it
3) Have you activated all the recent changes in ID?
Also check the following..
If you are using..
http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?action=FindChannel&channel=<party>:<ServiceName>:<Channel Name>
then try with the below one
http://<serverhost>:<port>/XISOAPAdapter/MessageServlet?channel=<party>:<ServiceName>:<Channel Name>
Regards,
Madan Agrawal

Similar Messages

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

Error handling in File - XI - SOAP scenario without BPM

Hello!
We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
Regards, Tanja

Hi Tanja,
>>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
I think, you should check that out. It is assumedly only 2 days work to build a scenario:
IDoc -> BP
BP <-> SOAP/HTTP
BP -> IDoc (Acknowledgement)
In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
>>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
Filling of ALEAUD fields:
E1ADHDR/MESTYP: original message type
E1ADHDR/E1STATE/DOCNUM: original IDoc number
E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
I ve done such a scenario several times. That works without any problems.
Regards,
Udo

HTTP 500 Internal Server Error with Large Attachment in SOAP Scenario

Hi,
we have implemented SOAP - XI - SOAP Scenario in our landscape (Sap Neatweaver Process Integration 7.1) .
One of the functionality of this scenario is the Upload of Documents to External Web Service through standard SOAP Attachment.
If we try to upload a small file (smaller than 20MB), task works fine and the document is correctly uploaded.
If we try to upload a larger file, we encountered in this generic error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)
We tried to increase timeout parameters (in communication channel and in ICM Value) but the response is the same.
We verify also if icm/HTTP/max_request_size_KB parameter was set to a value smaller than our file size limit (20MB) but is set to default value (100MB).
The problem isn't on External Web Service Layer because if we try to upload the same documents directly to that web service upload works fine, and in External Web Service's Log there aren''t any indications of this error.
So I ask you: are there any System Parameters to verify to solve this issue?
For additional, in ICM Monitor LOG we can read this WARNING when we call our service:
WARNING => IcmReadFromConn(id=53/454390): temporarily out of MPI buffers -> roll out [icxxthrio_mt 2646]
This warning may be related to the problem? If yes, how can we solve it?
Thanks a lot,
Marcello Ricci

Hi ,
Please answer my following questiosn.
1) which PI version are you using?
2) How many J2EE nodes you have.
please be reminded that SOAP is not for the heavy messages. Then you need to increase your timeout parameters from BASIS.
Rgds
Veeru
Edited by: viru srivastava on Dec 14, 2010 10:18 PM

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Error in synchronous( abap proxy to soap)scenario

Hi experts,
My scenario is synchronous abap proxy to sysnchronous soap. for proxy I am using business system name as ERDCLNT220 and soap business system name as BS_HRS_DEV
configuration steps are
1. only client proxy to soap scenario I have done.
communication channels: only receiver soap adapter. no proxy sender communication channel for client proxy.
Already we have RFC destination connection and connection type H for proxy to xi.
1.Is it required RFC destination connection for xi to server proxy.
2.Is it required receiver proxy communication channel for server proxy?.
i HAVE TESTED THIS INTERFACE. I am able to send the request. But I am not able to receive the response from soap webservice message .
error is:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson
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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Exception occurred while trying to invoke service method getPerson. Setting message to status failed.
Kindly help me.
advance thanks
thanks and regards
elton
Edited by: eltonsaranya on May 9, 2011 10:27 AM

Your exception message shows problem at the webservice side.
Check the following:
a) you need two mappings one for proxy req to soap request and other soap response to proxy response
b) You need to create service interfaces both sender and receiver synchronous .
c) communication channel QOS is best effort for both sender and receiver
d) I dont see problem in soap configuration. Bcuz you are able to ping and while getting response from the method getPerson it fails.
f) See your SOAP response structure matches with WSDL provided.
g) You can also test outside PI.. I meant testing via soap client tool like SOAPUI for that web service. So that you know whether problem exists on the target system or not.
Hope that helps.

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

RFC to SOAP Scenario error

Hello ALL
I am trying to working in RFC to SOAP scenario in sap pi 7.31 single stack system.with help of blog **************** - Scenario on RFC to SOAP
i am trying to pass input values from ECC through RFC to web service .
while sending data using function module from ECC system i got following error
thnx in advance

Hi Ganesh,
are you getting any error is SM58? Please check the below blog for configuration
Michal's PI tips: How do you activate ABAP Proxies with AEX - simplified version
IDOC_AAE To File with all Configurations
the below discussion will be useful
RFC to FILE(7.3) single stack

Error RFC to SOAP Scenario

Hi Experts,
I am getting an error while dealing with RFC to SOAP scenario::
soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
IS it problem from the webserver in sending the response?
Please suggest.
Thanks & Regards,
Sushama

Hi Suraj,
Thanks for the imputs.
We are given with the webservice by separate team, also I am accessing the application via Citrix. I cant test the WS outside the client network and in client desktop they haven't installed Altova Xml Spy
Request and response both are generated in Moni. It seems problem in receiving response only ?? WS url is also correct.
Regarding Receiver Soap parameters:
I have checked adapter specific identifiers and Variable transport binding.
Please suggest, if this is problem with the WS, I need to check with the team.
Thanks & Regards,
Sushama

Error in SOAP sender scenario

Hi All,
   I am getting the following error when i execute a sender SOAP scenario from XMP Spy.
Scenario : SOAP --> XI --> RFC
I am getting the following error when i try to send request from XML Spy.
Error in XMl Spy:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
               <text>com.sap.aii.af.mp.module.ModuleException: *adapter inactive*
     at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:703)
     at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)
     at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
     at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
     at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:436)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
When i go to RWB-- > communication channel monitoring i see the channel status as "Started but Inactive" and when i go to Cluster node tab--> Cluster Node Details for Channel Unifier i see the following two entries every single time i try to send a message
14/10/10 05:35:10   error occured
14/10/10 05:35:10   request received
Please help to figure out what could be wrong.

open the SOAP Sender channel in Integration directory and change the status to active and then activate. Try resending SOAP message from XML spy

HTTP 401 Unauthorized, error in proxy to SOAP Scenario

Hi all,
We got the below error in our proxy to SOAP Scenario.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized
We configured User Authentication,Proxy and Proxy User Authentication for the Receiver Communication Channel correctly still we are getting this error.
So please let me know what could be the possible reasons behind it and how to resolve it.
Waiting for your valuable response.

Hi,
Consider the parameters connection pool size and connection wait time:
ume.r3.connection.master.poolmaxsize
ume.r3.connection.master.poolmaxwait
These parameters are described in the note below:
#821026 - AdapterEngine messaging URL returns HTTP 401 under high load
Also, ensure you have maintained the correct password, which MUST be the same, for all the service users
on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..
Please kindly check the note below:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
And ensure that the user has the correct role as per link below:
http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm
Regards,
Caio Cagnani

HTTP to SOAP scenario error

Hi guys,
I have developed an HTTP to SOAP scenario, in order to invoke a Web Service.
I am trying to test the scenario by using an HTTP client.
However, I am getting the following message, in the result:
Result:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Pipeline specified in URL attribute (type) not existing</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code><SAP:P1>/sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=++++&sap-client=100&sap-language=EN</SAP:P1><SAP:P2>ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS</SAP:P2><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Pipeline ID ENTRYNAMESPACE=HTTP%3A//FAMAR.GR%3ADEMOS which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&amp;interface=GetStockQuote_Sync_OB&amp;service=HTML_Service&amp;party=&amp;agency=&amp;scheme=&amp;QOS=BE&amp;sap-user=xiappluser&amp;sap-password=++++&amp;sap-client=100&amp;sap-language=EN)
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Do you have any ideas?
Also, I am not able to see in SXMB_MONI the messages that are generated.
This is only possible in Message Monitoring in RWB.
Thank you
Evaggelos

Hi Evaggelos,
The URL you used to generate the WSDL for your webservice is wrong:
URL = /sap/xi/engine?type=entrynamespace=http%3A//famar.gr%3ADemoSOAP&interface=GetStockQuote_Sync_OB&service=HTML_Service&party=&agency=&scheme=&QOS=BE&sap-user=xiappluser&sap-password=+++++&sap-client=100&sap-language=EN
It should be of the type:
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>
Thanks,
Varun

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

Fault message in sender SOAP scenario

Hi mates,
I've a o/b synch MI which is exposed as a web service. I've specified the fault message with faultcode, faultstring, faultactor and detail. I've a BPM as the receiver for this synch infterface. This BPM implements synch-asynch bridge.
Now the question is...How can I specify that a particular fault message needs to be returned to the SOAP caller. I can send the response for the SOAP caller using the send step with mode 'Closes S/A bridge'.
I appreciate you inputs.
thx in adv
praveen

Moorthy,
I've the FM in my BPM. But...how can I append this to Response message as these have two different MTs?
Do you mean to say my response message should have a node for fault message data?
I'm trying to implement sth like in this blog <a href="/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client">Propagation of meaningful error information to SOAP Client</a>
To achieve FM in SOAP scenario, should I be using <b>only</b> a non-BPM receiver like a R/3 system using FM with exception as the receiver? Can this be not possible if I use BPM as receiver?
thx in adv
praveen

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

ERROR in SOAP scenario

Similar Messages

Maybe you are looking for