Error in Synchronous client proxy

Hi Gurus,
I have created a scenario in which I am using client proxy at source side (ECC ) and soap at target side.
Its a synchronous scenario for which I have written an abap report.This interface sends a company name and uses a webservice to fetch the stock value of that company.
I am a beginner in abap, so I am unable to to know the reason why is it showing the following error when I am executing the code.
Method "EXECUTE_SYNCHRONOUS" is unknown or PROTECTED or PRIVATE.
This error is coming at line :
CALL METHOD Proxy->execute_synchronous
Following is the code :
REPORT  ZSYNC_PROXY_STOCKQUOTE NO STANDARD PAGE HEADING.
DATA Proxy TYPE REF TO ZCO_SI_SOURCE.
CREATE OBJECT Proxy.
DATA: t_company_name TYPE zsource_request_mt,
       t_stock_value TYPE zsource_response_mt.
SELECTION-SCREEN: BEGIN OF BLOCK B1.
PARAMETER: p_id TYPE String.
SELECTION-SCREEN: END OF BLOCK B1.
  START-of-selection.
  TRY.
    t_company_name-Source_Request_MT-Company_name = p_id.
    CALL METHOD Proxy->execute_synchronous
    Exporting
      output = t_company_name
   IMPORTING
     input = t_stock_value.
   WRITE: t_stock_value-Source_Response_MT-stock_value.
   CATCH cx_ai_system_fault.
     DATA fault TYPE REF TO cx_ai_system_fault.
     CREATE OBJECT FAULT.
    WRITE:/ fault->errortext.
    ENDTRY.
    END-OF-SELECTION.

Hi,
You have wrongly assigned the method. It should not be pointing to Execute method.
it should be something like below
TRY.
           CREATE OBJECT proxy.
           CATCH cx_ai_system_fault.
  ENDTRY.
TRY.
    CALL METHOD Proxy->  " GIVE THE OUTBOUND SERVICE INTERFACE NAME HERE"
    Exporting
      output = t_company_name
   IMPORTING
     input = t_stock_value.

