A Service Consumer (Consumer Proxy) was created and a corresponding Logical Port has been configured in transaction SOAMANAGER.
When executing the call, the target system returns an error, saying soap:Header was not understood, or simply a generic HTTP 500 Internal Server Error - depending on how the provider system is configured.
- SAP NetWeaver
- SAP Web Application Server for SAP S/4HANA
- Web Services for ABAP
WS-Addressing, Metering, SAP:Trace, SOA Runtime Trace Configuration, Disable Web Service Addressing, To, From, ReplyTo, MessageID, FaultTo, Action, Transfer protocol, Metering of Service Calls, Transfer via HTTP header, CallerInformation , KBA , soap:mustunderstand="1" , metering , sap:trace , web service addressing , metering of service calls , BC-ESI-WS-ABA-RT , WebServices ABAP Runtime , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.