Skip to Content

I have been ask to describe how to use the SAP EarlyWatch Alert Workspace to get informed about the most important technial issues in an SAP landscape. Here is what I usally do in a cookbook format:

To do’s:

  1. Create a weekly entry in your calendar
  2. Watch your favorite systems: Create a filter variant for Workspace
  3. What to look out for:
    • New severe alerts in your landscape
    • HANA systems that haven’t send data in two weeks
    • Top systems with new red alerts
    • Response time increase in ABAP systems
  4. Check your favorite systems’ KPIs



1.    Create a weekly entry in your calendar

The SAP EarlyWatch Alert(EWA) is a weekly service which collects data from Monday until Sunday and transfers it to SAP. Most of the downloads arrive on Monday and Tuesday, however you can also choose another day of the week for the transfer.

Since the EWA Workspace has no notification mechanism yet, it is best to create a weekly-reoccurring entry in your outlook calendar with a link to the SAP EarlyWatch Alert Workspace.

2.    Watch your favorite systems: Create a filter variant for Workspace

The application offers filters for customer number, system and database type. If you are responsible for one or several customer numbers and all the systems of these customer numbers, then it is best to use the customer number filter. If you are responsible only for specific systems from one or many customer numbers, use the filter dialog for System ID.

You can save your filter values as a variant, give it a meaningful name and save it as default variant. Consequently, the app will show your favorite systems automatically when you open it via link or tile.

3.    What to look out for

New severe alerts in your landscape

The Alert card in the Workspace shows only the alerts that are most critical and will give the whole report a red rating. You directly see the alert short text and can navigate to the EWA chapter with the recommendations. Per default only the new alerts are shown from the latest report available and “new” means compared to the previous report.

HANA systems that haven’t send data for more than 2 weeks

It is important that especially HANA systems send data on a weekly basis, because only than we can provide complete time series for important HANA KPIs and show trends. Please make sure that your systems are sending the data on a regular basis. In the donut chart on the workspace you see 2 grey categories: “No current service data” and “incomplete data”. See SAP Note 1684537 for troubleshooting.


Top systems with new red alerts

The bubble chart cart displays the top 10 systems either by number of users or database size. Check for red bubbles: This indicates that a large system has a very critical alert, which is new this week.

Response time increase in ABAP Systems

The bar chart “Top Deviation in Response Time” shows the Top 5 systems that are much slower than the long-term average or much faster. A drill-down into the history of the response time can reveal a bad trend in the response time that should be followed up with a support service.

Check your favorite systems in the dashboard

The EWA dashboard shows technical KPIs per system. Watch out for critical findings for CPU and Memory utilization indicated in a yellow or red circle.

The system section of the dashboard shows 4 trend charts for the last 5 weeks. There may be a bad trend in response time or data growth. You get the definition of the KPIs, when you press on the information icon.

Check out the “What’s new?” card in Workspace to see the latest blogs and videos.

Feel free to share your favorite recipes how to use the EWA cloud apps in the comment section!

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Alexander Zimmer

    Prima, herzlichen Glückwunsch das ist eine sehr gute und erfrischend neue Aufbereitung der sehr wertvollen Daten, die der SolMan liefert. Weiter so und vielleicht gibt es ja bald auch noch mehr Security Themen wie:

    • Patch Status des Systems bzw. alter des SP Releases (24-monats Regel)
    • Gateway Status *.* Einträge
    • Schwache Passwort Hashes
    • RFC Callback Security

    das wäre Klasse und würde uns bei den Sicherheitsthemen den Rücken stärken.


Leave a Reply