SoapFaulCodeName: ActionNotSupported |SoapFaulCodeNamespace: http://schemas.microsoft.com/ws/2005/05/addressing/none

[tobias_ptz]

Hi everybody,

We are trying to use an external webservice in AS ABAP (ERP 6.07) and we've read all threads about this and other error messages.

The WSDL file and the webservice are running without any error via SoapUI.

We have created the proxy via SE80 and the logical port via SOAMANAGER, creating the logical port automatically with the WSDL brings the following error message: "SRT Framework exception: Error in WSDL parsing: Exception occured in library handler", even with the parameter "icm/trace_secured_data=true" we are not able to analyse this error message, so we created the port manually.

Now if we want to test the webservice via SE80

> Enterprise Services > Proxy Object > Ext. > Ext WSDL > Service Consumer > (proxy) > Enter > F8 (test)

> Use Runtime > logical port name (F4 > logical port from SOAMANAGER) > Method name (same method tested via SoapUI) > Use generated consumer class > Generate Request Template > F8 (execute)

Change "?" with some values > check syntax > F8 (execute)

Than we get the error message as in the title only in German, even if I logon with language EN:

SoapFaulCodeName: ActionNotSupported |SoapFaulCodeNamespace: http://schemas.microsoft.com/ws/2005/05/addressing/none Die Nachricht mit Action "" 
kann aufgrund einer fehlenden ContractFilter-Übereinstimmung beim EndpointDispatcher nicht verarbeitet werden. 
Mögliche Ursachen: Vertragskonflikt (keine Action-Übereinstimmung zwischen Sender und Empfänger) oder ein Bindung/Sicherheit-Konflikt zwischen 
dem Sender und dem Empfänger.  Stellen Sie sicher, dass Sender und Empfänger über den gleichen Vertrag und die gleiche Bindung verfügen 
(einschließlich Sicherheitsanforderungen, z. B. "Message", "Transport", "None").

Exception of class CX_AI_SOAP_FAULT

Anyone an idea what this can be? As I said, the service is running via SoapUI, but unfortunately not via SAP.

Thank you in advance!

Best regards,

Tobias

[tobias_ptz · Accepted solution]

After all, we found out that a simple ERP system cannot handle things like that.

One way is to install a XI/PI system, the other way is to setup a separate proxy that maps the needed thing in the right way.

[tobias_ptz]

Hi,

We found out, that SAP sends the wrong Envelope parameter, so the provider ignores our request.

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">

The right one should looks like that

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

I've read some threads about creating XSLT mapping, but these are all for a PI-SAP system, we are just using ECC ERP 6.07.

In our system I didn't find a point to add a mapping, or something else like that.

Where can I edit the SAP settings, that SAP sends the right parameters?

Thanks for any help!

Best regards,

Tobias

[Jelena]

I feel ABAP forum is not the right space for this, so you might not get much response. Moderator alerted to move to a different space.

[matt]

Moved.

[tobias_ptz]

Thank both of you!

[tobias_ptz]

The switch "Transport-Binding-Typ" in the consumer-proxy just shows "SOAP 1.1" and "SOAP 1.2".

The SRT_LOG gives me the following payload examples

SOAP 1.1 - Tags begin with <s:

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

SOAP 1.2 - Tags begin with <env:

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">

SOAP 1.1 use the right schema (xmlsoap.org) but the wrong tags.

SOAP 1.2 use for us useless tags and schema (w3.org)

Any hint to get the needed tags with the right schema?

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

Thanks for any help!

Best regards,

Tobias