Showing results for 
Search instead for 
Did you mean: 

When open Apps “Change Project Original Budget” URL in IE & Fiori screen is not same

Former Member
0 Kudos

Hi Experts,

Do you have any idea for this issue?
We are using S/4HANA 1610 Demo21 embedded system (S/4HANA+Fiori+Webdispatcher in same box)

Error: When open Apps “Change Project Original Budget” The URL in internet explorer tab and Fiori screen is not same

How to Simulate the error

  • 1.Login to Fiori Launchpad
  • 2.Click “Change Project Original Budget”

  • 3.The URL in internet explorer tab and Fiori screen is not same. vhcals4hci.dummy.nodomain --> wrong hostname

Steps done to troubleshoot.

  • 1.Check in RZ10 (profile parameter) --> no vhcals4hci.dummy.nodomain maintained
  • 2.Use F12. I see some error log :

    2017-08-18 12:34:38.965404 Component URL defined in target mapping does not match the URL retrieved from application index. A possible reason is that the component ID is not unique or that a wrong URL has been defined in the target mapping. The URL of the application index is used for further processing.See SAP note 2177717 for more information.

    Target mapping URL: /sap/bc/ui5_ui5/sap/sakp_genericui/
    Application index URL: /sap/bc/ui5_ui5/sap/sakp_gen_ui_s1/~17C0C256BE547A0C8434F1876F292DFE~5 sap.ushell_abap.bootstrap.abap

  • 3.Search SAP Note 2177717. Resolution -->1. Error caused by wrong URL in target mapping:
    Verify that the URL defined in the target mapping refers to an existing SAPUI5 application. If not, open the SAP Fiori launchpad designer and correct the target mapping.
  • 4.Open Launchpad Designer --> SAP_SFIN_BC_CO_BUDGET --> Target Mapping

  • 5.The application type is transaction. So we could not maintan the URL(/sap/bc/ui5_ui5/sap/<application_object>/) as per SAP Note 2428812 and 2177717.


  • a.2428812 - Cannot launch Fiori application from Launchpad & 2177717 - Duplicate id for SAPUI5 Fiori Application when running in SAP Fiori launchpad on ABAP system
  • b.
  • c.
  • Thanks,

    Fadzly Iqbal

    Accepted Solutions (1)

    Accepted Solutions (1)

    Former Member
    0 Kudos

    The related RFC:S4HCLNT100_HTTPS is pointing to the wrong hostname

    Answers (0)