Error in Consuming Webservice in ABAP

Hello Experts,
I am very new to webservices in ABAP. just to test the webservice within ABAP, I created a Service Definition which gave me a WSDL URL using the Provider wizard. then I generated proxy class to consume the WSDL URL generated in previous step . I am calling the proxy class within a program as below. It is raising a exception CX_AI_SYSTEM_FAULT . Does anyone have idea what this could be and how to correct it?
   TRY.
              CALL METHOD TEST->ZTESSTHJKJH
                EXPORTING
                  INPUT = INPUT
                IMPORTING
                  OUTPUT = output
               CATCH CX_AI_SYSTEM_FAULT .
               CATCH CX_AI_APPLICATION_FAULT .
              ENDTRY.
Thanks,
Harkamal

Hi Harkamal,
It seems that the webservice provider and consumer are on the same server (loopback). It's probably releated with network access. You can follow SAP Note Number 1009109 (Analyzing Web service problems using the ICF recorder) to track down the sent and received soap messages . Alternatively, you can download and use "Webservice Studio", a small freeware program to test the webservice easily. Official website is: [http://webservicestudio.codeplex.com/]
Good luck,
Ozcan.

Similar Messages

Error in consuming webservices using ABAP

Dear Gurus,
I am trying to consume webservices using ABAP. We dont have XI installed and no java instance installed.
I created a customer proxy through SE80 and generated a proxy class by giving a WSDL link and also defined logical port. Traditionally followed the steps. But while testing webservices , I get a ICF error.
The error is as follows:
SOAP : 1:023 SRT : Processing error in internet communication framework ("ICF error when recieving the response ICM_HTTP_CONNECTION_FAILED)
Please let me know the cause of this error and solution to be provided.
I also tried to call the method from an abap program, But I get CX_AI_SYSTEM_FAULT exception.
Awaiting your replies.
Thanks in advance for your support and valuable time.
Thanks
Gurushanthi

Hi Gurushanthi,
It could one of several problems, examples:
- A firewall setting
- http communication out disabled by Basis team or
- The logical port wasn't configured correctly.
Try the suggestions in this thread to narrow down the reason (particularly the telnet test from the server):
[Re: Error testing external web service ICM_HTTP_CONNECTION_FAILED;
Regards, Trevor

Soapfaultcode:1 Error when consuming webservice through abap proxy class

Hi All,
I am facing a issue executing a proxy class created by consuming web service.
I have consumed a web service which queries data from oracle server to process them in SAP.We have created a Proxy class and did the following configurations:
1) Created a logical port using SOAMANAGER
2) In SICF t-code we have selected No proxy setting for local server.
But when we execute the proxy class it gives an error as "SoapFaultCode:1'.
Regards,
Madhu.

Hi Madhu,
Please tel us how u have solved it. I am also facing this problem.
I am trying to understand this problem description 'SOAP ACTION name by definition of the logical port.' via the thread Re: Get error "SoapFaultCode:1"Consume web service in ABAP proxy - But couldn't able to understand how to do this.
Thank You,
Regards,
Naresh.

Consuming Webservice in ABAP: SoapFaultCode:1

Hi,
I have created a webservice with NetweaverDeveloperStudio and deployed it to a J2EE. I tested it with the "NDS-Webservice-Tester" and it worked fine.
I then created a proxy following the section for WebAS 640 in the weblog of Thomas Jung:
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
When using the "test-interface" function in SE80 (also described in Thomas weblog) I get the following result:
<CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SoapFaultCode:1</CODE>
<ERRORTEXT>
000D6019F1DD004000000036000020D8000405473991B26F:
Found 0 operation definitions using keys:
Key name:'first-body-element-ns'
key value: 'urn:EdilogUserManagementWebserviceWsd/EdilogUserManagementWebserviceVi/document';
Key name:'SoapRequestWrapper'
key value:'getCompany';
</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
Any idea what might cause this error? Is there a list with the SoapErrorCodes and their specific meanings?
Thanks and regards
Jan Hempel

I solved the problem "accidentally": The name of the Webservice was to long! Changing the name from "EdilogUserManagementWebservice" to "UserManagement" did the trick.
This is probably due to the restricted fieldlength of ABAP-programnames.
Regards
Jan Hempel

Error in Consuming Webservice

