Technical Articles
S/4 Purchase Order Flexible Workflow: Push Notifications
Hello,
Following the Purchase Order Flexible Workflow series, today we’re gonna talk about Notifications. For every Activity that you enter (through SWDD_SCENARIO) you’ll see the Notification Tab:
This tab tells you if that specific Task has Push Notifications Active or not (and mapping).
If you select, you’ll go to a “new” Transaction: SWF_PUSH_NOTIF_CUST (with the specific WF already filtered). If you desire to go through all WFs at the same time, just open this transaction in a new screen:
It’s pretty simple, you need your WF/Task number, activate and map Actions and Texts to make the Push notification happen. Let’s take an example that i’ve created:
When the Workflow is created, in my Launchpad:
If you wan’t to know deeper details on how to configure from scratch and more technical details, you can download the PDF here and to to the official documentation here.
Bonus: There are some new SWF* Transactions available in S/4, you can explore if you wan’t to know more:
Like SWF_FOOTPRINT for example:
Enjoy!
Regards.
Hello Josh,
Nice document, please let me know what is the use of push notfication T.code ?
Hello venu gopal , how are you? With this Tcode configured, every time a new Workflow is created a Push Notification is sent to the Approvers Launchpad automatically.
Regards.
Hello Josh,
Thanks for your update, let me ask you one more question as I am new to this topic, suppose if you are not cobfigured above T.code then what could be the result ? is it manuval process to trigger ?
Hello venu gopal,
If you have a Flexible Workflow without Push configured the flow will work normally, without any issues (just like Classical Workflows). The process to trigger is not manual, just the configuration above will result in notifications on the approvers Launchpad, ok?
Regards.
Thanks a lot dear..
Hi,
I'm missing the Notification Tab for workflows. Will this mean the push notification functionality doesn't work for these or am I missing some customizing?
Kind regards,
Hello Rob Veerman , how are you?
This Notifications Tab exists only for Flexible Workflows, not Regular (or Classical) Workflows. To achieve notifications on Classical Workflows, you shall use an EXIT (and ABAP code) on your Decision Task, ok?
Thanks.
Thanks Jose.
Hi Jose,
In case of the release of a PR/PO using flexible workflow. Is it possible to set up push notifications to inform the initiator that the approver has approved/rejected the document?
Kind regards.
Hello Wim Desmedt, how are you?
If you're looking for Email notifications at the end, please check:
https://help.sap.com/viewer/0e602d466b99490187fcbb30d1dc897c/2002.500/en-US/ceeb8059ce984943bfe9bbc7e464cd0b.html
If you're looking for the same type of Push Notifications in a more "Custom" way, you can check out the Class/Method: CL_MM_PUR_PO_FLEX_WFL=>IF_SWF_FLEX_IFS_RUN_APPL~RESULT_CALLBACK (some ABAP Code needed).
I'll try to create a Blog about it as well.
Thanks.
Hello Wim Desmedt,
Please take a look here: https://blogs.sap.com/2020/06/08/s-4-flexible-workflow-abap-code-for-push-notifications
Regards.
Hello,
I am having problems with Flexible Workflow for PR/PO. No notifications are being pushed at all.
I assume that when a PR gets rejected a notification should be pushed for the requester right? I can see that I have texts updated for PR and PO tasks. Those texts refer to newly created PR/PO for approvers. still those notifications are not being shown.
My main question is, where do I set the notification for rejected PRs? So the requester would receive a message telling him/her that the PR needs to be changed?
thanks
Hello Gonzalo Simon, how are you?
Regarding the notifications, please go through the steps here to make sure as is setup.
Regarding the notification when the PR gets rejected, should it have the reject text...? Is it a possibility to use some ABAP code as well or you need to be 100% configuration?
Regards.
Hello Jose ,
Very nice blog.. we done. I have a issue though , Can we send hyperlink in Notification ? When i send it through workflow , it consider it as text. I had also tried it woth html tag.
Thanks
Hello Jose,
I have activated standard flexible workflow for PR header level approval : WS02000458. I need notification sent to requester/Creator whenever PR is Rejected. I created template YY1_02000458_COMPLETE_NEGATIVE. But email notification to the requester is not generated when PR header level is Rejected in FIORI . How to generate Rejected notification for Flexible workflow : WS02000458 , TASK TS02000702 ( Overall Release of purchase requisition) ?
Does Push notification configurations is something i'm missing ?
Please note I also created YY1_02000458_CRT_19 which is working as expected.
Thanks,
Subha
Hello Jose,
We have implemented push notifications in our system for PO & PR Flexible Workflow. It is working perfectly fine.
Our issue is testing team has created many POs & PRs having 18 agents and now those push notifications are sent to all agents.
Our basis team tried to clear and delete entries from tables /IWNGW/NOTIF and /IWNGW/NRECIP to reduce the load on the system but even after clearing all entries after few hours the tables are populated again with notifications details even though no new WF task is triggered.
It is triggering push notifications again for old WF task which are already sitting in MyInbox App for the action.
Is there a way to stop these notifications to be triggered again and reduce the load of the system. We can't approve all POs & PRs as of now.
Why it is triggering push notifications again and creating millions of entries in table /IWNGW/NOTIF and /IWNGW/NRECIP?
Thanks,
Jaymin
Hello Jaymin Thakkar, how are you?
Did you check any OSS notes for that?
Regards.
Hello Jose,
I am doing, Thanks! I hope you are also doing good
Yes I tried to search OSS notes but was not able to find any.
The table /IWNGW/NRECIP has entries for all those 18 agents again after clearing the metadata and cache. Not sure what process is generating entries in the table again.
Table /IWNGW/NOTIF is empty for all 18 users after clearing metadata and cache.
I cleared metadata and cache using /IWNGW/H_CLEAR_NOTIF transaction for all those 18 users.