The known use case is in an SAP Fiori environment.
However, the behavior can occur on any scenario.
To facilitate access to Fiori applications, aliases are being created at the Web Dispatcher.
Such aliases are being configured through the parameter "icm/HTTP/redirect_X".
icm/HTTP/redirect_X = PREFIX=/alias, FOR=server.example.com, TO=/sap/bc/ui2/flp?sap-client=<ZZZ>#<SemanticObject-action>
When the user accesses "https://server.example.com/alias", the target of the redirect is "...?sap-client=<ZZZ>%23<app specific>" instead of the expected "...?sap-client=<ZZZ>#<SemanticObject-action>", leading the user to the Fiori home page instead of the desired app.
- Product independent
- Release independent
- Client/Server Technology - ICM (Internet Communication Manager)
- Client/Server Technology - Web Dispatcher
- SAP Fiori environments
intent, semantic object, action, fragment, anchor, hashtag, pound sign , KBA , BC-CST-WDP , Web Dispatcher , BC-CST-IC , Internet Communication Manager , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , CA-FLP-FE-COR , SAP Fiori Launchpad Frontend Core and Services , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.