Fiori Launchpad - Notification Configuration

[esakkidurai01]

Configuration of Notification in Fiori Launchpad - Embedded System

 

Dear SAP Communities,

In this blog post, we will dive into the configuration of fiori notification, including the backend configuration and customization options. This blog will equip you with the knowledge and insights to configure the notification effectively.

Throughout this blog, we will learn the fundamental concepts, underlying architecture, configuration options and integration possibilities of fiori notification configuration.

---

Below are the key steps involved for fiori notification configuration:

1. Introduction

2. Create Roles from PFCG Role Templates

3. Activating SICF node

4. Publish Notification OData Service

5. Setup Push Channel

6. Create Backend System Alias

7. Register and Activate Notification Provider

8. Enabling Notification Icon in Fiori Launchpad

9. Triggering a Notification to the Notification

---

 

1. Introduction:

The SAP Fiori Notification Icon is a visual representation used in SAP Fiori Launchpad to indicate the presence of notifications or alerts for the user. It is typically displayed as a small bell-shaped icon which shows the new or unread notifications.

When there are unread notifications, the bell icon is usually highlighted or may display a badge with a number indicating the count of unread notifications. The exact design and appearance of the notification icon can vary depending on the specific Fiori application or theme being used.

The Fiori Notification Icon is a key component of the SAP Fiori user experience, providing users with a convenient way to stay informed about important events or tasks requiring their attention within the SAP system.

2. Create Roles from PFCG Role Templates:

1. Run transaction code PFCG.


2. Give the Role name. In our example, it is called “Z_PUSH_NOTIFICATION” and click the Single Role button.
   

   

   
   


3. Input “Description” as Notification Icon Implementation.


4. Click Save button.


5. 
   

   Go to Authorization tab.

   
   

   

   
   


6. Click Change Authorization Data Button.


7. On the next screen, it will prompt for choosing a template. Select one of the templates below.
   Three of the authorizations will be inserted. Then, click on Generate Profiles button.Click Continue button..


8. Now go back to User tab.


9. Enter the User id’s of the User to receive notifications in their Fiori Launchpad.


10. 
    

    Click Save button.

    
    

    

    
    NOTE:
    
    
    
    • Please repeat the above steps to create the other PFCG roles from the role template if necessary.
    
    
    • Assign the newly created roles to the eligible user based on their role.
    
    
    
    

3. Activating SICF node:

1. Run T-code sicf.


2. 
   

   Enter “/sap/opu/odata4” in the Service Path field and click Execute button.

   
   


3. 
   

   Right click the sicf node and click “Activate Service”.

   
   


4. 
   

   Click the second “Yes” button.

   
   
   
   
   

4. Publish Notification OData Service:

OData V4 service /IWNGW/NOTIFICATION_SRV is used to create notification and execute all other task with respect to this notification.

1. Run the transaction spro and go to the below mentioned path (or) Run the transaction /N/IWFND/V4_ADMIN which opens the same.


2. On the next screen, click on Publish Service Groups Button.


3. Enter the System Alias as LOCAL and click on GET SERVICE GROUPS. It will show the list of Not Published Service Groups below.


4. In that list, select “/IWNGW/NOTIFICATION” and click PUBLISH SERVICE GROUPS button.


5. Click on Continue.
   Then, it will prompt for a Customizing TR. Create one for capturing the Service group publishment. Select the TR and click on Continue.
   Now, a Service Group for Notification Channel is published.
   After the Service Group is published, we need to test the Service Group.


6. Now go back to the published Service Group, select it and click the SERVICE TEST button.


7. Click on Execute Button.
   The Status code is 200 (Green). So, the Connection works well.

5. Setup Push Channel:

Notifications use an ABAP Push Channel to push notifications to the Fiori Launchpad. The recommended approach is to use a WebSocket connection for this purpose. Web Sockets establish a bi-directional communication channel between server and client. Using Web Sockets, a server can push notifications to the client.

1. Go to the below path in the Transaction SPRO and execute Manage WebSocket Endpoint.


2. Enter “NOTIFICATION_PUSH_APC” in Service Name and click EXECUTE button.


3. Right click on the sicf node and activate the services.
   The Notification Push Service is activated and now we need to activate the PUSH NOTIFICATION.


