Connection AFW failed, due to: RecoverableException : SOAP Adapter.

Hi All,
We are using XI3.0 Sp14 . the message flow is
IDOC> XI> SOAP ADPATER (receiver side)--> External system.
Here everything is fine, we are using https URL of the extrnal system to send the cXML file on there side. The external URL is fine and working.
When we send the idoc from R/3 to XI. then it gives very common message. I dont know what is wrong with this message. .
Please check this , what I got in Audit log:
2007-04-16 10:14:03 Error Exception caught by adapter framework: null
2007-04-16 10:14:03 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2007-04-16 10:14:03 Success The asynchronous message was successfully scheduled to be delivered at Mon Apr 16 10:19:03 EDT 2007.
2007-04-16 10:14:03 Success The message status set to WAIT.
I don't know why I am getting this error message. Please help me to resolve this. Thanks
regards
Ram Singhal

Hi,
For SOAP receiver adapter, you have the WSDL file from the provider of the webservice, either from a URL link or physically receiving the file.
The WSDL file contains the attribute "location" from the element "address", and the attribute "soapAction" from the element "operation". These 2 values must be entered exactly as is into the SOAP comm chan config.
Also, insure the proxy information are also entered correctly, include the userid/password if required. The webservice provider may also require authentication, so make sure it is also entered.
If possible, execute the webservice using a generic SOAP client tool to test. Use the exact configuration entries as those you used in XI. There are many free tools from the internet.
Regards,
Bill

Similar Messages

Connection AFW failed, due to: Received HTTP response code 500

Hi,
I have tried to develop a file to file scenario in XI 3.0. The Sendor File adapter is reading the file but the message is not getting transfered to Integration engine.
The audit log for the message is as follows:
2005-05-07 04:10:24 Success Channel FileSendor: Send binary file "/tmp/xi_input.dat". Size 324 with QoS EO
2005-05-07 04:10:24 Success Application attempting to send an XI message asynchronously using connection AFW.
2005-05-07 04:10:24 Success Trying to put the message into the send queue.
2005-05-07 04:10:24 Success Message successfully put into the queue.
2005-05-07 04:10:24 Success The application sent the message asynchronously using connection AFW. Returning to application.
2005-05-07 04:10:24 Success Confirmation mode test found. File will be resent next time
2005-05-07 04:10:24 Success The message was successfully retrieved from the send queue.
2005-05-07 04:10:24 Success The message status set to DLNG.
2005-05-07 04:10:24 Error Transmitting the message to endpoint http://nadcp517:8020/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
Any suggestion...

hi
This problem comes due to the post installation steps might be at the time of post installation some wrong might be done.
step1 : In sxmb_adm configure the integration server by giving the path as http://<host>:<abapport>/sap/xi/engine?type=entry
step 2 : Check ur business system created at the time of post installation there u need to main the path as it as above.
Reward points if useful,
Regards,
Srinivas.D

Webservice and BPM; connection AFW failed

I have created the following integration process:
1. Asynchronous receive step of a xml file;
2. Synchronous send step to invoke webservice;
3. Asynchronous send step of the response file.
In this process XI will read a xml file from a directory on the server, convert this file to a SOAP request, call the webservice and convert the SOAP response to a xml file. This file is then sent to the same server directory.
When I look in SXMB_MONI the whole process is set to ok. The response of the webservice is in the payload of the XI response message. (This is the message from my integration process to the inbound message interface.).
But the response file never reached its destination.
When I look at the file adapter monitor it reports: "Up and running - no message processing until now".
And when I look at the message monitoring, there are the following messages:
2005-07-29 11:30:55 Success The message was successfully received by the messaging system.
Profile: XI URL: http://nthvsnw4:50000/MessagingSystem/receive/AFW/XI
2005-07-29 11:30:55 Success Using connection AFW. Trying to put the message into the receive queue.
2005-07-29 11:30:55 Success Message successfully put into the queue.
2005-07-29 11:30:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:30:55 Success The message status set to DLNG.
2005-07-29 11:30:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:30:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:35:55 CEST 2005.
2005-07-29 11:30:55 Success The message status set to WAIT.
2005-07-29 11:35:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:35:55 Success The message status set to DLNG.
2005-07-29 11:35:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:35:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:40:55 CEST 2005.
2005-07-29 11:35:55 Success The message status set to WAIT.
2005-07-29 11:40:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:40:55 Success The message status set to DLNG.
2005-07-29 11:40:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:40:55 Success The asynchronous message was successfully scheduled to be delivered at Fri Jul 29 11:45:55 CEST 2005.
2005-07-29 11:40:55 Success The message status set to WAIT.
2005-07-29 11:45:55 Success The message was successfully retrieved from the receive queue.
2005-07-29 11:45:55 Success The message status set to DLNG.
2005-07-29 11:45:55 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-07-29 11:45:55 Error The message status set to NDLV.
I looked at several postings with the subject "Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException", but I could not find any which seems to meet my problem.
I would highly appreciate any help on this.

