SAP Knowledge Base Article - Preview

2032659 - ESI - Error: soap:Header was not understood

Symptom

When executing a web service call, the target system returns one of the following error messages:

  • soap:Header was not understood,
  • HTTP 500 Internal Server Error (depending on how the provider system is configured),
    OR
  • MustUnderstand headers: {http://schemas.xmlsoap.org/ws/2004/08/addressingjAction, {http://schemas.xmlsoap.org/ws/2004/08/addressingjTo] are not understood.


Read more...

Environment

  • SOAMANAGER
  • ABAP Web Services
  • SAP NetWeaver
  • SAP NetWeaver Application Server for SAP S/4HANA
  • ABAP PLATFORM - Application Server ABAP

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

Webservice, Web Service, Webservices, Web Services, ESI, ESI_GDPR, ESI_STD, 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, SoapFault:faultstring=MustUnderstand headers, MustUnderstand
, KBA , soap:mustunderstand="1" , web service addressing , metering , metering of service calls , sap:trace , BC-ESI-WS-ABA-RT , WebServices ABAP Runtime , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , How To

About this page

This 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.