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

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

• soap:Header was not understood,
• SoapFaulCodeName: SecurityError "A security error was encountered when verifying",
• 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.

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

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, SoapFaulCodeName: SecurityError, WS-A header, Reliable Messaging, Cloud Integration, SRT_UTIL, SRT_LOG, SRT_ELOG,
, KBA , web service addressing , soap:mustunderstand="1" , sap:trace , metering , metering of service calls , BC-ESI-WS-ABA-RT , WebServices ABAP Runtime , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , How To