Sorry for my late response, but I did not look at this after it was solved and I did not receive any mail. So please let me know if you still need some support.
I could send you a document with some screen shots. If so send me an email ([email protected])

Entry using connection AFW failed

Hi,
I am trying to read an external file and push it in to R/3 by calling RFC using XI.
I configured everything.
File and RFC adapters are working fine.
After processing as per settings it is deleting the file but it is not pushing in to R/3.
In the Audit log i am getting the following messsages:
1.Success>Send binary file "tom.xml" from FTP server "entegdt27:XIshared", size 140 bytes with QoS EO
2.Success>Application attempting to send an XI message asynchronously using connection AFW.
3.Success>Trying to put the message into the send queue.
4.Success>Message successfully put into the queue.
5.Success>The application sent the message asynchronously using connection AFW. Returning to application.
6.Success>The message was successfully retrieved from the send queue.
7.Success>File "tom.xml" deleted after processing
8.Success>The message status set to DLNG.
9.Error>Transmitting the message to endpoint http://entegdt27:8000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500..
10.Success>The asynchronous message was successfully scheduled to be delivered at Tue Dec 06 09:39:01 IST 2005.
During retry the same error(9) is repeating.
Can Anyone Help.
Thanks in Advance

Hi Chemmam,
       The file adapter is picking up the file and deleting the same.The problem should be in mapping or the receiver adapter configuration.
Check the following things.
        1.In design time(repository) check whether the mapping between the two data types are perfect.Check the same by using test tab and execute option.
        2.Then go to the reciver SAP r/3 business system and go to transaction SM59.Check whether the a connection is established between the receiver system and the Intergration server.
          Create connections by giving the log on parameters of the XI server and the program ID and test the connection.
        3.If the test connection is perfect , then go to receiver R3 system and try executing the RFC as stand alone by giving appropriate inputs.
        4.If that is working fine.Then check for your configuration settings.The Comunication channel between XI and Receiver SAP R/3 should be under the SLD registered business system while the sender communication channel(File adapter) should be under a service.
         5.In receiver communication channel check for the log on parameters of the receiver SAP system.
      Hop this helps you in locating the root cause.
regards,
aravindh.

Connection afw failed

hi gurus,
i getting an error msg " transmitting the message to endpoint http://hostname:8000/sap/xi/engine?type=entry using connection AFW failed ,due to com.sap.aii.af.ra.ms.runtime:clusterexception: serverinternal locking not avaliable"
With Regards,
Shakthi Raj N.

Hi, I'm experiencing the same problem.. how did you solved it?
Thanks in advance for your help
Sonia

Connecting XI with other XI using SOAP adapter, is it possible?

Hi all,
I know that for connection between XIs is recommended using XI connectivity adapter. But I want to send/receive messages trough other XI outside of my network and Im thinking using SOAP adapter for effect. Is it possible?
Thanks in advance.
Cheers,
Ricardo.

Yes, it is. But why? Both are SOAP messages based on HTTP.
Regards
Stefan

AFW: Failed to transmit message due to RecoverableException

