SAP GUI default change to Edge

After upgrading to SAP GUI 7.70 you can change the default browser from Internet Explorer to Edge.

More on SAP support for browsers in general can be found in this blog.

Prerequisite: install WebView2

First read OSS note 2913405 – SAP GUI for Windows: Dependencies to browsers / browser controls. This note describes the need for you to download and install the Microsoft WebView2 framework:

Impact of WebView2: 2901278 – SAP GUI HTML Control based on Chromium Edge: Legacy HTML does not work (correctly) / present limitations.

Switch browser setting for SAP GUI

Now you can go to the settings of you SAP 7.70 GUI and change the default browser in the Interaction Design/ Control Settings:

If fallback to Internet Explorer is still required, read this note: 2957665 – SAP GUI HTML Control: Browser Control Fallback Configuration.

In case the option is locked: 3191784 – Edge (based on Chromium) HTML control option is locked in the SAP GUI Control Settings.

If you need to build a workstation package with the default Edge setting, read this OSS note: 3221242 – How to set the Edge (based on Chromium) as the default browser control in single file Installer aiming SAP GUI distribution on multiple workstations.

Switch browser setting for SAP Business Client

For SAP business client the settings are in the Settings/Browser section:

Here you can choose the browser and download location to be used.

Chromium security updates

There might be a lot of hotnews and security OSS notes on the Chromium part. Main OSS note: 2622660 – Security updates for the browser control Google Chromium delivered with SAP Business Client.

OSS notes

Relevant OSS notes:

Relevant blogs on browsers and SAP web technology

More blogs on browsers and browsing technology:

  • HTTP/2 support for FIORI and ABAP web applications: read this blog.
  • TLS v1.2 setup in ABAP system: read this blog.
  • Webadmin pages disablement: read this blog.
  • More on SAP support for browsers in general can be found in this blog.
  • How to check HTTP usage in your system: read this blog.
  • FIORI gateway timeout settings: read this blog.
  • FIORI cache refresh: read this blog.
  • FIORI gateway tips and tricks: read this blog.
  • Webdynpro Unified Rendering updates: read this blog.

Reducing S4HANA upgrade downtime: ZDO, zero downtime option

Next to nZDTM (near zero downtime) there is now a new option called ZDO (Zero Downtime Option). This new option even further reduces the downtime of an upgrade to a newer version.

The ZDO option is primarily available for S4HANA upgrades (for example upgrade from S4HANA 2020 to S4HANA 20201), but is also available for products based on the same ABAP version, like SAP Focused Run.

How does the ZDO work?

ZDO is the next evolution of the shadow system. Now not only the code is duplicated, but also the data and settings. This is done in a so called bridge system. Postings are duplicated in the main and in the bridge system.

In this way the business downtime is further reduced:

A ramp down, restart and ramp up is still required.

Technical background

All the technical background and restrictions are listed in OSS note 2707731 – Prerequisites and restrictions of Zero Downtime Option of SUM for SAP S/4HANA and training ADM330e.

The note states as well that the basis person must have followed the training ADM330e before the customer is allowed to perform the ZDO option. The option is released for customer, after training. Why is training required? The option is technically very nice, but also complex (updates are done in both the old and new release). The restrictions and execution must be done correctly and in high quality fashion. This cannot be done without proper training.

You should also do a full dress rehearsal of the ZDO upgrade including people posting data in the system during the bridge phase.

The most common use case is an S4HANA upgrade. But the ZDO upgrade can be used in other used cases as well. For example SAP Focused Run can also be upgraded with ZDO. There are special notes, instructions and restrictions: 3269755 – SAP Focused Run 4.0 Support Package 00 – Update Preparation and Postprocessing Documentation. Check the notes carefully for your specific use case.


ZDO will use more memory since it will have 2 database schemas. Check and monitor this carefully on your test upgrades and extrapolate to production. A ZDO upgrade does require a test run on full production copy size.

Execution of ZDO issues

During execution of ZDO, you will get far more issues and errors as compared to the downtime optimized scenarios. For this reason, the first ZDO upgrade you execute should be on a sandbox system. Preferably as a copy of your productive system. You will learn a lot of things on the sandbox upgrade, to make the real upgrade later on go smooth.


Some addons might block the upgrade. Some can still be allowed in the upgrade, but cannot be upgraded along with the upgrade and have to remain at the same version. At the bottom of note 2707731 there is an always up to date excel file containing the Allow List for addons.

OSS notes in ZDO checks phase

During the prechecks and later even in shadow system build up, SUM will come with list of OSS notes that need to be applied in main system or in shadow.

For the real upgrade: already apply all the notes on the development system before the upgrade and transport these to production.

Database inconsistencies

All database inconsistencies must be resolved. Repair via SE14, see blog.

BI system settings

ZDO is currently only supported for embedded BI scenario. This might mean you need to get help from your BI team on de-activating some BI content.

To find out what is blocking: go to transaction SE24 and enter class CL_RS_UTILITIES. Start the test tool and launch method GET_SYSTEM_SCOPE. If the answer is DATA_WAREHOUSE, this will block the upgrade. Use your debug skills (or ask ABAP developer) to see which items are throwing roadblocks. Then de-activate or delete that content (with help of your BI team).

Old HANA transport containers

Some old HANA content might block the ZDO upgrade. Read more on this in OSS note 2982320 – HTA for HDI: Error in execution of HDI call: insufficient privilege. Steps to solve: repair privileges on the ABAP HANA user. Run program SCTS_HTA_ADMIN in repair mode.


Background blog from SAP: read here.

SNOTE revamp

After many years of faithful service, SNOTE got a revamp from SAP.

Questions that will be answered in this blog are:

  • How does the new revamp of SNOTE look like?
  • How can I get this new revamp of SNOTE?
  • Can I download latest versions of OSS notes in batch mode?

If you update main SNOTE OSS note 1668882 – Note Assistant: Important notes for SAP_BASIS 730,731,740,750,751,752,753,754,755,756, you will get this message:

New revamp SNOTE

OSS note 3051466 – Simplified Note Assistant: SNOTE Revamp describes the main functions and background of the revamp of SNOTE.

Main changes listed in the note:

  • A new Home screen, where the user work list and Note Browser is integrated in a single screen. The work list and search results are displayed in tabs to improve usability
  • Possibility to perform a Note Search for Valid Notes in SAP ONE Support Launchpad, and then download it from the search results 
  • Provision to mark/unmark Notes as your ‘Favorite’
  • Option to set up background jobs which will automatically look for and if required, download newer version of Notes which are already in your system
  • Implementation of Notes has been streamlined with lesser pop-ups and better error handling
  • Improved display of Manual Text during a Note implementation. It will now also be displayed during de-implementation of a Note.
  • Changes in the Note Display screen, including a compact header section, provision to display only valid corrections and only the actions that will be possible for the given Note will be displayed
  • An improved display of Note Log 
  • Provision to launch reports which will show the details of all the prerequisite and successor Notes, or the list of repository objects affected by the Note
  • Ability to customize the Note Assistant using the ‘Note Assistant User Settings’. The Note download procedure can also be provided here
  • Additionally, the tool will now automatically remember some of the user choices made in the user interface

Starting SNOTE now looks like this:

The settings button shows easily you can set your own preferences:

Updating OSS notes versions is possible now via the menu Download latest version of Notes, and then you can choose to run in foreground or (new great function) in background.

For the last update run you now can get a nice overview of the results of the updates:

Installation of new SNOTE revamp version

The new revamp version of SNOTE is standard in S4HANA 2021. You can also install it separately.

Steps to follow:

  1. First apply the prerequisite notes listed in OSS note 3051466
  2. Make sure the TCI file of OSS note 3051466 is placed in your system (read more on TCI notes in this blog)
  3. Apply OSS note 3051466
  4. Apply OSS note 3092620 – SNOTE – Adapting Download of Latest Version of SAP Notes in Background for Revamped Note assistant
  5. Check if newer bug fix notes are present (search for SNOTE Revamp as key word in component BC-UPG-NA)

