Problem ABAP PROXY to SOAP

[#1]

I am developing an ABAP Proxy to SOAP interface.

I'm using an external definition with the wsdl for the service inbound interface and outbound interface for the determination, I was not allowed to use the definition as external error occurred while creating the abap proxy.

Thus, utilized a message type of structure to be sent, and a message maping.

However when I run the error message occurs:

/ Parsing / ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'mt_XXX_Request'.

Already confirmed URL of sending CC and left blank SOAP ACTION, however problem persists.

Already viewed this problem?

[former_member187533]

Error creating ABAP PROXY in SPROXY using the External Interface Definition in Service:

message part refers a type, not an element

Structure XML:

<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:DefaultNamespace" xmlns:intf="urn:DefaultNamespace" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:DefaultNamespace">

<wsdl:types>

<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:DefaultNamespace">

<complexType name="CAMPO">

<sequence>

<element name="NOMECAMPO" type="xsd:string"/>

<element name="TIPOCAMPO" type="xsd:string"/>

<element maxOccurs="unbounded" minOccurs="0" name="VALORCAMPO" type="xsd:string"/>

</sequence>

</complexType>

<complexType name="DOC">

<sequence>

<element name="CHAVE" type="xsd:string"/>

<element name="FORM" type="xsd:string"/>

<element maxOccurs="unbounded" minOccurs="0" name="CAMPOS" nillable="true" type="impl:CAMPO"/>

</sequence>

</complexType>

<complexType name="RETORNO">

<sequence>

<element name="UNID" type="xsd:string"/>

<element name="CODIGO" type="xsd:short"/>

<element name="MESSAGE" type="xsd:string"/>

</sequence>

</complexType>

</schema>

</wsdl:types>

<message name="ATUALIZADOCResponse">

<part name="ATUALIZADOCReturn" type="impl:RETORNO"/>

</message>

<message name="ATUALIZADOCRequest">

<part name="DOC" type="impl:DOC"/>

</message>

<portType name="GerAtualizaRegistro">

<operation name="ATUALIZADOC" parameterOrder="DOC">

<input message="impl:ATUALIZADOCRequest" name="ATUALIZADOCRequest"/>

<output message="impl:ATUALIZADOCResponse" name="ATUALIZADOCResponse"/>

</operation>

</portType>

<binding name="DominoSoapBinding" type="impl:GerAtualizaRegistro">

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

<operation name="ATUALIZADOC">

<wsdlsoap:operation soapAction="ATUALIZADOC"/>

<input name="ATUALIZADOCRequest">

<wsdlsoap:body namespace="urn:DefaultNamespace" use="literal"/>

</input>

<output name="ATUALIZADOCResponse">

<wsdlsoap:body namespace="urn:DefaultNamespace" use="literal"/>

</output>

</operation>

</binding>

<service name="GerAtualizaRegistroService">

<port binding="impl:DominoSoapBinding" name="Domino">

<wsdlsoap:address location="http://XXXXX/GeralDoc?OpenWebService"/>

</port>

</service>

</definitions>

[rhviana]

Lucas,

Because there is no any element into wsdl.

As for XSD, is it possible ?

If you I suggest you generate manually, creating a DT e MT  - REQ/RESP

Kind regards,

BR.

Ricardo Viana.

[former_member187533]

So Ricardo, this was my first exit, create the DT and MT REQ / RES, but then the interface begins to show the problem:

/ Parsing / ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'mt_XXX_Request'.

If I use the External Definition SI presents the error to create the proxy!

Thanks for the help!

[rhviana]

Lucas,

Could you please provide the audit log from adapter SOAP ?

Also display the soap adapter configuration and soapAction from Webservice.

Kind regards,

[former_member187533]

31.01.2014 10:17:38.994	Information	Message was received by the messaging system. Protocol: XI URL: http://XXXX/MessagingSystem/receive/AFW/XI Credential (User): PIISPD1
31.01.2014 10:17:38.998	Information	Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue
31.01.2014 10:17:39.003	Information	Message successfully put into the queue
31.01.2014 10:17:39.006	Information	The message was successfully retrieved from the request queue
31.01.2014 10:17:39.007	Information	Message status set to DLNG
31.01.2014 10:17:39.009	Information	Delivering to channel: XXXX_Funcionario
31.01.2014 10:17:39.009	Information	MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
31.01.2014 10:17:39.030	Information	SOAP: request message entering the adapter with user J2EE_GUEST
31.01.2014 10:17:39.218	Information	SOAP: completed the processing
31.01.2014 10:17:39.219	Information	SOAP: continuing to response message ad26d533-8a71-11e3-b462-000003ca861a
31.01.2014 10:17:39.219	Error	SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation mt_XXX_Request
31.01.2014 10:17:39.226	Error	SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation mt_XXX_Request
31.01.2014 10:17:39.226	Error	MP: 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: No such operation 'mt_XXX_Request'
31.01.2014 10:17:39.230	Error	Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'mt_XXX_Request'
31.01.2014 10:17:39.231	Error	Delivery of 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: No such operation 'mt_XXX_Request'. Setting message to status failed
31.01.2014 10:17:39.233	Error	Message status set to FAIL