Hi Expert,
I have a problem in consuming webservice into my client proxy.
when I test the client proxy it will raise error :
SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
Does anyone here has facing this problem too.
And how to solve it.
Need your advice please.
Regards,
Ikrar

Solved by thread Re: Get error "SoapFaultCode:1"Consume web service in ABAP proxy

Error in Consuming webservice proxy in SAP

Hi,
I have a webservice which I am not able to consume in SAP. I get an error 'Cannot generate Proxy (object <attribute name="arrayType"> missing in WSDL, see long text').
When i tried to search in SDN, I found a post which says that SAP doesnt support soapenc:Array types and it can be converted to corresponding Sequence. I went through the help link
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/frameset.htm
which has a link which shows an example.
Accordingly, I have changed mine from:
- <schema targetNamespace="https://tserver.perfectcompliance.com/4DSOAP/LLX_Guardian" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
- <complexType name="ArrayOfstring" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
- <complexContent>
- <restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="xsd:string[]" />
</restriction>
</complexContent>
</complexType>
</schema>
To:
- <schema targetNamespace="https://tserver.perfectcompliance.com/4DSOAP/LLX_Guardian" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
- <complexType name="ArrayOfstring">
- <sequence>
<element name="item" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
</schema>
After doing the above changes, I am able to consume webservice and create a proxy but it's not working. When i execute any method which is using the Arrayofstring, it gives me an error:
Complex Types cannot be parsed.
Is my above change in XML wrong. Do I need to do any other changes.
Regards,
Nikhil

Anyone has any idea on how to solve this issue?

Getting error while consuming webservices

Hi Colleagues,
In our application we are calling External webservice through WSDL file. I have deployed the WSDL files on server and get the WSDL URL using "WDURLGenerator.getAbsoluteWebResourceURL(wdComponentAPI.getDeployableObjectPart(), "file.wsdl")". I am able to call the service from WS Navigator.
I have consumed webservices uisng Adaptive webservice model and given the service group configuration ,created a provider system, assigned the provider system to the application through SOA Management-->Application Communication
Now when i tried to run the webdynpro application i am getting following error
Could anyone please let me know how to overcome this?
Exception i am facing is given here:
com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: BORM_SWDC_API_SLM_SP_GET_DLPortType using destination : dwd.SystemHome.50000
    at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:198)
    at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getEndpointConfigurations(DestinationsHelperImplSoa.java:1448)
    at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getWSDLUrl(DestinationsHelperImplSoa.java:1025)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:578)
    at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:338)
    ... 76 more
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'BORM_SWDC_API_SLM_SP_GET_DLPortType_service_sap_com_BASIC' and application name 'demo.sap.com/softcomp'. Check mass configuration has been done properly.
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:522)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:435)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:403)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:381)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:317)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:292)
at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:68)
at com.sap.demo.softcomp.model2.Model2.<init>(Model2.java:63)
at com.sap.demo.softcomp.softcomp.comp.SoftcompComp.wdDoInit(SoftcompComp.java:127)
at com.sap.demo.softcomp.softcomp.comp.wdp.InternalSoftcompComp.wdDoInit(InternalSoftcompComp.java:266)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:253)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:553)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1338)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:74)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:252)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:677)
... 48 more
Caused by: com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: BORM_SWDC_API_SLM_SP_GET_DLPortType using destination : dwd.SystemHome.50000
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getEndpointConfigurations(DestinationsHelperImplSoa.java:1459)
at com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa.getWSDLUrl(DestinationsHelperImplSoa.java:1025)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.getWSDLUrl(GenericServiceFactory.java:578)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:338)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:321)
at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:282)
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:514)
... 73 more
Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.ObjectNotExistsException: BORM_SWDC_API_SLM_SP_GET_DLPortType using destination : dwd.SystemHome.50000
at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSEndpoints(WSQueryImpl.java:198)
Please let me know how to overcome this?
Thanks in Advance
Regards
Swetha

Hi Swetha,
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'BORM_SWDC_API_SLM_SP_GET_DLPortType_service_sap_com_BASIC' and application name 'demo.sap.com/softcomp'. Check mass configuration has been done properly.
some configurations for consuming services using service group is missed out.
check this article for consuming service :
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50d70a19-45a3-2b10-bba0-807d819daf46]
Thanks and Regards

Consuming webservice in ABAP Webdynpro

Hi all,
I am using SAP ECC 5.0.Can I consume External webservices using ABAP Dynpro.Sending related links will be highly appreciated.
Regards
Sandeep.S

the thread is marked as answered? is it resolved or are you still looking for an answer

Exception error: While consuming webservice

While trying to consume webservice from other server. We get the following error
"I/O Exception: Name in certificate 'URL' does not match host name 'URL'
The code works fine in development environment. Whereas, when we are trying to consume with/without the port number as 443 using cfhttp method. It is throwing the above error.
Environment :
Coldfusion 8
SQL Server 2005
Which we are consuming is :
Java/J2EE.
Can you please help us? If you require any other details kindly let me know.
Thanks,
Satheesh.

Try setting the resultFormat on your HTTPService to e4x.
HTH;
Amy

Consume webservice from ABAP : SoapFaultCode:4

Hi ,
    I need your valuable ideas in overcoming the problem mentioned below.
    This problem relates to consumption of a webservice from ABAP - Client Proxy without XI. The system is WAS 6.40.
I had created a client proxy (along with the corresponding methods) using a WSDL file pasted below. I had also created a logical port for the proxy class generated.
When I test the interface for one of the methods , I get the following error message.
<u>Error Message</u>
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o103" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o103">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>193</PROGID>
<CONTID>1050</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT>http://www.sap.com/xml_errorcodes</CODECONTEXT>
<CODE>SoapFaultCode:4</CODE>
<ERRORTEXT>System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: //10.136.129.245/PinnacleWebServices/DatabaseAvailable. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
<u>WDSL file used for creating the Client Proxy</u>
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="//10.136.129.245/PinnacleWebServices" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="//10.136.129.245/PinnacleWebServices" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:types>
      <s:schema elementFormDefault="qualified" targetNamespace="//10.136.129.245/PinnacleWebServices">
         <s:element name="DatabaseAvailable">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="DatabaseAvailableResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="DatabaseAvailableResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddCustomers">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddCustomersResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddCustomersResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddContracts">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddContractsResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddContractsResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddInstalledEquipment">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddInstalledEquipmentResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddInstalledEquipmentResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddProducts">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddProductsResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddProductsResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddCreditAlerts">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
                  <s:element minOccurs="1" maxOccurs="1" name="bool_updatecustomers" type="s:boolean" />
                  <s:element minOccurs="1" maxOccurs="1" name="bool_updatecontracts" type="s:boolean" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddCreditAlertsResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddCreditAlertsResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddStockFigures">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="s_dbalias" type="s:string" />
                  <s:element minOccurs="0" maxOccurs="1" name="s_xml" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="AddStockFiguresResponse">
            <s:complexType>
               <s:sequence>
                  <s:element minOccurs="0" maxOccurs="1" name="AddStockFiguresResult" type="s:string" />
               </s:sequence>
            </s:complexType>
         </s:element>
         <s:element name="string" nillable="true" type="s:string" />
      </s:schema>
   </wsdl:types>
   <wsdl:message name="DatabaseAvailableSoapIn">
      <wsdl:part name="parameters" element="tns:DatabaseAvailable" />
   </wsdl:message>
   <wsdl:message name="DatabaseAvailableSoapOut">
      <wsdl:part name="parameters" element="tns:DatabaseAvailableResponse" />
   </wsdl:message>
   <wsdl:message name="AddCustomersSoapIn">
      <wsdl:part name="parameters" element="tns:AddCustomers" />
   </wsdl:message>
   <wsdl:message name="AddCustomersSoapOut">
      <wsdl:part name="parameters" element="tns:AddCustomersResponse" />
   </wsdl:message>
   <wsdl:message name="AddContractsSoapIn">
      <wsdl:part name="parameters" element="tns:AddContracts" />
   </wsdl:message>
   <wsdl:message name="AddContractsSoapOut">
      <wsdl:part name="parameters" element="tns:AddContractsResponse" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentSoapIn">
      <wsdl:part name="parameters" element="tns:AddInstalledEquipment" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentSoapOut">
      <wsdl:part name="parameters" element="tns:AddInstalledEquipmentResponse" />
   </wsdl:message>
   <wsdl:message name="AddProductsSoapIn">
      <wsdl:part name="parameters" element="tns:AddProducts" />
   </wsdl:message>
   <wsdl:message name="AddProductsSoapOut">
      <wsdl:part name="parameters" element="tns:AddProductsResponse" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsSoapIn">
      <wsdl:part name="parameters" element="tns:AddCreditAlerts" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsSoapOut">
      <wsdl:part name="parameters" element="tns:AddCreditAlertsResponse" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresSoapIn">
      <wsdl:part name="parameters" element="tns:AddStockFigures" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresSoapOut">
      <wsdl:part name="parameters" element="tns:AddStockFiguresResponse" />
   </wsdl:message>
   <wsdl:message name="DatabaseAvailableHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
   </wsdl:message>
   <wsdl:message name="DatabaseAvailableHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddCustomersHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddCustomersHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddContractsHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddContractsHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddProductsHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddProductsHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
      <wsdl:part name="bool_updatecustomers" type="s:string" />
      <wsdl:part name="bool_updatecontracts" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresHttpGetIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresHttpGetOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="DatabaseAvailableHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
   </wsdl:message>
   <wsdl:message name="DatabaseAvailableHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddCustomersHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddCustomersHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddContractsHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddContractsHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddInstalledEquipmentHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddProductsHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddProductsHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
      <wsdl:part name="bool_updatecustomers" type="s:string" />
      <wsdl:part name="bool_updatecontracts" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddCreditAlertsHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresHttpPostIn">
      <wsdl:part name="s_dbalias" type="s:string" />
      <wsdl:part name="s_xml" type="s:string" />
   </wsdl:message>
   <wsdl:message name="AddStockFiguresHttpPostOut">
      <wsdl:part name="Body" element="tns:string" />
   </wsdl:message>
   <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesSoap">
      <wsdl:operation name="DatabaseAvailable">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
         <wsdl:input message="tns:DatabaseAvailableSoapIn" />
         <wsdl:output message="tns:DatabaseAvailableSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
         <wsdl:input message="tns:AddCustomersSoapIn" />
         <wsdl:output message="tns:AddCustomersSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
         <wsdl:input message="tns:AddContractsSoapIn" />
         <wsdl:output message="tns:AddContractsSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
         <wsdl:input message="tns:AddInstalledEquipmentSoapIn" />
         <wsdl:output message="tns:AddInstalledEquipmentSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
         <wsdl:input message="tns:AddProductsSoapIn" />
         <wsdl:output message="tns:AddProductsSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
         <wsdl:input message="tns:AddCreditAlertsSoapIn" />
         <wsdl:output message="tns:AddCreditAlertsSoapOut" />
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
         <wsdl:input message="tns:AddStockFiguresSoapIn" />
         <wsdl:output message="tns:AddStockFiguresSoapOut" />
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpGet">
      <wsdl:operation name="DatabaseAvailable">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
         <wsdl:input message="tns:DatabaseAvailableHttpGetIn" />
         <wsdl:output message="tns:DatabaseAvailableHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
         <wsdl:input message="tns:AddCustomersHttpGetIn" />
         <wsdl:output message="tns:AddCustomersHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
         <wsdl:input message="tns:AddContractsHttpGetIn" />
         <wsdl:output message="tns:AddContractsHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
         <wsdl:input message="tns:AddInstalledEquipmentHttpGetIn" />
         <wsdl:output message="tns:AddInstalledEquipmentHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
         <wsdl:input message="tns:AddProductsHttpGetIn" />
         <wsdl:output message="tns:AddProductsHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
         <wsdl:input message="tns:AddCreditAlertsHttpGetIn" />
         <wsdl:output message="tns:AddCreditAlertsHttpGetOut" />
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
         <wsdl:input message="tns:AddStockFiguresHttpGetIn" />
         <wsdl:output message="tns:AddStockFiguresHttpGetOut" />
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:portType name="Pinnacle_x0020_Web_x0020_ServicesHttpPost">
      <wsdl:operation name="DatabaseAvailable">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Checks if a connection to the selected database is available.</documentation>
         <wsdl:input message="tns:DatabaseAvailableHttpPostIn" />
         <wsdl:output message="tns:DatabaseAvailableHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Customers within Service Director</documentation>
         <wsdl:input message="tns:AddCustomersHttpPostIn" />
         <wsdl:output message="tns:AddCustomersHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Contracts within Service Director</documentation>
         <wsdl:input message="tns:AddContractsHttpPostIn" />
         <wsdl:output message="tns:AddContractsHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Installed Equipment within Service Director</documentation>
         <wsdl:input message="tns:AddInstalledEquipmentHttpPostIn" />
         <wsdl:output message="tns:AddInstalledEquipmentHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add or Update Products within Service Director</documentation>
         <wsdl:input message="tns:AddProductsHttpPostIn" />
         <wsdl:output message="tns:AddProductsHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Credit Alerts to Customers and/or Contracts within Service Director. Warning - Will remove all credit alerts first as it assumes a full list is provided every time.</documentation>
         <wsdl:input message="tns:AddCreditAlertsHttpPostIn" />
         <wsdl:output message="tns:AddCreditAlertsHttpPostOut" />
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <documentation xmlns="http://schemas.xmlsoap.org/wsdl/">Add Stock Figures to mobile_data_connector within Service Director in order that the PDA get updated.</documentation>
         <wsdl:input message="tns:AddStockFiguresHttpPostIn" />
         <wsdl:output message="tns:AddStockFiguresHttpPostOut" />
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesSoap" type="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
      <wsdl:operation name="DatabaseAvailable">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/DatabaseAvailable" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCustomers" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddContracts" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddInstalledEquipment" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddProducts" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddCreditAlerts" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <soap:operation soapAction="//10.136.129.245/PinnacleWebServices/AddStockFigures" style="document" />
         <wsdl:input>
            <soap:body use="literal" />
         </wsdl:input>
         <wsdl:output>
            <soap:body use="literal" />
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
      <http:binding verb="GET" />
      <wsdl:operation name="DatabaseAvailable">
         <http:operation location="/DatabaseAvailable" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <http:operation location="/AddCustomers" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <http:operation location="/AddContracts" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <http:operation location="/AddInstalledEquipment" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <http:operation location="/AddProducts" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <http:operation location="/AddCreditAlerts" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <http:operation location="/AddStockFigures" />
         <wsdl:input>
            <http:urlEncoded />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:binding name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" type="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
      <http:binding verb="POST" />
      <wsdl:operation name="DatabaseAvailable">
         <http:operation location="/DatabaseAvailable" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCustomers">
         <http:operation location="/AddCustomers" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddContracts">
         <http:operation location="/AddContracts" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddInstalledEquipment">
         <http:operation location="/AddInstalledEquipment" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddProducts">
         <http:operation location="/AddProducts" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddCreditAlerts">
         <http:operation location="/AddCreditAlerts" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
      <wsdl:operation name="AddStockFigures">
         <http:operation location="/AddStockFigures" />
         <wsdl:input>
            <mime:content type="application/x-www-form-urlencoded" />
         </wsdl:input>
         <wsdl:output>
            <mime:mimeXml part="Body" />
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="Pinnacle_x0020_Web_x0020_Services">
      <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesSoap" binding="tns:Pinnacle_x0020_Web_x0020_ServicesSoap">
         <soap:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
      </wsdl:port>
      <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpGet" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpGet">
         <http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
      </wsdl:port>
      <wsdl:port name="Pinnacle_x0020_Web_x0020_ServicesHttpPost" binding="tns:Pinnacle_x0020_Web_x0020_ServicesHttpPost">
         <http:address location="http://10.136.129.245/pinnaclewebservices/maintenance.asmx" />
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>
Thanks in advance.

Hi Raja,
              Thanks for your prompt reply. I tried changing in the WSDL file the SOAP action parameters (http) like you said and still I got the same error message while testing the interface.
              I have corrected the problem by trying a different approach. Earlier I used file option for Client Proxy creation and I got the error message.
Now I created the Client Proxy by using the option URL/HTTP destination ( which was also showing errors earlier but it is OK now after our Network Specialists opened the concerned port.)
                Your reply was usefull as it helped me to check the "Soap Action" in the "OPERATIONS" tab of the "LOGICAL PORT" for the client proxy. I have awarded the points for that.
                I have seen your Blogs and the your replies to the questions in this form. I would like to thank you and all the like minded contributors of this forum. Keep up the good work.
Regards.
François

Consuming WebServices in ABAP WebDynPro via webservice proxy code

Hi,
My requirement is to consume a webservice using WSDL(basic authentication) in WebDynPro ABAP. then based on the SOAP response I need to show a pop up message whether the response valid or not.?
I first tested the webservice by creating LPCONFIG Logical Port and generated WebService Proxy class.
It got response correctly with basic authentication enabled each time I send a request.
Secondly I generated webservice proxy code using service calls on creating webdynpro test application with some UI elements. Service call created Nodes,attributes and method correctly.
it's giving me error when it tries to invoke webservice method through generated code.
Question is that How do we code authentication to the webservice method via WebDynPro ABAP code.
I appreciate anyone who worked on this area and taken basic authentication via coding. or worked successfully through coding.
Thanks
Praveen

hi
Refer this:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6066fbe8-edc4-2910-9584-a9601649747d
It might be usefull for u.
Regards
Vivekananthan.S

Error while consuming webservice

While consuming a webservice i got this error and i didn't found what's the problem.
Any help?
TypeError: Cannot marshall type 'http://www.w3.org/2001/XMLSchema::ReverseGeocodeRequest0' to simple content.
    at mx.rpc.xml::SchemaMarshaller/marshall()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\x ml\SchemaMarshaller.as:97]
    at mx.rpc.xml::SchemaManager/marshall()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\xml\ SchemaManager.as:468]
    at mx.rpc.xml::XMLEncoder/encodeType()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\xml\X MLEncoder.as:1434]
    at mx.rpc.soap::SOAPEncoder/encodeType()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\soa p\SOAPEncoder.as:806]
    at mx.rpc.xml::XMLEncoder/encode()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\xml\XMLEn coder.as:96]
    at mx.rpc.soap::SOAPEncoder/encode()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\soap\SO APEncoder.as:749]
    at mx.rpc.soap::SOAPEncoder/encodePartValue()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rp c\soap\SOAPEncoder.as:646]
    at mx.rpc.soap::SOAPEncoder/encodeMessage()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\ soap\SOAPEncoder.as:592]
    at mx.rpc.soap::SOAPEncoder/encodeOperationAsRPCLiteral()[E:\dev\4.5.1\frameworks\projects\r pc\src\mx\rpc\soap\SOAPEncoder.as:464]
    at mx.rpc.soap::SOAPEncoder/encodeBody()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\soa p\SOAPEncoder.as:358]
    at mx.rpc.soap::SOAPEncoder/encodeEnvelope()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc \soap\SOAPEncoder.as:197]
    at mx.rpc.soap::SOAPEncoder/encodeRequest()[E:\dev\4.5.1\frameworks\projects\rpc\src\mx\rpc\ soap\SOAPEncoder.as:162]
    at com.ngi.flex.lbs.webserviceObjects::BaseNGILBSWebService/call()[D:\Workspaces\WS_Stage201 1\ngiLbsFlexWebservice\src\com\ngi\flex\lbs\webserviceObjects\BaseNGILBSWebService.as:420]
    at com.ngi.flex.lbs.webserviceObjects::BaseNGILBSWebService/wsReverseGeocode()[D:\Workspaces \WS_Stage2011\ngiLbsFlexWebservice\src\com\ngi\flex\lbs\webserviceObjects\BaseNGILBSWebSer vice.as:404]
    at com.ngi.flex.lbs.webserviceObjects::NGILBSWebService/wsReverseGeocode()[D:\Workspaces\WS_ Stage2011\ngiLbsFlexWebservice\src\com\ngi\flex\lbs\webserviceObjects\NGILBSWebService.as: 529]
    at com.ngi.flex.lbs.webserviceObjects::NGILBSWebService/wsReverseGeocode_send()[D:\Workspace s\WS_Stage2011\ngiLbsFlexWebservice\src\com\ngi\flex\lbs\webserviceObjects\NGILBSWebServic e.as:539]
    at com.ngi.flex.lbs::NgiLBSSimplifiedWebservice/sendWsReverseGeocodeReq()[D:\Workspaces\WS_S tage2011\ngiLbsFlexWebservice\src\com\ngi\flex\lbs\NgiLBSSimplifiedWebservice.as:78]
    at com.ngi.flex.lbs::NgiLBSSimplifiedWebservice/reverseGeocode()[D:\Workspaces\WS_Stage2011\ ngiLbsFlexWebservice\src\com\ngi\flex\lbs\NgiLBSSimplifiedWebservice.as:66]
    at testMyLibrary/___testMyLibrary_Button1_click()[D:\Workspaces\WS_Stage2011\testMyLibrary\s rc\testMyLibrary.mxml:88]

