Skip to Content
Product Information

SAP S/4HANA 1809 Fully Activated Appliance – Known Issues

This blog covers latest information and known issues for the SAP S/4HANA 1809 Fully-Activated Appliance.

Note: The overview blog for this appliance can be found under

Cross Topics

Initial system performance after instance creation

When you create an instance, the initial system performance will be slow, especially within the Fiori Launchpad. Also, the first click on a Fiori tile will be significantly slower. This is due to initial caching in the system and will become faster if you continue working.

Other performance tuning tips are:

  • Choose the cloud provider location nearest to you (for good network latency)
  • Fiori rendering performance on the remote desktop is often slower than on your local laptop
  • The demo users contain a relatively large number of roles and Fiori tiles. You can copy these demo users in TCode SU01 and adapt accordingly (remove roles, personalize the Fiori launchpad, create your own roles / Fiori catalogs)

Note to SAP administrators: SGEN has been performed to pre-compile ABAP coding.


SAP Best Practices activation for India

The India localization for SAP Best Practices is not yet activated in clients 300 & 400 (the other 28 localizations are activated). The India activation is planned for the 1809 FPS01 update.


Fiori Launchpad

Fiori app “Monitor Central Purchase Contract Items” prompts for credentials

When clicking on the app “Monitor Central Purchase Contract Items” (assigned e.g. to users S4H_MM_DEM / S4H_MM or S4H_DDR_DEM), you will run into an authorization pop-up pointing to client 928.

The error is caused by a wrong client definition on the tile, which includes a parameter pointing to client 928 in the service URL. To solve this error:

  1. Access the Fiori Designehr via this url. https://vhcals4hcs.dummy.nodomain:44300/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CONF&sap-client=100&sap-language=EN#/Catalog/X-SAP-UI2-CATALOGPAGE:SAP_TC_PRC_COMMON
  2. Search for the “Monitor Central Purchase Contract Item” tile.
  3. Click into the Tile and remove the ‘sap-client=928’ parameter from the Service URL.
  4. Save and exit.


Web Assistant (for Fiori help, question mark in upper right corner) for instances behind a corporate firewall or within a virtual private cloud does not work

This is an expected behavior: The Web Assistant pulls content dynamically from the SAP Cloud Platform (SCP). If there is a customer-specific proxy between the S/4HANA backend server and SCP, this proxy needs to be configured in the Web Dispatcher of S/4HANA.
In the appliance, this proxy setting is empty by default since most instances are created in public Internet.
To adapt this to your corporate network settings, you will need PuTTY (or another SSH client) and the private key file (.pem) that was generated when you created the instance. Unless you chose to save it on your own computer, the .pem file can be downloaded from the instance details page.
For details how to log on with PuTTY, see this page > How to connect to a running instance via the secure shell protocol (SSH).
  1. Log on to the Linux backend system as root. .
  2. When logged on to Linux, enter su s4hadm (to change to user s4hadm)
  3. Enter cd /usr/sap/S4H/SYS/profile (to change to the directory with the Web Dispatcher config files)
  4. Enter vi S4H_ASCS01_vhcals4hcs to open the configuration file in the vi text editor
  5. Scroll to the end of the file where you will find the following text block:
    # system_0 and system_1 configure the FIORI web assistant for context sensitve help. If you are behind a corporate proxy use lines with # and enter your proxy information.
    # and comment/uncomment the lines for system_0 and system_1 respectivly
    # wdisp/system_1 = SID=DEF, EXTSRV=, PROXY=<PROXY_SERVER>:<PROXY_PORT>, SRCURL=/resources/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
  6. Enter your proxy name <PROXY_SERVER> and port <PROXY_PORT> in the respective parameters. Remove the comment # at the beginning of the two changed lines, and
  7. Delete or comment the two lines right after the text block (containing the default configuration without any proxy parameters).
    If you comment them, it should then look like below:

    #wdisp/system_0 = SID=ABC, EXTSRV=, SRCURL=/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF
    #wdisp/system_1 = SID=DEF, EXTSRV=, SRCURL=/resources/sap/dfa/help/, SRCSRV=*:*, STANDARD_COOKIE_FILTER=OFF​
  8. Save & quit vi.
  9. Lastly, restart the Web Dispatcher. Log on to https://vhcals4hcs.dummy.nodomain:44301/sap/admin/public/default.html with user bpinst and password Welcome1 (for this URL to work, you need to maintain your local hosts file)
  10. In Core System > Monitor > Status, choose Shutdown SAP Web Dispatcher from the drop-down menu and confirm.
  11. Reload the Fiori Launchpad in your browser to check if the question mark icon with the User Assistance is visible.

Issues in Demo & Business Scenarios

Credit Management cases are not created e.g. in Order-to-Cash demo scenario

When creating a sales order for a customer that has a credit block, the corresponding credit case is not visible in the Fiori app “Manage Credit Cases”.
Technical symptoms are errors in the web service call trace (in TCode SRT_UTIL), failed execution of the Adobe Document Service check reports such as FP_00_TEST (TCode SA38), or an SSL error when doing a connection test of the RFC connection ADS (TCode SM59 > HTTP to external servers).

The root cause is a missing trust relation between the ABAP and JAVA server (the Adobe Document Services on the JAVA server are needed for the Credit Management scenario).
Follow these steps to to fix the issue (takes ~ 5 minutes):

  1. Open Notepad on your computer and copy the following lines into a new notepad file
    -----END CERTIFICATE-----​
  2. Save the file as java_cert.cer on your local computer (it should look like this):
  3. Logon to your S/4HANA instance in SAP Logon (client 100)
  4. Follow the steps in the video in SAP Note 2333326 to import the .cer file into TCode STRUST (see video as from 2:20, the first part of the video just explains how to retrieve the above certificate file for any server)
  5. To verify success, do a connection test of the RFC connection ADS in TCode CM59. It should succeed now.


Be the first to leave a comment
You must be Logged on to comment or reply to a post.