Hi all,
I use a XI 3.0 SP 14.
I've created a BPM with 3 steps:
1) receive step
2) send synchronous step
3) send asynchronous step
XI exposes a Asynchronous Message Interface as a Web Service. Than the BPM uses this information to send a synchronous call to a Web Service (this WS is created from an EJB and deployed on a SAP Web AS 6.40). Than the BPM uses the WS response to send an asynchronous mail.
In the SXI_MONITOR everything works fine, but in the message monitor (Messages from the Adapter Framework) I get this error when I try to send an e-mail (step 3):
2005-11-08 15:22:25 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapadx01:51600/MessagingSystem/receive/AFW/XI
2005-11-08 15:22:25 Success Using connection AFW. Trying to put the message into the receive queue.
2005-11-08 15:22:25 Success Message successfully put into the queue.
2005-11-08 15:22:25 Success The message was successfully retrieved from the receive queue.
2005-11-08 15:22:25 Success The message status set to DLNG.
2005-11-08 15:22:25 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2005-11-08 15:22:25 Success The asynchronous message was successfully scheduled to be delivered at Tue Nov 08 15:27:25 CET 2005.
2005-11-08 15:22:25 Success The message status set to WAIT.
2005-11-08 15:27:25 Success Retrying to deliver message to the application. Retry: 1
In the default trace I can see:
Failed to transmit message 436f38c9-0617-022e-0200-00000ab44471(INBOUND) due to com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
java.lang.NullPointerException
     at com.sap.aii.af.service.alerting.Alert.getInputInterface(Alert.java:330)
     at com.sap.aii.af.service.alerting.Alert.send(Alert.java:103)
     at com.sap.aii.af.service.alerting.Alert.run(Alert.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
I don't have this problem if instead of SOAP Synchronous call I do an RFC Synchronous call (on step 2)
I also get a mail (step 3) if I have a System Error Exception in the SOAP synchrounous call (step 2)
I have also noticed that:
when I call the mail adapter (asynchronous step) with the Web Service Response in the HEADER I've got the ACK field:
<SAP:Ack xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Status>OK</SAP:Status>
<SAP:Category>permanent</SAP:Category>
</SAP:Ack>
Instead if I call the mail adapter (asynchronous step) with the BAPI Response in the HEADER I haven't got the ACK field.
But in the BPM send Asynchronous step the "acknowledgement" parameter is set to NONE
Could you please help me?
Best Regards,
Paolo

Ops... the note will be released in the near future...
Anyway my problem was that the response message from the SOAP Receiver Adapter included the XI Ack header for any successfull response message. Then, when I tried to send an asynchronous request message to the Mail Receiver Adapter it was not able to manage this ACK.
Best Regards,
Paolo

Unable to find channel ID at inbound SOAP Adapter

Hi experts,
I encountered a very puzzling problem:
I have a scenario:
IDOC -> XI -> SOAP
For 2 interfaces of such nature, 1 works fine, 1 doesn't.
The one that does not work is throwing the following error in RWB - Message Display Tool (MDT):
2007-03-22 10:57:05 Success The message was successfully received by the messaging system. Profile: XI URL: http://ootspdbs02:50100/MessagingSystem/receive/AFW/XI
2007-03-22 10:57:05 Success Using connection AFW. Trying to put the message into the receive queue.
2007-03-22 10:57:06 Success Message successfully put into the queue.
2007-03-22 10:57:06 Success The message was successfully retrieved from the receive queue.
2007-03-22 10:57:06 Success The message status set to DLNG.
<b>2007-03-22 10:57:06 Error Unable to find channel ID
2007-03-22 10:57:06 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: a277e57c-c837-e44f-9ae2-da0d701980c4. </b>
2007-03-22 10:57:06 Success The asynchronous message was successfully scheduled to be delivered at Thu Mar 22 10:58:06 SGT 2007.
2007-03-22 10:57:06 Success The message status set to WAIT.
In SXMB_MONI, it shows the message has been processed successfully - indicating that the mapping is fine. Status = Awaiting acknowledgement.
I've looked up the forums, and the general solution offered is to refresh the SLD cache.
I've tried that, but it doesn't work.
Please help.
Thanks.
Ron

> hmm.. then things not a problem with the cache.
> Is the error in MONI? Or is it in the Adapter Engine?
>
>
> I know it isrepeatitive, but checking if the Objects
> are all active and correct in the ID is the only
> solution I can suggest.
>
> Regards
> Bhavesh
In the MONI, the status is successful, awaiting acknowledgement.
After sometime, the ack status will be "Acknowledgement contains System Errors"
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_ROUTING_BACK_ERROR</SAP:Code>
<SAP:P1>,BS_DEV1_NAUTICUS_OOTS</SAP:P1>
<SAP:P2>,BS_NHGDDBS01,,</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error occurred during back-routing Error in communication channel</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
But I don't think these are related, because the message wasn't sent out, naturally there's an error in the ack.

SOAP Adapter: Exception in method process

Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!

Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error.

Messages failing in the SOAP adapter with the errror

HI
I am getting the below error in the SOAP adapter monitoring . can any body tell what does "No route to host: Connect" mean .
could some one help us on resolving this .
Error Exception caught by adapter framework: No route to host: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect. Setting message to status failed.
Error The message status set to FAIL.
Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect.
thanks and regards
sandeep

Hi!
First please confirm whether you are working on XI or PI 7.1 ?
because in XI you need to generate WSDL manaually via Tools>Define Web service-Giving Input..and in XI you need to test the SOAP scenario from external tool like Altova xml spy tool kit or else SOAP client tool.
In PI 7.1::
You can publish directly the web service in the SERVICE REGISTRY from sender agreement onwards.
once it is published you can check the status on your interface in service registry as CONFIGURED..Okay
Here you can test directly in service registry...
According to your error check ocne agan even though you gone through all the steps..
1. Check whether the SOAP service is active or not in SICF>SAP>bc>XI>Service-->SOAP.
2. sicne after generating wSDL u can get one url right that URL itself acts as a gateway to enter the source data into XI..
lets give to the source team to try with XI super uID adn PWD as authentification.
3. Also please STOP ur communication Channel and start once again.
4. Please check whether the WEB Service is configured correctly or not.
Regards::
Amar Srinivas Eli

PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

We are exposing a webservice through SAP PI. Occassionaly we have customers calling our webservice and some failure occurs. The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..). Generally in these cases we can see the error in communication channel monitoring.
Here is an example:
12/12/11 4:39:07 PM com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
12/12/11 4:39:06 PM request received for a channel
I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails. The communication channel will show a SUCESSFUL message payload with a link to it. But it does not show a failed one.
Where can I find the FAILED payload that accompanies this message? These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring... I did some searching around, but did not find anything offhand. I would greatly appreciate any pointers from anyone who has crossed this bridge.