Try setting the resultFormat on your HTTPService to e4x.
HTH;
Amy

Error while Consuming WebServices

Hi!
I've created a abap - proxy and a lpconfig to consume a WS.
When i test the service client in se80 i get this error:
Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
In the log of the Serviceprovider, we can see, that authentication was ok and no exception occured...
Can anybody help me?
Regards,
Christian

Hi to everybody!
FYI: I solved the problem: In Lpconfig i had to use port 80 -> now it works

Logon error while consuming webservices

I am able to create webservice and generate WSDL from SOAMANAGER with endpoints in ECC 6.0. I am getting error while trying to use this WSDL in my soapUI. It just says logon error, 401 authenticating, icf team... I cannont test this in soamanager as I don't have javastack, that whay i have to soapui to test.
I created service user and gave some webservice consumer roles.
Do I need do any RFC Dest settings(sm59) or some other basis setting in ICF.
Should I need to publish these services in order for other internal non sap systems to access it.

Hello,
Your problem seems like a SOAPUI usage problem. Most probably you did not povide the user and password at the right place...
Regards,
Olivier

Consuming webservice in ABAP - empty complexType table

Hello,
I've the following problem:
I consume a webservice, which has two parameters as response-result. The first parameter is a simple type. The second parameter is a table type described as follows in the WSDL:
- <element name="getVarListResponse">
- <complexType>
- <sequence>
<element name="getVarListReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
- <complexType name="ArrayOf_xsd_string">
- <sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="xsd:string" />
</sequence>
</complexType>
- <complexType name="ServiceResult">
- <sequence>
<element name="_errorMessage" nillable="true" type="xsd:string" />
<element name="_resultList" nillable="true" type="impl:ArrayOf_xsd_string" />
<element name="_successfull_processed" type="xsd:int" />
</sequence>
</complexType>
- <element name="getVarListFromDWDocument">
- <complexType>
- <sequence>
<element name="dwdocumentID" type="xsd:long" />
</sequence>
</complexType>
</element>
- <element name="getVarListFromDWDocumentResponse">
- <complexType>
- <sequence>
<element name="getVarListFromDWDocumentReturn" type="impl:ServiceResult" />
</sequence>
</complexType>
</element>
I created a proxy to consume this service. When I test the proxy directly I get the correct result displayed as XML (the response). When I try to call the service over ABAP code (use the proxy in a report), I've the problem that the complex-type table is empty. The simple type value is correctly filled.
Does anyone have an idea which could be the problem? I guess the mapping of the XML response in the DDIC-types isn't working correctly, but I've no idea why.
Thanks in advance
Cunanan1980