Similar Messages

  • Synchronous Client Proxy to JDBC !!

    Hi,
    My scenario is like this:
    I am working on a synchronous scneario where SAP is sending
    using synchronous client proxy to a database and after uploading
    of data on JDBC side, the response(Success/Failure) flag has to be
    sent back to SAP.
    Please let me know how this scneario can be designed and if BPM is required here.
    Thanks...

    Hi,
    Go thru  this
    http://help.sap.com/saphelp_nw70/helpdata/en/45/20d251c20a0732e10000000a155369/content.htm
    https://forums.sdn.sap.com/click.jspa?searchID=8242639&messageID=4482651
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
    JDBC Synchronous call  using BPM
    Regards
    Agasthuri Doss

  • RFC calls & Synchronous Client Proxy

    If I want to execute a Synchronous Client Proxy, sending request to XI and waiting for response from XI, do I HAVE TO define and import a RFC structure ?
    My doubt is whether implementing RFC is a must in this case, or we can just define a equivalent structure (to the RFC structure: request & response), define all the mapping and create the proxy accordingly and it will work?
    Your help is appreciated.

    Hi!
    No, you don't need to do that. Simply define your interface and generate proxies.
    Peter

  • Error in synchronous( abap proxy to soap)scenario

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

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

  • Exception handling in synchronous client proxy

    Hi, I have a synchronous outbound proxy-web service scenario. If our Post request (unknown data in the receiver) fails, the receiver system returns a 404 error that results in application error in PI. Now, I want know how to handle CX_AI_APPLICATION_FAULT using the standard fault message type (ExchangeFaultData). I couldn't find any reference for synchronous client proxies using this. I hope you can help me out. Thank you.

    Hi Mark,
    You have a link here How to handle CX_AI_SYSTEM_FAULT in RFC - Code Gallery - SCN Wiki or here https://help.sap.com/saphelp_nw04/helpdata/en/75/a55c3cff8ca92be10000000a114084/content.htm
    I dont know what is your exact problem, you can retrieve certain information in the ABAP code but i usually set a generic message like "Connection unsuccessful" because if you debbug the object the information is so technical to be showed to a client.
    Hope this helps.
    Regards.

  • Error at creating Client Proxy of external webservice (WSDL)

    Hi Experts,
    I try to create a Client Proxy Object out of an external webservice. Here is the WSDL URL:
    [http://www.webservicex.net/CurrencyConvertor.asmx?wsdl]
    I try to create it with this URL and then I get the error message
    Not implemented
    Exception of class CX_SIDL_INTERNAL_ERROR
    I found two other threads with a similar problem:
    cunsuming external webservice in ABAP
    Problem while consuming external webservice
    But there is no solution that worked for me. In the first thread it is mentioned, that the code between
    <wsdl:binding name="XXXXHttpGet" type="tns:XXXHttpGet">
    and it's closing brackets should be removed in a local file. I tried that and was able to create a client proxy object out of this local wsdl-file. But then I called the webservice with the folling coding for testing:
    report  z_currency_converter.
    data: convert type ref to zzzco_currency_convertor_soap.
    try.
        create object convert
      exporting
        logical_port_name  = 'Z_LP'
      catch cx_ai_system_fault .
    endtry.
       data: output type zzzconversion_rate_soap_out  .
       data: input type zzzconversion_rate_soap_in .
       input-from_currency = 'EUR'.
       input-to_currency = 'USD'.
    try.
    call method convert->conversion_rate
      exporting
        input  = input
      importing
        output = output
    catch cx_ai_system_fault .
    catch cx_ai_application_fault .
    endtry.
    write output-conversion_rate_result.
    The same code worked fine in another system. In this "older" system could also create a client proxy, I think because it has a newer Support Pack version.
    SAP says the following:
    The problem is that this WSDL uses two bindings different from SOAP
    binding which is not in conformance with Basic Profile 1.1 -
    http://www.ws-i.org/Profiles/BasicProfile-1.1.html#WSDLBINDINGS .
    I looked in the document, but I do not know where the problem in the WSDL file exactly is. What have I to change? Or can somebody give me the URL of a free webservice, that you used for creating a client proxy with a new support pack standing? In the "old" system there is not yet the SOAMANAGER but in the one where it doesn't work.
    I hope you have an idea.
    Thanks a lot in advance!
    Best Regards,
    Ingmar

    I think it is the problem of version.U need to ask SAP to release some patch levels to correct it.
    Regards
    Snehasish

  • Error while creating Client Proxy from SE80

    Hi all,
    I am trying to create Client Proxy with WSDL through SE80. There is no involvement of XI to create the Proxy.
    I am using the option 'Local file' and uploading the wsdl file.
    But I am getting the following errors.
    "Proxy-Generierung: Fehler aufgetreten"
    "Exception occurred in library handler"
    "Illegal syntax: Element header has invalid enhancement attribute
    http://schemas.xmlsoap.org/wsdl/:required"
    If any one could understand them and worked in a similar scenario, pls help me out.
    regards,
    teja.

    hi,
    you might want to post the WSDL in question for us to have a look at.
    but actually, the error message tells a lot:
    http://schemas.xmlsoap.org/wsdl/:required
    the second colon(, the one between wsdl/ and required, makes this expression an illegal one in any kind of a URI-like meaning (namespace, ref-URL, ...)
    anton

  • Error  while generating client proxy

    Hi All,
    I have got a WSDL file for which I am generating the client proxy. It is giving me a dump saying that, memory is not sufficient while generating the proxy.
    I have also contacted the basis team, even after increasing the memory... we are facing the same issue. Can anyone suggest any solution or SAP Note if there are any???
    Thanks in advance.
    Bhargava.

    Hi,
    Please find the dump details below:
    ST22 DUMP:
    Short text
        No storage space available for FORM stack.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
        Try to find out (e.g. by targetted data selection) whether the
        transaction will run with less main memory.
        If there is a temporary bottleneck, execute the transaction again.
        If the error persists, ask your system administrator to check the
        following profile parameters:
        o  ztta/roll_area            (1.000.000 - 15.000.000)
               Classic roll area per user and internal mode
               usual amount of roll area per user and internal mode
        o  ztta/roll_extension       (10.000.000 - 500.000.000)
               Amount of memory per user in extended memory (EM)
        o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
               Amount of memory (malloc) for all users of an application
               server. If several background processes are running on
               one server, temporary bottlenecks may occur.
               Of course, the amount of memory (in bytes) must also be
               available on the machine (main memory or file system swap).
               Caution:
               The operating system must be set up so that there is also
               enough memory for each process. Usually, the maximum address
               space is too small.
               Ask your hardware manufacturer or your competence center
               about this.
               In this case, consult your hardware vendor
        abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each dialog process.
        Parameters for background processes:
        abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each background process.
        Other memory-relevant parameters are:
        em/initial_size_MB:         (35-1200)
               Extended memory area from which all users of an
               application server can satisfy their memory requirement
    Error analysis
        You attempted to extend a stack, but the required storage spac
        not available.
        Storage request..............: 8450048 bytes.
    How to correct the error
        Please check whether uncontrolled recursive calls caused this
        runtime error.
        Try to decide by analysis whether this request is
        reasonable or whether there is a program error. You should pay
        particular attention to the internal table entries listed belo
    System environment
        SAP-Release 701
        Application server... "dcr"
        Network address...... "10.1.105.112"
        Operating system..... "AIX"
        Release.............. "6.1"
        Hardware type........ "00C834224C00"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 4

  • Error when create client proxy in ABAP

    hi all
        when I tried to create a client proxy through wsdl: http://www.webservicex.net/geoipservice.asmx?wsdl , I got and error message "Exception occurred in library handler", what's the really matter with this error ?
    thanks very much!

    You need to copy the WSDL file to a local file and edit it.  The WSDL file contains non-SOAP bindings and that's what the generator is choking on.  Use the 'Local file' option to generate the proxy class after editing the file.

  • Error With ABAP Client proxy

    Hi All,
       I am trying to use ABAP Client Proxy(Sync). I am getting the error.
    1. Message from SXMB_ADMIN on Business system.
    <b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="400" p2="ICM_HTTP_CONNECTION_FAILED" p3="" p4="">HTTP.HTTP_CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:Text language="EN">Error during http receive: Error code: 400 Error text: ICM_HTTP_CONNECTION_FAILED</SAP:Text>
      </SAP:ErrorHeader></b>
    2. No message On XI server.
    3.Went through the Ravikumar Allampallam's blog
    on ABAP ClientProxy .
    4. Went through the  vijaya kumari's " How do you activate ABAP Proxies?"
    5. created connections (sld)and one http connections in SM59. Tested the connections.
    6. Went throught the Forms.
    Any help would be appriaciated.
    Thank you
    Ganges Leaves.

    Vijaya Kumari,
       1. I have checked it. For XI server these are the values.
        Business System Role  : Integration Server.
        Pipe Line url : http://server:8000/sap/xi/engine?type=entry.
    8000 is the http port which i see in the SMICM+shift F1.
    Thank you
    Ganges Leaves

  • Error while testing client proxy

    Hi Gurus,
    We have a scenario: we are consuming an external Webservice into SAP (Creating a client proxy), we have created the proxy class and the binding in using SOAMANAGER.
    When we are testing this proxy it is giving us below error:
    Regards,
    Krishna Chauhan

    Hi Krishna,
    Try installing the SSL cert to TrustedCAs keystore reconfigure your communication channel that will locate the exact location of the certificate.
    Refer the below thread
    ICM_HTTP_SSL_ERROR
    Regards
    Bhargava Krishna

  • Namespace Error when generating Client Proxy for Java Web Service

    Hi.Experts:
        When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
        The error like this:
        "Incorrect value: Unknown Namespace http://sql.java
        Exception of class CX_SLIB "
       I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
    Best Regards
    Martin Xie

    Hi Martin
    I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
    Maybe my version is different.
    You say that you can select the file ou url.
    Did you select the file or url?
    If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
    If was url, access this url, copy the xml and same in one file, then select this file in the step above.
    I don't know if works, its only a suggestion.
    regards
    Marcos

  • Error in Java Client proxy

    Hi All,
        My scenario is JavaClient Proxy -
    XI----
    >RFC.
    Here i generated JavaProxies for my Message interface and i imported that zip file into NWDS for my EjbModule project.
    and also i added Jar files in libraries by saying add External Jars.
    Here r the Jars:
    aii_proxy_xirt.jar
    aii_msg_runtime.jar
    aii_utilxi_misc.jar
    guidgenerator.jar
    even i am getting an error saying com.sap can not be resolved or not a type
    Any inputs
    Is there any other jars i need to add ??
    How to resolve this error.
    Thanks,
    Kalyan.

    Hi Kalyan,
    I think you have not set the classpath corectly.
    For this :
    1. Get the file aii_map_api.jar from XI server (if you have not done this already).
    2. Create a new folder in the Java project you have created for mapping program. Name it as "lib"(any name would do..I just try to follow widely used naming conventions).
    3.Copy the jar file aii_map_api.jar to this folder.(You can copy it in explorer and go to NWDS, select the lib folder and do a Ctrl + V).
    4. Right click on the java project, select properties. Select Java build path. Go to Libraries tab. Click on the button "Add jars". In the dialog that pops up select your java project> lib> aii_map_api.jar.
    5. Click apply / OK.
    Rewards,
    Vinod.

  • Error generating Client Proxy - object  missing in WSDL

    Hello,
    I have error while generating Client Proxy.
    I have WSDL and XSD in files. I get error message:
    object <message name="requestUPOMessage"> missing in WSDL
    Diagnosis
    In the WSDL document, the object
       "<portType name="GateServicePortType"> <operatio..."
    from the namespace
      "https://bramka.edeklaracje. mf.gov.pl/"
    links to the object
       "<message name="requestUPOMessage">"
    from the namespace
       "https://bramka.e-deklaracje.mf.gov.pl/"
    However, this last object does not exist in the WSDL document.
    WSDL FILE and XSD FILE: http://www.sendspace.com/filegroup/N8kSxPp5bhY2nVfcNBbAXg
    WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:gate="https://bramka.e-deklaracje.mf.gov.pl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="https://bramka.edeklaracje.
    mf.gov.pl/">
    <wsdl:types>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
    targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:include schemaLocation="GateService.xsd"/>
    </xs:schema>
    </wsdl:types>
    <wsdl:message name="sendDocumentWithAttachmentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachmentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOResponseMessage">
    <wsdl:part name="part1" element="ns:requestUPOResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentMessage">
    <wsdl:part name="part1" element="ns:sendDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOMessage">
    <wsdl:part name="part1" element="ns:requestUPO">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentWithAttachmentMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachment">
    </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="GateServicePortType">
    <wsdl:operation name="sendDocument">
    <wsdl:input message="gate:sendDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <wsdl:input message="gate:sendUnsignDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendUnsignDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <wsdl:input message="gate:sendDocumentWithAttachmentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentWithAttachmentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <wsdl:input message="gate:requestUPOMessage">
    </wsdl:input>
    <wsdl:output message="gate:requestUPOResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="GateServiceSOAP12Binding" type="gate:GateServicePortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap12:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap12:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap12:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap12:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="GateServiceSOAP11Binding" type="gate:GateServicePortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="GateService">
    <wsdl:port name="GateServiceSOAP12port" binding="gate:GateServiceSOAP12Binding">
    <soap12:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    <wsdl:port name="GateServiceSOAP11port" binding="gate:GateServiceSOAP11Binding">
    <soap:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    XSD
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    elementFormDefault="qualified" attributeFormDefault="qualified">
    <xs:element name="sendDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachment">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="attachment" type="xs:base64Binary" minOccurs="0"/>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachmentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPO">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPOResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="upo" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    Maybe someone know what is wrong in wsdl file and how to correct this?

    Hi Marcus,
    Did you fix the problem?
    I'm asking because I'm dealing with the same problem! I tried to generate a Proxy object from a WSDL document and I can't... I always receive the error "Cannot generate proxy (object  missing in WSDL, see long text)". I have checked on the service.sap.com and I found a xls document with all unsupported WSDL elements and one of them is the "part name=" and I have it in my WSDL! I don't know how to workaround this issue, can you help me please?
    Thanks in advance,
    Ricardo.

  • Web Service - Client Proxy generation error

    Hi All,
    I tried creating a client proxy using an URL provided to me and followed the steps using the wizard. I end up in getting the following error messages. Could anyone throw some light on resolving this? I do not have any idea about what WSDL is. Any help is highly appreciated. Not able to attach the WSDL code here.
    Below is the error message upon client proxy creation:
    Proxy-Generierung: Fehler aufgetreten
    Exception occurred in library handler
    Not implemented
    Thanks
    Srini
    Edited by: Srinivasan Karunakaran on Oct 22, 2010 11:11 PM

    Resolved through SAP Help. Refer SAP note# 0001403271.

Maybe you are looking for