In step 2 you need to upload the ST03 usage profile in CSV format. This is described in this SAP help file. So first create the file (in short, goto ST03, select last month, transaction profile standard, download to xls, remove header and save as CSV), then upload it in this step:
Upload front end and backend profile (in case on S4HANA embedded FIORI these are identical):
Name the analysis in step 4 and press the button to get to the analysis results:
Issues with SAP and browsers can be on both side: SAP and browser side. A new security note on SAP can suddenly block correct working of an SAP browser based function. A new security patch on the browser can also suddenly block it. Testing all combinations is a very hard process and almost impossible to do. The best way is to allow the users at least 2 different browsers. If one browser is having issue with an update, usually the other browser still works, which can be used as a workaround. It is not nice and pretty, but it gives you time to fix the issue. For issues on the SAP side: best to yearly patch the UI rendering notes (see this blog), and to carefully test notes that impact the web part (like security notes which are meant to close security holed in the netweaver web part).
The new generation of standard SAP FIORI apps can be easily be modified in layout and small extensions. This is called FIORI in app extensibility.
Questions that will be answered in this blog are:
How can I easily change the layout of a standard SAP FIORI app?
How can I hide fields or rename labels of a standard SAP FIORI app?
How can I extend a standard SAP FIORI app with a custom field?
Where can I find more background information on all possibilities for in app extension?
How do I technically enable in app extensibility?
How to enable in app extensibility transports?
Technical enabling of in app extensibility
Activate this SICF node: /default_host/sap/bc/lrep.
And assign authorization role SAP_UI_FLEX_KEY_USER to your user. Without the role, you will not get the needed menu item.
Cosmetic UI changes
We will use the app manage purchase requisitions as example. Go into the app and select a purchase requisition. At the point in time we want to make changes, we go to the Adapt UI menu option in the personal menu:
The Adapt UI screen will now open:
For example we will remove the block Batch. Select is and push the minus button to remove:
We do the same with Material supplier number.
And we want to change the location of the Desired vendor element: we use drag and drop to move it.
And we want to change the label Plant into the word Factory:
When we are done we publish the changes by hitting the Publish button:
Upon publishing the system will ask for a transport number to store the changes.
Best practice is to do the changes on development system and transport them (for the setup see below). Do not maintain UI changes directly on production.
Adding fields to the UI
We also want to add a new field to the UI. Select the block where you want to add a field and select the + symbol:
You can now add a field from the existing filed from the available business context:
Press Ok to add it.
If you want a new field, click on the + icon in the available fields. You are now redirected to the custom fields app:
Select the Plus icon now to create a new field:
As example we create a checkbox with title “Rush indicator”.
Choose Create and Publish. On the custom fields page, enable it for the correct apps:
Publish the changes.
Before you can use the field: please reload the app you were extending (server and UI definitions are out of sync).
Now go back into UI adaption mode and you are able to select the new field:
You can Publish now. New field is available for now for the users.
In case you were wondering where this data field is stored: it is stored in the S4HANA database.
In SE11 for table EBAN (purchase requisitions), you can see a new extend with the new field:
For different objects different tables are present. You need functional/technical SAP background knowledge to know the exact table.
Setting up the transport mechanism
To set up the transport mechanism for in app extensibility read this dedicated blog.
In short: transaction S_ATO_SETUP:
Set you packages and setup. Then activate and use the FIORI apps for transporting key user adaptation content.
This blog will explain the setup of FIORI notifications. They are sometimes also called FIORI push notifications.
The notifications on the FIORI launchpad are pushed to the end user on the top right part of the screen:
In this case 22 notifications are present.
Questions that will be answered in this blog are:
How to generically activate FIORI notifications?
Which specific settings do I need to perform to activate notifications for my specific workflow?
Hot to test FIORI notificaitons?
Where to find more background on FIORI notifications?
Setting up the FIORI notifications
Goto the customizing entry for notification channel configuration. We will set up the scenario for embedded FIORI. If you want to set up notifications for the FIORI gateway as a central step, more activities are required. These are listed at the sap help site.
Start with the Notification Hub RFC destination:
Set the destination to NONE and press execute:
Now set the backend system alias to LOCAL and press execute:
Now goto the menu entry for Manage Notification Providers to activate the desired ones:
Now we will setup the notification channel hub. Goto this customizing actions:
Start with the action Manage SAP System Aliases and map the LOCAL gateway to RFC destination NONE:
Now select the Publish the Notification ODATA Service entry and make sure the service /IWNGW/NOTIFICATION_SRV is published:
If not done, push the button Publish Service Groups, select LOCAL, press button Get Service Groups and search for /IWNGW/NOTIFICATION_SRV:
And publish it.
Now check in Manage WebSocket Endpoint that service NOTIFICATION_PUSH_APC is active:
In the customizing entry Activate and Maintain Push Channels, check that the push channels are properly active, and if not activate it:
Goto transaction SWF_PUSH_NOTIF1 to add the worflow task for push notifications. We will add task TS00008267 (this is used in the generic workflow verification):
Click on the text icon to maintain the text:
Make sure that in the technical job repository SJOBREPO (see blog) that the jobs for deadline monitoring and push notifications are running:
Testing the push notifications
Now you can start the verification workflow in SWU3 (see blog) or start test transaction /IWNGW/BEP_DEMO:
The results can be seen on the FIORI launchpad:
Notification icon not visible on the FIORI launchpad
If the notification is hidden, check the configurations in transactions /UI2/NWBC_CFG_SAP and /UI2/NWBC_CFG_CUST. It can be that an adminstrator has suppressed this function.
After update of a FIORI app UI5 code you will sometimes face issues that the browser or server still holds components from the old app version. This issue is there for both custom developed and for standard SAP UI5 apps. The root cause is the caching at multiple levels to assure highest performance. There are caches on frontend browser, gateway server and backend server.
Questions that will be answered are:
What do I need to do on the browser for refresh?
How do I clear the caches on the gateway frontend server?
How do I clear the caches on the backend server?
Browser cache refresh
After an update of the UI code best to clear the browser cache. In Chrome also: open the application in chrome and use key combination ctrl + shift + R to perform a hard reload.
Or run in Private or Incognito mode.
Best browser for testing is Chrome.
Gateway and backend server cache clearing
Use the following sequence to clear all caches:
1. Execute /IWBEP/CACHE_CLEANUP transaction in ECC system (or other backend system) as well as Gateway system.
2. Execute /IWFND/CACHE_CLEANUP transaction in Gateway system with checkbox checked.
3. In the gateway system, you need to do the below steps: