Problem consuming third party web service in SAP M...

Former Member · ‎10-22-2010

Hi,

I am trying to consume a web service that is developed on Java based system using xFire web service frame work, the WSDL of the same is as below.

<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions targetNamespace="http://services.sos.automation.eitl.com" xmlns:ns1="urn:http://dispatch.services.sos.automation.eitl.com" xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding" xmlns:tns="http://services.sos.automation.eitl.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">

<wsdl:types>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="urn:http://dispatch.services.sos.automation.eitl.com">

<xsd:complexType name="ArrayOfSAPReceiver">

<xsd:sequence>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="SAPReceiver" nillable="true" type="ns1:SAPReceiver"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="SAPReceiver">

<xsd:sequence>

<xsd:element minOccurs="0" name="MBLNR" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="FG_BATCH" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="FGID" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="MATNR" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="MJA" nillable="true" type="xsd:int"/>

<xsd:element minOccurs="0" name="ST_DESC_UPD" nillable="true" type="xsd:int"/>

<xsd:element minOccurs="0" name="STATUS_MSG" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="STATUS_REC" nillable="true" type="xsd:string"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="ArrayOfSAPReceiverResult">

<xsd:sequence>

<xsd:element maxOccurs="unbounded" minOccurs="0" name="SAPReceiverResult" nillable="true" type="ns1:SAPReceiverResult"/>

</xsd:sequence>

</xsd:complexType>

<xsd:complexType name="SAPReceiverResult">

<xsd:sequence>

<xsd:element minOccurs="0" name="FG_BATCH" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="FGID" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="MATNR" nillable="true" type="xsd:string"/>

<xsd:element minOccurs="0" name="SOS_FLAG" type="xsd:int"/>

<xsd:element minOccurs="0" name="SOS_MSG" nillable="true" type="xsd:string"/>

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://services.sos.automation.eitl.com">

<xsd:element name="updateSAPReceiverService">

<xsd:complexType>

<xsd:sequence>

<xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="xsd:string"/>

<xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="ns1:ArrayOfSAPReceiver"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

<xsd:element name="updateSAPReceiverServiceResponse">

<xsd:complexType>

<xsd:sequence>

<xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="ns1:ArrayOfSAPReceiverResult"/>

</xsd:sequence>

</xsd:complexType>

</xsd:element>

</xsd:schema>

</wsdl:types>

<wsdl:message name="updateSAPReceiverServiceRequest">

<wsdl:part name="parameters" element="tns:updateSAPReceiverService">

</wsdl:part>

</wsdl:message>

<wsdl:message name="updateSAPReceiverServiceResponse">

<wsdl:part name="parameters" element="tns:updateSAPReceiverServiceResponse">

</wsdl:part>

</wsdl:message>

<wsdl:portType name="SAPReceiverServicePortType">

<wsdl:operation name="updateSAPReceiverService">

<wsdl:input name="updateSAPReceiverServiceRequest" message="tns:updateSAPReceiverServiceRequest">

</wsdl:input>

<wsdl:output name="updateSAPReceiverServiceResponse" message="tns:updateSAPReceiverServiceResponse">

</wsdl:output>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding name="SAPReceiverServiceHttpBinding" type="tns:SAPReceiverServicePortType">

<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

<wsdl:operation name="updateSAPReceiverService">

<wsdlsoap:operation soapAction=""/>

<wsdl:input name="updateSAPReceiverServiceRequest">

<wsdlsoap:body use="literal"/>

</wsdl:input>

<wsdl:output name="updateSAPReceiverServiceResponse">

<wsdlsoap:body use="literal"/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service name="SAPReceiverService">

<wsdl:port name="SAPReceiverServiceHttpPort" binding="tns:SAPReceiverServiceHttpBinding">

<wsdlsoap:address location="http://150.0.150.237:8087/sos-sap-service/services/SAPReceiverService"/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

One navigating through the WEB Service wizard, in the link editor, I am not finding that the structure complete either for the input to web service or the output from web service.

However on using the same WSDL in PI, I am able to see the entire structure of both input and output.

Can any body please tell, why is this difference or is there any problem in the above WSDL file?

Regards,

Prasad

Edited by: RPB on Oct 22, 2010 7:36 PM

Former Member · ‎10-25-2010

Hi Mike,

Please find the details below

SAP MII 12.1.7 Build(47)

NW CE 7.2

HP Unix 11.23

Java 6 SE build 1.6.0_22-b04

Regards

Prasad

agentry_src · ‎10-25-2010

Please provide the full version of MII (i.e. 12.1.6 build 44), the version of NW CE you have installed, and any other pertinent environment information.

Regards,

Mike

Problem consuming third party web service in SAP MII 12.1

Accepted Solutions (0)

Answers (2)

Answers (2)

Manage Task Fiori Features - App F3091

Maintenance Single Cycle Plan

Re: Quantity and Activity Confirmation is not refl...

Re: Quantity and Activity Confirmation is not refl...

Re: Unable to debug Custom function module in CG54...