Regularly update note 3093855 – Note Assistant: Important SAP Notes for the Revamped Note Assistant as well. This is containing all fixes for the revamped SNOTE.

EWA tips & tricks

SAP early watch (EWA) contains information on your system that might already or in the future impact performance and security.

A periodical review of the EWA is needed.

This blog contains tips & tricks for the technical working of the EWA reports.

For other frequently asked questions, read the note 1257308 – FAQ: Using EarlyWatch Alert.

SAP EWA generation

The EWA can be generated from SAP solution manager itself. Or you can use SAP Focused Run or Solution manager as data collection system, and than relay the information to SAP. The end result can then be seen on the online EWA workspace in the SAP support portal. More information on the EWA workspace can be found in this blog.

Since most new functions are added in the EWA workspace it is the best way forward. It is also less maintenance work. The only thing to do is to keep sending the data. Any new reporting function is done by SAP. SAP will also take care to have the content updated.

So all in all, if you are currently doing the EWA generation directly in SAP solution manager, consider to switch to the model where you send the data to the SAP EWA workspace via solution manager or via SAP Focused Run.

Setup in SAP Focused Run

A good manual for SAP Focused Run for EWA setup can be found on these reference sites:

Troubleshooting guide for EWA in SAP Focused Run, follow this link.

Also check OSS note 2715504 – Configure Early Watch Alert Job.

EWA in solution manager

General activation process of EWA in solution manager is described in OSS note 2729186 – General Process of EWA Generation in SAP Solution Manager 7.2. If an add hoc extra EWA needs to be generated, follow the steps in OSS note 2357073 – How to Create an Ad Hoc EarlyWatch Alert SAP – Solution Manager 7.2.

Adding email receivers is explained in OSS note 2282944 – EarlyWatch Alert: Solution Manager 7.2 how to setup/configure EWA reports or add email recipients.

Content update of SAP EWA content in SAP solution manager is required at regular intervals. The procedure is described in OSS note 2732608 – How to replace the Service Content (AGS_UPDATE).

Known issue list for EWA

The known issue for EWA is kept as list by SAP on this page. And OSS note 3138592 – Known Issues with the EarlyWatch Alert (EWA).

Troubleshooting when EWA is not sent to SAP

When you have issues that the EWA data is not sent to SAP properly, follow the checks in OSS note 1684537 – EarlyWatch Alert not sent to SAP: troubleshooting guide.

Removing unwanted secondary HANA database from the EWA

If you setup a secondary HANA database in DBCO, that database might appear in the EWA of the primary system. To get this unwanted information out of the EWA follow the steps as described by SAP in this page. Basically add the description NON_EWA_ in the secondary connection:

Setting up the BKF section in the EWA

OSS note 2282310 – Business Key Figures for EWA report contains the steps to get the BKF chapter activated.

Make sure in the managed system the user running the EWA data collection has the special role SAP_MANAGED_BPOANA_DIS. This is cause number 1 of issues.

If you make the settings, you would have to wait 3 weeks before the data is filled properly.

To gain speed, you can use the Express option. This option is explained in OSS note 2821062 – BKF Express Option/Manually running the BPMON job.

The UI of Business key figures Chapter Setting settings in the EWA is terrible. Please use the scroll bars to go to the right part. And the instruction mentions that you need to double click on a button or tab. This is correct. If you click once, nothing will happen. You really need to double click. This is completely counter-intuitive. But if you don't do it, it will not work, and you loose a lot of time.

If it still does not work, don’t hesitate to raise a message to SAP for component SV-SMG-SER-EWA.

SAP might ask you to apply the note 2477832 – SAP EWA Special Content BKF – on demand data collection (routine update & ZReport) as a workaround.

Generic background information

EWA wiki of SAP: link.

Generic background information on EWA can be found in these OSS notes and blogs: