Notifications and Subscriptions in BW4/HANA

Notifications and Subscriptions functionality is available in BW4/HANA based BW systems. In case of the Notifications, the user has a chance to receive notification either via email or to mobile devices about different events that happened in the BW system. The events are following:

Process chain run aborted

Process chain run completed

Process chain run is overdue

Process chain run is seriously delayed

Process chain run takes longer

Process chain run takes much too long

Request ended with errors

Subscriptions on other hand defines specific conditions of BW∕4HANA objects that user receives the notifications for.

Settings related to notifications and subscriptions are available SAP BW∕4HANA Cockpit – (BW Fiori Launchpad). From here the notifications/subscriptions can be enabled/disabled.

From the BW backend perspective the functions are needed first to be customized.  In a t-code SPRO there is an item called Notification Channel -> Notification Channel Provider Enablement. Here all customizing needs to be done from the Configuration and Administration perspective. To switch the function on - the customizing under Administration -> Notification Provider Settings -> Manage Notification Providers (t-code /IWNGW/VB_REG_P, maintenance view /IWNGW/VB_REG_P and table /IWNGW/B_REG_P) needs to be activated.

There are a few tables that holds data about the settings:

BW4FLPNOTIF                    BW/4 FLP Notifications, each notification has a unique ID (NOTIF_ID), TYPE_KEY identifies type of the notification (BW ones e.g.: BW4_RSPC_VERY_LONG, BW4_RSPC_LONG, BW4_RSPC_BERY_LATE, …)

BW4FLPNOTIFREC                 BW/4 FLP Notification Receivers, a list of the user per unique notification ID

BW4FLPNOTIFSUB                 BW/4 Notification Subscriptions, each subscription has unique ID (GUID), user (USER_ID) specific the user to whom the subscription belongs to, OBJECT columns defines object which the subscription is related to (e.g.: ADSO, PC, PREC, etc.), validity columns from – to, who created, when,…

BW4FLPNOTIFSUBCO               BW/4 Notification Subscriptions Conditions, condition has unique ID (SUBSCR_GUID), FIELDNAME, and SEL_LOW and SEL_HIGH define object e.g. PC tech name

Some of these tables can grow fast thus housekeeping needs to be performed on them. There are standard programs like RS_BW4_FLP_NOTIF_DELETE and RS_BW4_FLP_NOTIF_OFF to support that.

 

More information:

Online documentation

2922364 - FAQ: BW/4HANA 2.0 Cockpit Notifications

Process Chain – Processed with Errors

While checking process chain there can following message displayed:

Processes with Error        Message No. RSPC022

Diagnosis

Error occurred when checking the process chain.

System Response

When errors occur, the system does not activate the chain.

Procedure

Call the relevant messages for the processes that are marked in yellow and red using the context menu.

 

The problem with that message is that it doesn’t say what process has the error. The error is just shown as generic and from the message it is not possible to say what is wrong.

To get to know what process the error is related to a debugging is needed. Check of PC’s processes are executed by method CHECK of ABAP class CL_RSPC_CHAIN. There is an internal table called E_T_CONFLICTS holding information about the erroneous process:

In my case the error was related to aDSO activation process. The aDSO object technical name is shown in field MSGV1.