Customer Relationship Management Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
cancel
Showing results for 
Search instead for 
Did you mean: 
AbinashNanda
Product and Topic Expert
Product and Topic Expert

So far with HCI end to end monitoring of messages has always been little difficult. For example in the past it was always difficult to find an IDOC and its corresponding SAP Cloud for Customer message ID. With 1505 release, now the monitoring of asynchronous messages have been made easy.


This feature has been introduced via the help of Content Modifier (Using SAP_ApplicationID header element)


For ERP->HCI->C4C we can search message based on IDOC numbers and for C4C->HCI->ERP we can search messages based on message ID available via web service message monitor in SAP cloud for Customer.


For this simply specify the IDOC no or SAP Cloud for Customer message ID in the search field Application ID as shown below



Now to see end to end monitoring in action, let's take an example scenario in which data flows from ERP to SAP Cloud for Customer via HCI. Using t-code WE05 in the back end system we can get the IDOC number and provide it as a filter in the Application ID field. This should return us the corresponding HCI message in the message monitor



Now we can open the message processing log and search for the string com.sap.sod.utils.idoc.soap.messageid, which will give us corresponding message ID for the SAP Cloud for Customer system


For the other direction in which data flows from SAP Cloud for Customer to SAP ERP via HCI, we can get the message ID using the web service message monitor in SAP cloud for Customer and provide it as a filter in the Application ID field.



Now we can open the message processing log and search for the string com.sap.sod.utils.idoc.soap.idocassign, which will give us corresponding IDOC no in the SAP back-end system.




Limitations:

1.     Currently only asynchronous messages can be monitored and

2.     Bulk IDOC monitoring is not supported


A Conclusion note: You can use the content modifier to search the message based on any other header fields or payload element.

For getting all the header fields you can write a simple groovy script, which should return all the header fields available in runtime

For searching based on payload element you can use XPath expressions.






10 Comments