How to use this .WSDL file

Question

Hello,
I was given this .WSDL file and asked to import it into PI. It's a very simple operation. From ECC  we will send some user data in the header and some Ticket data in the body. It is forwarded by PI to 3rd party ticket system. The result sent back is the ticket ID that is created in ticket system.
However i'm facing difficulties with this. Please see actions i've done below.
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
    xmlns:soap = "http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tm = "http://microsoft.com/wsdl/mime/textMatching/"
    xmlns:soapenc = "http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:mime = "http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:tns = "http://srv-dca-sc-web1.AAAA.com/"
    xmlns:s = "http://www.w3.org/2001/XMLSchema"
    xmlns:http = "http://schemas.xmlsoap.org/wsdl/http/"
    targetNamespace = "http://srv-dca-sc-web1.AAAA.com/"
    xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
        <s:schema elementFormDefault = "qualified" targetNamespace = "http://srv-dca-sc-web1.AAAA.com/">
            <s:element name = "HrwHeader" type = "tns:HrwHeader"/>
            <s:complexType name = "HrwHeader">
                <s:sequence>
                    <s:element minOccurs = "0" maxOccurs = "1" name = "Username" type = "s:string"/>
                    <s:element minOccurs = "0" maxOccurs = "1" name = "Password" type = "s:string"/>
                    <s:element minOccurs = "0" maxOccurs = "1" name = "EmployeeId" type = "s:string"/>
                    <s:element minOccurs = "1" maxOccurs = "1" name = "CompanyId" type = "s:int"/>
                </s:sequence>
                <s:anyAttribute/>
            </s:complexType>
            <s:element name = "CreateTicket">
                <s:complexType>
                    <s:sequence>
                        <s:element minOccurs = "0" maxOccurs = "1" name = "description" type = "s:string"/>
                        <s:element minOccurs = "1" maxOccurs = "1" name = "serviceId" type = "s:int"/>
                        <s:element minOccurs = "1" maxOccurs = "1" name = "priorityId" type = "s:int"/>
                        <s:element minOccurs = "1" maxOccurs = "1" name = "levelId" type = "s:int"/>
                        <s:element minOccurs = "0" maxOccurs = "1" name = "thirdPartySystemID" type = "s:string"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:element name = "CreateTicketResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element minOccurs = "1" maxOccurs = "1" name = "CreateTicketResult" type = "s:int"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
        </s:schema>
    </wsdl:types>
    <wsdl:message name = "CreateTicketSoapIn">
        <wsdl:part name = "parameters" element = "tns:CreateTicket"/>
    </wsdl:message>
    <wsdl:message name = "CreateTicketSoapOut">
        <wsdl:part name = "parameters" element = "tns:CreateTicketResponse"/>
    </wsdl:message>
    <wsdl:message name = "CreateTicketHrwHeader">
        <wsdl:part name = "HrwHeader" element = "tns:HrwHeader"/>
    </wsdl:message>
    <wsdl:portType name = "TicketServiceSoap">
        <wsdl:operation name = "CreateTicket">
            <wsdl:documentation xmlns:wsdl = "http://schemas.xmlsoap.org/wsdl/">Create new ticket and return the Ticket ID as an integer</wsdl:documentation>
            <wsdl:input message = "tns:CreateTicketSoapIn"/>
            <wsdl:output message = "tns:CreateTicketSoapOut"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name = "TicketServiceSoap" type = "tns:TicketServiceSoap">
        <soap:binding transport = "http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name = "CreateTicket">
            <soap:operation soapAction = "http://srv-dca-sc-web1.AAAA.com/CreateTicket" style = "document"/>
            <wsdl:input>
                <soap:body use = "literal"/>
                <soap:header message = "tns:CreateTicketHrwHeader" part = "HrwHeader" use = "literal"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use = "literal"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
</wsdl:definitions>
What i wanted to do was to create a service interface in PI that could be used in ECC to create a proxy of. The service interface needs to use the HRWheader and Ticket SoapIn combined. However when I import the .WSDL in an external definition i see three separate messages (header, soapin, soapout) and there is no way i can use the two messages in one SI.
I also tried importing the .WSDL using "do not extract" but that doesn't help either.
I also tried importing the .WSDL file as a Service Interface directly and it neatly creates a synchronous interfaces with the soapin as request and soapout as response, but it still doesn't show the header. If i check the WSDL tab for my newly created interface i also miss the reference to the Header message.
So my question is for some help and what would be the best way to handle this.
Kr
Regards

Answer 1

hi ,
check this link ,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/244e7923-0a01-0010-5887-fe0b0c6dbb8d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/30f1b585-0a01-0010-3d96-ad0ea291c4f9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/db785a70-0701-0010-858c-eee0ec4fe1b3
In Web Dynpro ABAP there is nothing special about calling a web service. Unlike WD Java, there are not dedicated model object types in WD ABAP. WD ABAP simply has the ability to interact with other ABAP development object types. You can call function modules, ABAP classes, even modules in old dynpro apps.
So calling the webservice from ABAP therefore is just the process of generating the ABAP Proxy Class. This is the same process regardless of if you want to use this proxy class from WDA or any other type of ABAP development object. You can then call the proxy class from WDA just like any other type of ABAP class. There is a service wizard option in later support package levels that includes an option for ABAP Proxy classes - although it doesn't generate the proxy class it just generates the code and context for the call to an already existing proxy class. The service wizards in WD ABAP are not required however. They are just shortcut code generators and often can't even generate a complete context for a complex web service proxy - so expect to do some manual adjustment after running the wizard.
Regards ,
venkat .