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

Similar Messages

BIC XI Adapter call failed

Hi,
I am working on EDI 850 interface in SAP PI. I am using Seeburger adapter for the EDI data conversion. I am able to convert the data successfully and IDOCs are created successfully.
I am facing the problem in creating the 997 (functional acknowledgment) data. Below is the error message received the receiver communication channel:
Message processing failed. Cause: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: InhouseDocReader doSyntaxCheck(): offset[48]: the found segment Functional_Acknowledgment is not in the message description. DESCRIPTION: InhouseDocReader Error: The Segment Functional_Acknowledgment is missing in the message description. Check your file.
In SXMB_MONI i could able to see the Functional acknowledgment xml data under main document. But it is not getting processed successfully to generate the file.
Am i doing any mistake in configuration? Please help me...
Regards,
Vasantha

Hi Jyoti,
I had a raised a similar case with SAP and came to know that archiving only works if the error raised by the module is so called "Permanent". However, bic doesn't raise permanent error due to which archiving of error files won't be possible. Seeburger haven't came up with a solution yet.
Regards,
Prateek

See Burger Error in BICMODULE-module:Adapter call failed. Reason: null

Hello All,
Scenario IDOC to File using Seeburger BIC problems in in my receiver adapter when converting from XML to EDI.
Error is:
"Message processing failed. Cause: Error in BICMODULE-module:Adapter call failed. Reason: null"
The Seeburger modules used in my receiver adapter:
1     localejbs/CallBicXIRaBean     Local Enterprise Bean     BIC_MT
2     localejbs/CallBicXIRaBean     Local Enterprise Bean     BIC
3     localejbs/Seeburger/FileStore     Local Enterprise Bean     ARCHIVE_EDI
4     CallSapAdapter     Local Enterprise Bean     0
with following module configurations
BIC     destDelimiter     @http://seeburger.com/xi/bic/destDelimiter
BIC     destSourceMsg     source
BIC     destTargetMsg     MainDocument
BIC     dynamicConfiguration     true
BIC     newLine     true
BIC     useAttribIfSet     true
BIC_MT     PartnerLookup     on
BIC_MT     destSourceMsg     MainDocument
BIC_MT     destTargetMsg     MainDocument1
BIC_MT     mappingName     XML_Generic_ANSI_X12_to_DB_MT_OUT
BIC_MT     saveSourceMsg     source
Can some one tell me why there is an Error and what additional module configurations it requires .
Thank you,

Hi,
If possible go to mapping in BIC designer Tool and execute the same by passing your payload there...
if you encounter any errors then there might be a problem with mapping developed...or can be payload..
Also check the parameter used for destSourceMsg source ...is that the source message which contains the payload ?
HTH
Rajesh

Issue with SOAP Adapter calling a Web Service

I have built the Scenario outlined in the webblog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3408. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
I received the following error message in XI Monitoring:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Data.SqlClient.SqlException: Procedure or Function 'Research_GetCompanyIndustry' expects parameter '@Symbol', which was not supplied. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Invesbot.WebService.StockQuotes.GetQuote(String symbol) in c:Inetpubvhostsinvesbot_comwsApp_CodeStockQuotes.cs:line 81 --- End of inner exception stack trace ---</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked the SOAP Adapter which is green. I also checked the webblogs in the XI Forum concerning similar error messges as it doesn't seem to be a new problem. But I didn't find an answer to my issue.
Anybody any idea what could be the issue in this case.
Thanks in advance.
Alex

Hi Alex,
in the mentioned weblog a web service "Distance" is used, but your monitor entry say, that you call the web service "StockQuotes". So I think you have put a wrong URL in your receiver SOAP adapter.
The error comes from the web service server. It says that the request message is wrong. The element "Symbol" is missing.
Regards
Stefan

Testing a "Receiver SOAP Adapter" - Calling a remote webservice from PI

Hi ,
I am trying to call a remote webservice from PI 7.0.
The WSDL file is successfully imported to PI to create the required message types.
The "receiver SOAP adapter" is configured as the communication channel.
I would like to know the ways of testing the remote webservice from PI 7.0.
Thank you,
Panda