4. Now, go to the below path in the Transaction spro and Execute Activate and maintain Push Channels.


5. Click on New Entries Button.


6. Give the below Inputs:
   
   
   
   • Push Channel ID: SAP_WEBSOCKET
   
   
   • Push Channel Serial Number: 10
   
   
   • Check the Is Active? checkbox.
     
     
   
   
   
   


7. Click on Save Button and it will prompt for a Customizing TR.
   Create a new TR as Notification Icon Implementation and capture the changes.

6. Create Backend System Alias:

1. Go to the below path in the transaction spro and execute Enter the Backend System Alias.


2. Enter Local in the Backend SAP Alias and click Execute button. The system alias will point to the backend system.
   

   Now, the Backend System Alias is maintained successfully.

   
   


3. Now, go back to the below path in Transaction SPRO and Execute Enter the Notification Hub RFC Destination.


4. Since we are in Embedded Scenario, Enter NONE in the SAP Gateway RFC Destination and click Execute Button.
   After Executing, the screen will display as follows:


5. Now, go back to the below path in Transaction spro and Execute Create bgRFC Destination.


6. Click on Create button and Enter the Destination as IWNGW_BGRFC and Connection Type as 3 RFC connection to ABAP system and click Continue.


7. On the next Screen, Open Special Options tab and select Classic Serializer and No outbound bgRFC.


8. Click on Save Button and select Yes if it prompts for the below message.


9. Now, Click Connection Test.


10. Check for the below specifications. If same, then the connections work well.


11. Go back to the below path in Transaction spro and Execute Register RFC Destination for Background Processing.


12. Go to Define Inbound Dest. tab and Click on Create Button.


13. Enter the Inb. Dest. Name as IWNGW_BEP_OUT_BGRFC.


14. The Destination will be created with the prefix Q. Click on Save Button.


15. Go back to the below path in Transaction spro and Execute Create bgRFC Supervisor Destination.


16. Go to Define Supervisor Destination Tab.
    If you look at here, the destination is already created. If not, follow the below steps to create the Destination.


17. Click “Create” button.


18. Enter the below Details and click on Save button.

7. Register and Activate Notification Provider:

1. Go to the below path in Transaction SPRO and Execute Register Notification Providers.


2. Click on Create Button.


3. Enter the below details:Provider ID: ZIWNGW_DEMO1Provider Class: /IWNGW/CL_DEMO_NOTIF_PROVIDERDescription: Demo Notification.Note: Please put a letter “Z” before “IWNGW_DEMO1” or you will get error when assign it to a package in the following step.


4. Click on Save Button.


5. It will prompt for a package. Create a package called ZNOTIFICATION_PACKAGE and capture it in the same (Notification Icon Implementation) Workbench TR.
   The new Notification provider will be added successfully.Note: If you look at here, there is already one Demo Notification provider is configured. We can use that also to trigger a Demo/Test Notification.


6. Now, go back to the below path in Transaction SPRO and Execute Manage Notification Providers.


7. Click on New Entries and create the below entry.


8. Click on Save and it will prompt for a Customizing TR. Use the same Customizing TR that is created before for setting up Push Channel.

8. Enabling Notification Icon in Fiori Launchpad:

The Notification Icon will appear in your Fiori Launchpad by the Z_PUSH_NOTIFICATION Role itself.

For that, follow the below steps.

1. Go to Transaction PFCG and edit the role Z_PUSH_NOTIFICATION.


2. 
   

   Go to Launchpad Catalog in the Transaction Button.

   
   


3. Enter Catalog ID as /UI2/CONFIG_NOTIFICATION and click on Continue.
   

   Now the notification icon should be visible in your fiori launchpad.

   
   Fiori Launchpad before updating Role:
   
   
   Fiori Launchpad after updating Role:
   
   

9. Triggering a Notification to the Fiori Launchpad:

There are many Notification providers to provide the notifications, Here we will configure two such scenarios of Notification Providers.

Scenario 1: A Demo Notification Provider for testing the Notification Channel:

1. Run transaction code /N/IWNGW/BEP_DEMO.


2. Enter the Provider ID as /IWNGW/DEMO.


