Symptom
- App could not be opened either due to an incorrect SAP Fiori launchpad configuration or a missing role assignment.
Failed to resolve navigation target "#Shell-startWDA?ACTION=...". This is most likely caused by an incorrect SAP Fiori launchpad content configuration or by a missing role assignment. - In console we can find below information.
GET https://<hostname>:<port>/sap/opu/odata/UI2/INTEROP/SystemAliases(id='LOCAL')?$format=json 404 (Not Found)
Error (404, ) in OData response for GET "/sap/opu/odata/UI2/INTEROP/SystemAliases(id='LOCAL')?$format=json": HTTP request failed
Details: Requested resource could not be found - {"requestUri":"/sap/opu/odata/UI2/INTEROP/SystemAliases(id='LOCAL')?$format=json","statusCode":404 - Note 3349742 has already been applied.
3349742 - /UI2/INTEROP - Resolve System Alias that is Mapped to an Empty Target - Target Mapping contains System Alias LOCAL in catalog.
Read more...
Environment
SAP FIORI FES FOR S/4HANA 2022
Product
SAP S/4HANA 2022
Keywords
LOCAL,404,SystemAliases,/UI2/INTEROP , KBA , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview