Make sure the following is done:
Components, Support Packages, and SAP Notes are installed.
Communication channels are configured.
All relevant OData services and ICF nodes are active.
Roles and authorizations are assigned.
Symptom: Launchpad or launchpad designer does not display catalogs.
Symptom: Launchpad or launchpad designer does not start.
If the launchpad does not start or display catalogs, there can also be other causes, such as with SAP Gateway, back ends, or authorizations.
For general information about troubleshooting launchpad and launchpad designer, see the following:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon .
For SAP NetWeaver 7.4, see the documentation on SAP Help Portal at http://help.sap.com/nw74 .
For information about troubleshooting the coding, SAPUI5 applications in general, and browser-specifics, see the following:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon .
For SAP NetWeaver 7.4, see the documentation on SAP Help Portal at http://help.sap.com/nw74 .
For more information, see SAP Note 1797736 .
SAP Jam Integration
Symptom: HTTP error 400 Bad Request
Possible Causes |
Solution |
---|---|
This error can occur in the case of an incorrect request. If you are sure that your request is correct, the ict/odata_compatible_urls instance profile parameter may not be set to true. This can cause a truncation in the request URL. |
|
For information about troubleshooting the SAP Jam integration, see the SAP Library as follows:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74
Symptom: Search does not display results.
Symptom: Search field is not displayed.
For more information, see Setup of SAP Fiori Search.
SAP Fiori Apps in General
Symptom: A specific app is not displayed in the launchpad.
Symptom: App does not start.
Symptom: App does not display any data.
Symptom: App Launcher does not display dynamic data for app (counter or similar).
Possible Causes |
Solution |
---|---|
User is not authorized to display the app. |
Assign roles and authorizations. Check the browser log. Check the SAP Gateway error log (transaction /iwfnd/error_log). Check if the back end is connected. |
Symptom: The app displays data of other users or data that is created by another user ID.
Symptom: Error message “Your user is not configured properly. Please contact system administrator”.
Possible Causes |
Solution |
---|---|
Trusted RFC not configured correctly. |
For SAP Fiori System Landscape with ABAP Environment:ABAP Servers: Setup of Communication For SAP Fiori System Landscape with SAP HANA Database or for SAP Fiori System Landscape with SAP HANA XS:ABAP Servers: Setup of Communication |
Fact Sheets in General
Symptom: Fact Sheet is not displayed.
For more information, see Setup of SAP Fiori Search.
Symptom 1: Data is missing on a fact sheet.
Symptom 2: Problems during navigation: You cannot call fact sheets or back end transactions.
For more information, see SAP Note 1998366 .
Analytical Apps in General
Symptom: OData service returns a 500 (Internal Server) error with a message in the response “Invalidated View”.
Symptom: Activation error while importing delivery units.
For more information, see SAP Note 2000409 .
Materials Management (MM) Approval Apps
For issues with the following apps, see SAP Note 2000409 :
Approve Purchase Requisitions
Approve Purchase Orders
Approve Purchase Contracts