Skip to Content
Product Information
Author's profile photo Alexander Bundschuh

New Message Monitoring features with SAP S/4HANA Cloud 2008 shipment

As you may know, in SAP S/4HANA Cloud, the message monitoring capability is actually based on SAP Application Interface Framework (AIF). With the latest 2008 delivery of SAP S/4HANA Cloud, we have shipped a couple of AIF related features. Here, the major features at a glance.

Cancel and restart messages through the SAP Cloud Platform Workflow services

Since SAP S/4HANA Cloud 2005 it is possible to trigger a workflow instance in case of an error during message processing. The interoperability between SAP Application Interface Framework and SAP Cloud Platform Workflow has been enhanced so that you can either cancel or restart a failed message from within a workflow task.

Check out the sample project on Github, it has been enhanced with the new option of cancelling and restarting a message.

OData consumption supported in AIF

For synchronous OData service calls, AIF has been supported before, see SAP Help Portal. However, in this case you can only display the error messages, correcting the message payload, restarting, or cancelling messages of the OData service calls is not supported.

For OData consumption, i.e., when asynchronously exchanging messages through an outbound interface within an SAP S/4HANA Cloud system with a service provider using the OData protocol, interface implementation, runtime, error handling, restart of messages and the like is now supported.

SAP Fiori UX monitor – message monitor details

With SAP S/4HANA Cloud 2005, we have shipped a user interface in SAP Fiori UX technology providing a message overview. With 2008, the SAP Fiori UI has been enhanced supporting message monitoring details.

From the message monitoring overview which provides status information in a tile layout, you can navigate to a list of relevant messages.

Here, the following features are supported:

  • Getting an overview of messages with dedicated status processed through the selected interface
  • Filter for messages with the help of parameters like the status, message ID, key fields, etc.
  • Display the log messages
  • Restart or cancel a message if in status Error or In Process
  • Set process information for a message incl. comments to inform your peers that you took over the message in order to fix the issue
  • Provide an alternative (customized) message text replacing the original text of an error message
  • Provide a hint, for example, to write a procedure on how to correct a common error
  • Easy navigation to another app for dedicated key fields if key field navigation is configured

From the list of message view, you can select a message and navigate to the message details where actions can be taken for a particular message.

Roadmap

If you like to know which features are planned to be shipped in future, check out the SAP Road Map Explorer accessible from here.

Assigned tags

      12 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sundas Noor
      Sundas Noor

      This blog is very informative. It covered all the essential SAP monitoring features very beautifully.

      Author's profile photo Michael Walker
      Michael Walker

      HI Alexander.  Did this make it into the 2020 on premise release?

      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      yes, this will go into 2020

      Alex

      Author's profile photo Christoph Bürgmayr-Posseth
      Christoph Bürgmayr-Posseth

      Hi Alexander,

      great feature, but I am struggeling with the BADI. I want to allow the fields CostCenter and WBS to be edited for /MMPUR INVREQIN.

      Here is my code, do you have an Idea why it does not work.

       

      thanks for any hint.

      best regards

      Christoph Bürgmayr-Posseth

      Author's profile photo Britta Mangei
      Britta Mangei

      Hi Christoph,

       

      with the provided information I would guess that there is something wrong with the field path. Can you give more information about the used structure?

      Best Regards

      Britta

      Author's profile photo Christoph Bürgmayr-Posseth
      Christoph Bürgmayr-Posseth

      Hi Britta,

      thanks for your quick reply.

       

      I am exactly your opinon, my problem is the path, but I am not able to find the issue.

      I am using the standard structure for /MMPUR INVREQIN.

      We are on S/4Hana public cloud, so no backend access.

       

      Author's profile photo Britta Mangei
      Britta Mangei

      Hello,

      try to use the complete path (without the Root structure). It should look like below:

      SUPPLIER_INVOICE-SUPPLIER_INVOICE_ITEM_GLACCT-SUPPLIER_INVOICE_ITEM_GLPOSTIN-COST_CENTER

      Unfortunately I cannot see the complete structure. If SUPPLIER_INVOICE is not the first level you have to add the additional structures as well.

      Author's profile photo Christoph Bürgmayr-Posseth
      Christoph Bürgmayr-Posseth

      Hi Britta,

      Thanks for your help.

      That is the full string which works. (I now also added WBSELEMENT, works too)

      'SUPPLIER_INVOICE_REQUEST-SUPPLIER_INVOICE-SUPPLIER_INVOICE_ITEM_GLACCT-SUPPLIER_INVOICE_ITEM_GLPOSTIN-COST_CENTER'.

      But currently it only works in the (old) app: Message Dashboard

       

      In the new app Message Monitoring - I click on the edit buttong, but Cost-Center and WBSELEMENT are not editable.

      I noticed that the tab is named differently than in the old app, do I need to use a different path-field string?

      best regards

      Christoph

       

       

       

       

       

      Author's profile photo Britta Mangei
      Britta Mangei

      Hi Christoph,

      great to hear that it is working now.

      In general the changeable fields are using the same information in both monitors. Can you open an incident on BC-SRV-AIF describing the issue? This needs some investigation.

      Best Regards

      Britta

      Author's profile photo Om Prakash LNU
      Om Prakash LNU

      Hi Alexander Bundschuh

      Can we reprocess both inbound & Outbound proxy message ?
      I read about the OData Consumption you have explained , Are we saying that reprocess of Synchronous OData messages is not supported & Asynchronous OData messages can be reprocessed ?
      I am running on S/4 On-premise 2020.
      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      in general, you can restart async scenarios only, for sync a response has been returned to the caller already, here you can only show the error in the message monitor

      Alex

      Author's profile photo Om Prakash LNU
      Om Prakash LNU

      Thank you