Mobile Start-Push Notification

[BilalFaikoglu]

Hi,

We want to connect our On-prem system with Mobile Start. After all configuration/assignment, we can see documents or pending list on Mobile Start, but we couldn't see/get push notification on our mobile devices. I will put steps we've done on the system. Can you guide us on what's missing?
For example, when an order is created, the goal is to display a notification on Mobile Start, as shown
in the images.

Completed Sections:
BTP Build Workzone has been enabled for mobile start notifications. The notification settings have
been activated from the site directory settings.

Notifications have been activated in the settings section.The Cloud Connector structure is as follows.

The S/4HANA system has been connected to the BTP system via Cloud Connector and Destination.A parameter has been added to the Destination Parameter section.

NOTIF_SERVICEPATH = /sap/opu/odata4/iwngw/notification/default/iwngw/notification_srv/0001

An RFC destination has been created for the SAP BTP notification. The RFC was set up using T-Code
SM59.Certificates have been added.

The SAP S/4HANA administrator accessed T-Code SE80 to create an OAuth 2.0 client profile.The SAP_CLOUD channel has been added to the notification channel using T-Code SPRO.

The IWNGW_NOTIF_CLOUD_BGRFC queue instance has been added to the bgRFC section.
The Notification section has been added to the SFF Notification configuration.

For testing, when a notification was sent via SAP GUI, the test notification was received in the Fiori
Launchpad, but no notification was received through BTP Build Workzone.

BTP Notification Screen
The configuration for receiving notifications when SAP standard processes occur, such as the
creation of a purchase order, has been completed. The steps are listed below:
PFCG role templates have been created. The Z_PUSH_NOTIFICATION single role has been created.
The SICF node has been activated. The Service Path field has been set to "/sap/opu/odata4".
The Notification OData Service has been published. The OData V4 service
/IWNGW/NOTIFICATION_SRV has been created.

The Push Channels have been configured. An ABAP Push Channel is used to send notifications to the
Fiori Launchpad. The recommended approach is to use a WebSocket connection for this purpose, as
WebSockets establish a bidirectional communication channel between the server and the client. The
WebSocket setup has been completed.
The Define Inbound Destination configuration has been checked.
The notification provider sections have been saved and activated.

New records have been created in the Notification section using T-Code SWF_PUSH_NOTIF1.

Example Notification

A connection has been established between Fiori Launchpad and BTP Workzone. Notifications for
the incoming orders appear in the My Inbox section of the Fiori Launchpad, but no notifications are
being received in BTP Workzone, even though the orders are visible in the My Inbox there. Due to
the inability to receive notifications, the Task Center has been set up.
Task Center Setup Procedures:
The SAP Task Center Mobile Start setup has been completed. The configuration was done through
the Launchpad Service by the site administrator.

A new Group and Role have been added.

An X.509 certificate has been applied and the configuration has been updated in the Cloud
Connector section.
The service settings for Task Center have been configured in the S/4HANA system.
The Identity_Authentication_Connectivity_IDS URL has been configured in the BTP subaccount.

A destination has been created in the BTP Destination section to connect to S/4HANA.

At the end, we couldn't see any item on Task Center list.

[thomas-bruckner]

Dear @BilalFaikoglu,

the configuration process to expose notifications from SAP S/4HANA to SAP Build Work Zone, standard edition and thus also SAP Mobile Start is explained in detail in the Learning Journey "Setting up SAP Mobile Start with SAP S/4HANA on SAP Build Work Zone". In there, it exists a dedicated unit for "Receiving SAP S/4HANA Workflow Notifications".

Logically the first step would be to successfully expose the notification to be visible in SAP Build Work Zone, standard edition. Push notifications to SAP Mobile Start do work automatically if everything is configured correctly. A typical pitfall for push notifications to fail to be delivered is a mismatch of the user identifier.

If you are unable to solve the configuration with the mentioned learning journey, you may reach out to our product management team by writing to our central inbox: sapmobilestart@sap.com

Kind regards,
Thomas

[Private_Member_231371]

Hi @Thomas, thanks, what user identifier attributes that should match on S4 and IAS for Work zone? We have a setup where notifications are correctly pushed to Work zone from S4/H but Push notification on mobiles not working. The SMP logs on Work zone says that notification were requested but users not registered for push notification. Although we could see them registered and even sent them test messages successfully.

Thanks

MK

[thomas-bruckner]

By default, the Subject Name Identifier configured in the entry for SAP Build Work Zone under Applications in your Identity Authentication tenant is used by SAP Mobile Services to identify users, e.g. for push notifications. When you check the "Push Registrations" table in SAP Mobile Services, you see the values under "user name". From your provided notification settings in SAP Build Work Zone, you currently have selected "E-Mail (default)" as the identifier to deliver notifications. If in the username column another value (e.g. a UID) would be shown, this is the reason for the error message that no matching registration was found. You can also refer to SAP Note 3582623 for more information.

From there, there are multiple ways to solve this:

• With SAP Task Center and the end-to-end configuration of the Global User Id, notifications will also make use of the Global User Id.
• Without Task Center, you could either streamline the Subject Name Identifier to E-Mail or the S/4HANA User Id. This may include the removal of cached shadow-users on your SAP BTP Cockpit.
• Another way would be to override the matching attribute in SAP Mobile Services.

We would recommend you reaching out to sapmobilestart@sap.com, where me and my colleagues can take a look at your case specifically and recommend the best next steps.

[Vijjusk]

I am also getting same issue. Followed the steps based on the link provided. Looks like some key step is missing from in the document.