Hello there!
I think this link should help you
https://help.sap.com/saphelp_nwpi71/helpdata/en/46/793034608c0ad3e10000000a11466f/frameset.htm
Thanks and regards,
Caio Cagnani

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

How to Send Multiple Attachment by SOAP Adapter

Hi,
How to send multiple attachment by SOAP Adapter.
I am able to send single attachment but at the time of sending multiple attachment i am not able to see in SXMB_moni.
Regards,
Anurag

On the communication channel, please check the 'Do Not Use SOAP envelope' option. Also, please, add the "nosoap" attribute to the SOAP adapter caller. Check the note below for more information
#856597 FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
> "How does the nosoap mode work for the SOAP sender adapter?"

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

SOAP Receiver adapter error. SOAP CALL Failed

Hi ,
I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
SOAP: call failed
SOAP: error occured: java.net.ConnectException: Connection timed out
Message log is as below.
Any clue ?
Thanks & Regards,
Mathew
2005-10-31 18:59:58
Success
output
1130810398454
The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
2005-10-31 18:59:58
Success
output
1130810398458
Using connection AFW. Trying to put the message into the request queue.
2005-10-31 18:59:58
Success
output
1130810398458
Message successfully put into the queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message was successfully retrieved from the request queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message status set to DLNG.
2005-10-31 18:59:58
Success
output
1130810398460
Delivering to channel: CC_CALCULATOR
2005-10-31 18:59:58
Success
output
1130810398564
SOAP: request message entering the adapter
2005-10-31 19:03:07
Success
output
1130810587497
SOAP: call failed
2005-10-31 19:03:07
Error
output
1130810587497
SOAP: error occured: java.net.ConnectException: Connection timed out
2005-10-31 19:03:07
Error
output
1130810587498
Exception caught by adapter framework: Connection timed out

Hi Mathew,
Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
Prasad

Web Service Call with XI fails at SOAP Adapter

Hi,
I am currently trying to call a web service that is located in the Internet via XI using the SOAP Receiver Adapter. In the ABAP Monitoring (SXMB_MONI) the call is successfull. But when I check the Message Monitoring in the Runtime Workench I see the message failed in the SOAP Adapter. It stays in status 'wait' for some time and the shows a system error. I was able to call the Web Service via a SOAP Test Tool, i.e. the service is available and working.
Any ideas why the message fails in the SOAP Adapter? What are the steps to find the root cause?
Thanks and regards.

Hi,
>>>I was able to call the Web Service via a SOAP Test Tool, i.e. the service is available and working.
but does XI have access to internet?
as you used SOAP Test Tool from your computer and not from XI machine
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Call SOAP Adapter from CE BPM failed

Hi everyone,
i have just a problem calling a webservic on the PI 7.11 server from CE 7.2 BPM via SOAP adapter.
1. I've created a very simple scenario on the PI 7.11 Server using SOAP Adapter sender. I've gotten the WSDL URL from the Sender Agreement. It is like the following:
http://piserver:50000/dir/wsdl?p=sa/2e1cf474911939c89c0f5530b24c36f0
2. In the Service Registery of the CE server, I published this service manuelly. The SR created automactically endpoints (http,https) for me. I tested both. They worked very well. While publishing the service, I've also assigned it to the correct system, which has the type IS.
3. I've imported the wsdl into my BPM and assigned it to a automatic activity. I've also created a new service group for this service interface.
4. After deploying the BPM onto the CE server, I've created a new provider system with type IS. In the WS connectivity type, I entered the wsdl url from above again and the admin user on PI server for the Metadata User.
5. I've created a user in the "User Account Management" with connectivity type WS and entered the same user on the step 4 for the Metadata User, assigned this user to the provider system created on step 4.
6. In the "Application Communication", I assigned the provider system from step 4 to the serivce group created on the step 3.
7. Start the BPM and find out a very strange error message:
Error during SCA Processing
[EXCEPTION]
java.rmi.RemoteException: Could not process message for operation SI_SearchSalesOrder_outbound in web service plugin module.; nested exception is:
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://piserver:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=SAP_CE&receiverParty=&receiverService=&interface=SI_SearchSalesOrder_outbound&interfaceNamespace=http%3A%2F%2Fconet.de%2FSalesOrder> returned message <Unauthorized>. Http proxy info: none
I suppose that the metadata user is used to read the wsdl information form PI. For runtime processing maybe should also I provide a user. But I have no idea where I can configure the runtime user in the NWA.
Could some one give me some help on this position?
Thanks a lot in advance.
with best regards
Xiang

Hi Michal,
thanks a lot for your answer. That's also my question. I've provided user to get the meta info for the WS on the CE server. But during the runtime, the BPM on the CE should also have a user to call the soap adapter. Normally we can add the sap-user, sap-pass behind the ws endpoint. But it doesn't work on the CE. Maybe I should use the principle propagation.
thanks a lot for your reply.
with best regards.
Xiang

Error in while calling a Soap Adapter using the UDF

hi,
i am trying to make a call to Soap Adapter using a UDF.
The code of the UDF is as follows :
InputStream isPayloadStream = null;
AbstractTrace trace= container.getTrace();
String sService="Business Component";
String sChannelName="Soap Channel(Sender)";
SystemAccessor accessor=null;
trace.addInfo("entered UDF");
StringBuffer sb = new StringBuffer(" ");
trace.addInfo("creating the reference file");
sb.append("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
sb.append("<ns0:MT_123082_UDF xmlns:ns0=\"http//infosys.com/pi/projects/png/n1\">\n");
sb.append("<INTERCHANGECONTRLNOS>" + var1 + "</INTERCHANGECONTRLNOS>");
sb.append("<PGPARTNERID>"var2"</PGPARTNERID>""\n""</ns0:MT_123082_UDF>");
trace.addInfo("trigerring the SOAP channel ");
try{
Channel channel = LookupService.getChannel(sService,sChannelName);
accessor = LookupService.getSystemAccessor(channel);
isPayloadStream = new ByteArrayInputStream((sb.toString()).getBytes());
trace.addInfo("creating the xml payload ");
XmlPayload payload = LookupService.getXmlPayload(isPayloadStream);
Payload result=accessor.call(payload);
catch (Exception e){
trace.addInfo(e.getMessage());
finally{
if ( accessor !=null) {
accessor.close();
return " ";
The above code is throwing an error while end to end testing.
the scenario is such,while graphical mapping a UDF will be used, which will create an Xml payload, and send this payload to another SOAP to file scenario.
The error in the sxmb_moni is: "Error when calling an adapter by using the communication channel CC_123085_UDF_SOAP_OUT (Party: , Service: BC_123082_REMADV_D96A, Object ID: fa9c6ee15efc30c68ec34b08034d87d1) XI AF API call failed. Module exception: 'failed to set up the channel fa9c6ee15efc30c68ec34b08034d87d1'. Cause Exception: 'Channel stopped by administrative task.'."
Please can anyone suggest how this error can be rectified.
regards,
Meenakshi

Hi,
i have checked the communication channel and the XML. The following error occurs everytime i try to run the scenario.
Error:
Error when calling an adapter by using the communication channel CC_123082_UDFRECEIVER_SOAP_IN (Party: , Service: BC_123082_REMADV_D96A, Object ID: 2a895589066d30d4b2686e9d3a8d4c8d) XI AF API call failed. Module exception: 'SOAP Error'. Cause Exception: 'SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request'
Please let me know how this error can be resolved.
Regards,
Meenakshi

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.

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

SOAP: call failed: java.lang.NullPointerException

Hi,
We are geeting the error in RWB -->
SOAP: call failed: java.lang.NullPointerException
We checked the communication channel and interface and all are working fine.
Can anybody suggest?
Regards,
Akki..................

Hi,
use this link to find the answer..
SOAP adapter
Regards,
Amitanshu

Recvr.CC SOAP Adapter call failed

Similar Messages

Maybe you are looking for