Hi,
When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

SOAP Adapter XI 3.0 - HTTP 200 response fails

We have a scenario where a request message is sent successfully to a URL by the SOAP Adapter.
However, the response message has an HTTP response of 200 (meaning ok) which is not handled correctly by the
SOAP Adapter.
The error text shown in SXMB_MONI is:
com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint HTTP 200 OK
Is there something I am missing in the configuration to allow HTTP responses in the SOAP Adapter ? It is very odd that the SOAP Request works fine, but the SOAP Response does not.
Any ideas anyone ?
Kind regards
Colin.

Hi Bill
1. synchronous out / in
2. yes
3. working fine
following the way out to the elocateserver system is working fine.
The soap is working and the responce from the elocteserver is fine . But when the message is pick put the Timeout show up.
below is the Responce from elocateserver to xi
Hope this will help you
thanks olaf
Help
!http://sapnt09:50200/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://sapnt09:50200/sap/public/icman/img/theme.jpg!
500 Connection timed out
Connection timed out (-5)
Error:
-5
Version:
6040
Component:
ICM
Date/Time:
Sat Oct 16 06:13:25 2004
Module:
icxxthr.c
Line:
2556
Server:
sapnt09_M64_02
Detail:
Connection to partner timed out
© 2001-2003, SAP AG

SOAP Adapter recvr.CC unable to call, call failed

Hi,
i'm doing the IDoc to SOAP Scenario for Vendor Master. Sender CC is IDoc Adapter & Receiver CC is SOAP Adapter. Sending the vendor data(SAP ECC) to third party(through WebService) system. In the recv.CC,
in the Connection Parameters>Target URL->i've given the URL given by third party (which is working fine when i open in explorer), & below in Conversion Parameters>SOAP Action also i've given. After sending the vendor from ECC by BD14, it is not received in Webservice.
In the Runtime Workbench,
Component Monitoring-->Communication Channel Monitoring
--> for my recv.SOAP CC, it is showing the error as:
MsgID:----
Explanation
98719886-dbc5-194c-9da7-0cfe8d77082c call failed
98719886-dbc5-194c-9da7-0cfe8d77082c request entering
URL is working fine in the browser.
SOAP Action is rightly given.
Webservice not requires any logon data, so not configured User Authentication.
No Proxy settings we are using.
How to verify about firewall and ports to send SOAP message out of XI Box or network
Any other settings or configurations i've to do in XI system?
what might be the reason for this error. Experts pls help in resolving the same.
rgds,
balu

hi,
thanks for the quick reply..
It is showing:
Status:red symbol
Adapter Type: SOAP
Direction: Receiver
In cluster Node tab,
Processing Errors: in the last 20 hours
Short Log: active
MsgID:----
Explanation
98719886-dbc5-194c-9da7-0cfe8d77082c----- call failed
98719886-dbc5-194c-9da7-0cfe8d77082c----- request entering
Above already i've given the in recvr.CC what & all entered. pls do the needful.
tnx n rgds,
balu

Recvr.CC SOAP Adapter call failed

Hi,
i'm doing the IDoc to SOAP Scenario for Vendor Master. Sender CC is IDoc Adapter & Receiver CC is SOAP Adapter. Sending the vendor data(SAP ECC) to third party(through WebService) system. In the recv.CC,
in the Connection Parameters>Target URL->i've given the URL given by third party (which is working fine when i open in explorer), & below in Conversion Parameters>SOAP Action also i've given. After sending the vendor from ECC by BD14, it is not received in Webservice.
In the Runtime Workbench,
Component Monitoring-->Communication Channel Monitoring
--> for my recv.SOAP CC, it is showing the error as:
MsgID:----
Explanation
98719886-dbc5-194c-9da7-0cfe8d77082c call failed
98719886-dbc5-194c-9da7-0cfe8d77082c request entering
what might be the reason for this error. Experts pls help in resolving the same.
Thanks & Regards,
Balaji

hi,
thanks for the quick reply..
URL is working fine in the browser.
SOAP Action is rightly given.
No Proxy settings we are using.
your third point:
Also verify about firewall and ports to send SOAP message out of XI Box or network
i did't get. pls elaborate. Any other settings or configurations i've to do in XI system?
Thanks & Regards,
Balaji

Following message failing in sender soap adapter

Hi all,
The message below fails when it is sent to our adapter with a 500 error from a webmethods server. however if I pull the soap message out of the mime, and use our client test tool, it posts fine.
What is wrong with the message below?
Message-ID:<28413146.1155935375732.JavaMail.webmethods@exshaw>
MIME-Version: 1.0
Content-Type: multipart/related; type="text/xml"; boundary=X-K12456234-X
X-K12456234---X
content-type: text/xml;charset=UTF-8
content-transfer-encoding: 7bit
Content-ID: <SES>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"></SOAP-ENV:Header>
<SOAP-ENV:Body>
<nr1:ServiceAcknowledgementRequest xmlns:nr1="http://sap.com/xi/SAPGlobal/Global">
        <MessageHeader>
                <ID schemeID="0240">74000003400000000020060329170547</ID>
                <CreationDateTime>2006-03-29T17:05:47Z</CreationDateTime>
                <SenderParty>
                        <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">6000000011</InternalID>
                </SenderParty>
                <RecipientParty>
                        <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">0000000236</InternalID>
                </RecipientParty>
        </MessageHeader>
        <ServiceAcknowledgement>
                <ID schemeAgencyID="SSR_100" schemeAgencySchemeAgencyID="ZZZ">7400000340</ID>
                <BuyerID>7400000340</BuyerID>
                <CreationDateTime>2006-03-29T17:03:55Z</CreationDateTime>
                <Note>Service Entry Sheet#1</Note>
                <Item>
                        <ID>10</ID>
                        <Quantity unitCode="EA">5.0</Quantity>
                        <Product>
                                <TypeCode>1</TypeCode>
                                <Note>Test Service</Note>
                        </Product>
                        <Price>
                                <NetUnitPrice>
                                        <Amount currencyCode="USD">1.0</Amount>
                                     <BaseQuantity unitCode="EA">1.0</BaseQuantity>
                               </NetUnitPrice>
                       </Price>
                       <PurchaseOrderReference>
                               <ID>2000000742</ID>
                               <ItemID>1</ItemID>
                       </PurchaseOrderReference>
                </Item>
        </ServiceAcknowledgement>
</nr1:ServiceAcknowledgementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
X-K12456234---X

Hi Richard,
I think, it is because of the Autorization Problem..i.e
Webservice is not able to execute by SOAP adapter.. So Security Roles etc..
Check this SAP SOAP Note for FAQ-856597 (Question No 1)
A similar symptom is mentioned in this note....
Regards,
Abhy

Connection AFW failed, due to: RecoverableException : SOAP Adapter.

Similar Messages

Maybe you are looking for