3. Enter the user that you want to send notification.


4. Click Execute.


5. After executing, the screen will display as below


6. Login to Fiori Launchpad, you will see the badge count.By this way, we can test the Notification Icon is configured or not by triggering a test notification to the user ID.

Scenario 2: A Standard SAP Business Workflow Notification Provider delivered by SAP. [Workflow Configuration]

1. Run transaction code SWF_PUSH_NOTIF1. The screen will display as below:
   

   Make sure the Provider button is in green. If not, we need to activate/register Notification Provider SAP_BUSINESS_WORKFLOW.

   
   


2. Click Display/Change button to change to edit mode.


3. Click Create New Entry button.


4. Create a new entry for the task or the workflow step you want to create notifications.
   
   
   
   • Task Number: Enter a Task or Workflow ID.
   
   
   • Step: If you enter a task in the “Task Number” Field, this field will be disabled. If you enter a Workflow in the “Task Number” Field, please define a step to create notifications. If you want to have notifications for more than one steps, you need to create a new entry for each step of the workflow.
   
   
   • Active: if you set the “Active” flag, push notification will be enabled.
   
   
   • Groupable: it defines whether the notifications can be grouped by type or not. It determines whether group texts can be maintained or not. Create a new entry for the task or the workflow step you want to create notifications.Configure each Workflow ID by using the same steps.
   
   
   
   


5. Once it is done, Click Save button.


6. To make the changes you have made to your workflow visible in your SAP Fiori Launchpad, refresh the cache using the transaction /IWNGW/H_CLEAR_CACHE.

After completing all the above steps, trigger a Workflow that should hit the SBWP Inbox and Fiori My Inbox App. Then check the Fiori Launchpad, you can see Notification has been generated for the Workflow.

I'll try to keep updating the latest features and developments about this Notification Configuration.

Happy Reading.

Thank you! 

[srinihog]

Hi Durai,

Thank you for the detailed hands-on blog.

I have followed all the steps, every step execution is fine, and I completed all the configuration as per the blog. When I execute a custom workflow, SWBP inbox and Fiori inbox updating with new work items but not getting the notifications.

Please find attached screenshots and help me to understand what I am missing.

 

 

Regards,

Srinivas

[esakkidurai01]

Hi Srinivas,

Have you tried triggering the Notification using the Scenario 1. If yes, please share the result displayed in "Test Create Notification" screen.

[srinihog]

Hi Durai,

 

Yes, I tried scenario 1 and with that I am getting the notification.

Notification

 

Notifications in Fiori launchpad

Regards,

Srinivas

[esakkidurai01]

Hi Srinivas,

Sorry for the delay.

If the notification is sent to the Fiori Launchpad using Scenario 1, then the notification icon is set up perfectly.

If Scenario 2 applies to you, please verify that the Fiori Launchpad's Custom workflow is set up to trigger notifications. You should also verify that the SWF_PUSH_NOTIF1 transaction is configured correctly.

[peter_quintus]

Hi Durai,

thanks for your detailed documentation.
In our case we have a separate Fiori Front End Gateway system.
I am therefore not sure which of your described steps have to be performed in the front-end gateway system and which in the ABAP back-end system?
Could you possibly include this in the documentation?
That would be very helpful for us.

Best regards Peter

[kulsar_007]

Hello Durai,

 

I have a requirement to get the pop-up notification for MIRO Invoice, could you please share some more details on how to get the pop-up notifications?

Business scenario:

in case of cross company STO PO we get the warning message but in Fiori app how to set up warning message pop up? Currently I am getting warning message but not getting pop up. Business user expectation is instead of clicking on warning he should get warning message pop up after enters PO n umber into MIRO so even user forget to check messages still due to pop up its easy for user to see pop up and act accordingly.

Cross-company code transaction in PO item 4500098011 00010, company code 1000

Message no. M8393

 

Please note we are using SAPUI5-on-ABAP: 1.71.57

 

It would be great help if you could share your experience in setting up pop-up message launch.

[esakkidurai01]

Hello Quintus,

All the described steps in the blog has to be performed in the Backend system which will reflect back in the Front-end. So, please proceed with the configurations in the ABAP back-end system.

[yannick_meertens]

What to do with this error message?