cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Soap Response

Former Member
0 Kudos

Hi Guys,

In the saop scenario i'm working I'm getting a fault message response when i send my soap request to web service.

<u><b>Source Message:</b></u>

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<soapenv:Header>

<ns1:SessionHeader soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns1="urn:enterprise.soap.sforce.com">

<ns1:sessionId>0lmq2S7F_FTxo6OV71b78GysebxKpXppxwwLg6xAE1U8u8VEVrZtrH_pbxqh9WgwrzM0MsEbZXlkWlInFWWPH3ZmHyM=</ns1:sessionId>

</ns1:SessionHeader></soapenv:Header><soapenv:Body><upsert xmlns="urn:enterprise.soap.sforce.com"><externalIDFieldName>SAP_Customer__c</externalIDFieldName><sObjects><ns2:type xmlns:ns2="urn:sobject.enterprise.soap.sforce.com">Account</ns2:type>

<Name xmlns="urn:enterprise.soap.sforce.com"></Name>

<Owner xmlns="urn:enterprise.soap.sforce.com">

<ns3:type xmlns:ns3="urn:sobject.enterprise.soap.sforce.com">User</ns3:type>

<Horizon_User_ID__c>

</Horizon_User_ID__c>

</Owner>

<SAP_Customer__c xmlns="urn:enterprise.soap.sforce.com">

</SAP_Customer__c>

</sObjects>

</upsert>

</soapenv:Body>

</soapenv:Envelope>

<u><b> fault response Message:</b></u>

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sf="urn:fault.enterprise.soap.sforce.com"><soapenv:Body><u><u><b><soapenv:Fault><faultcode>sf:INVALID_TYPE</faultcode><faultstring>INVALID_TYPE: Must send a concrete entity type.</faultstring><detail><sf:fault xsi:type="sf:InvalidSObjectFault"><sf:exceptionCode>INVALID_TYPE</sf:exceptionCode><sf:exceptionMessage>Must send a concrete entity type.</sf:exceptionMessage><sf:row>-1</sf:row><sf:column>-1</sf:column></sf:fault></</b></u></u>detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

Could you please help me by finding a solution to the error message.

Regards

Jithesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jithesh,

there must be soimthing wrong with your Response.

a) On the one hand examine the payload and compare it with the WDSL file (In most cases DATE fields cause problems!)

b) or give the payload to the developer to the WebService (Thats the way I do it :.-).

Regards Mario

Message was edited by:

Mario Müller

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Check the input parameters..

See the below links to get an idea..

Consuming XI Web Services using Web Dynpro – Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii

Consuming XI Web Services using Web Dynpro – Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0d7349b6-0901-0010-ddbe-ec43178a...

/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client

/people/kevin.liu/blog/2006/04/12/wsdl-11-binding-extension-for-soap-12

/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server

/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi

/people/thomas.jung3/blog/2005/05/25/sap-teched-2005--shameless-plug

Troubleshooting SOAP Message - XI - /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

Troubleshooting - RFC and SOAP scenarios-/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

/people/michal.krawczyk2/blog/2005/09/07/xi-why-dont-start-searching-for-all-errors-from-one-place

Regards

Chilla..

Regards

Chilla..