3511109 - How to configure asynchronous call with SAP RM protocol from CPI to ABAP Webservice

Error messages may be generated in both Cloud Platform Integration (CPI) and the target backend system. This occurs when a CPI Integration Flow executes a SOAP call to an ABAP web service that requires the Reliable Messaging (RM) protocol. The specific errors associated with this configuration are detailed below:

1. Error in CPI monitoring: org.apache.cxf.binding.soap.SoapFault: Web service processing error; more details in the web service error log on provider side (UTC timestamp xxxxxxxxxxxxxx; Transaction ID XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX) 

2. From the backend, via the following transactions: SRT_LOG, SRT_UTIL and SRT_MONI. These transactions are also accessible via the SRT_TOOLS transaction. Use the Transaction ID mentioned in the error message or the timestamp to find the specific error message. 

3. The below error can be seen in the backend, when the call from CPI does not meet SAP-RM protocol: 

   • SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID and no WSRM assertion provided

• SAP Integration Suite
• SAP Cloud Integration 
• 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, SRT_CORE141, SAP RM, MessageId, Plain SOAP, WS-RM, WSRM assertion, no MessageId, no message id, Web Service processing error; more details in the web service error log on the provider side, org.apache.cxf.binding.soap.SoapFault, CPI,  , KBA , LOD-HCI-PI-CON-FTP , FTP, SFTP and SOAP Adapter , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , Problem