Interop issue: SAP consumer calls 3rd party provider
[com interop] [fault] [header] [interop] [interop.excel.dll] [interop.vba] [SOAP] [WS-A] [WS-Addressing] [wsa:Action] [wsa:To]
Related:
- Change ownership of WS-Addressing protocolSymptom Change the WS-Addressing objects ownership Other terms WS-A, WS-Addressing...
Symptom
If SAP system is used as Web Service consumer that calls a service
provided by a 3rd party, the 3rd party provider returns a SOAP fault
message as response complaining that the “To” attribute cannot be
understood.
Other terms
WS-Addressing, WS-A, wsa:To, wsa:Action, fault, soap, header
Reason and Prerequisites
The SOAP fault message indicates that the SAP client sends the WS-A
headers to the 3rd party provider, which however cannot understand the
WS-A protocol. “To” is one of the SOAP headers defined by WS-Addressing
protocol. Please refer to: http://www.w3.org/TR/ws-addr-core/ for
further information.
Solution
To go around this issue, either you deactivate the WS-A protocol on the
SAP consumer or turn on the WS-A protocol support on the 3rd party
provider.
To deactivate WS-A protocol on the SAP system:
1. Start the SOA Manager with TCODE soamanager
2. Search for the consumer proxy
3. display the proxy definitioin
4. Select the logical port
5. Choose the tab “Messaging”
6. In the DropDown “Message ID Protocol” select “Suppress ID Transfer”
If you still get SOAP fault message back which contains now different errors, such as HTTP “SOAPAction” is not understood or supported by the the provider, you have to assign the operation explicitly in the SAP system by setting the “soapaction” into the operation specific properties. Please refer to section 2 and point c of note 1292171.