Hi Srikanth,
Check this regarding the web service in WDA.
Ist Step : configure Logical Port
http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
2nd Step : Generate Proxy Object
http://help.sap.com/saphelp_nw70/helpdata/EN/16/285d32996b25428dc2eedf2b0eadd8/frameset.htm
3rd Step : Instantiating the proxy object & calling the methods exposed by webservice
data: sys_exception type ref to cx_ai_system_fault,
      sys_exception2 type ref to cx_ai_application_fault,
      client_proxy type ref to zco_myesa, "MY PROXY CLASS
      lv_ret_code type int4,
      lv_input type zsend_email_input,
      lv_response type zsend_email_response.
data: lv_from type string,
      lv_from_address type string,
      lv_to type string,
      lv_to_address type string,
      lv_subject type string,
      lv_msg type string.
lv_input-from = 'MYSAPTEST'.
lv_input-from_address = '<someAddress>'.
lv_input-to = 'Prashant'.
lv_input-to_address = '<someAddress>'.
lv_input-subject = ' TEST'.
lv_input-msg_body = ' Hi this is wonderfull to see it work'.
try.
create object client_proxy
exporting
logical_port_name = 'BASIC'. " Basic is a TYPE G RFC Destination
call method client_proxy->send_email
   exporting
     input = lv_input
   importing
     output = lv_response    .
catch cx_ai_system_fault into sys_exception .
    data lv_err type string.
     lv_err = sys_exception->if_message~get_text( ).
     write: / lv_err.
catch cx_ai_application_fault into sys_exception2 .
     lv_err = sys_exception->if_message~get_text( ).
     write: / lv_err.
endtry.
if lv_response is initial.
   write: /'Not Executed'.
else.
   write: /'Did Execute'.
endif.
Regard
Manoj Kumar

Error in Consuming Webservice in ABAP

Similar Messages

Maybe you are looking for