Extended Notifications ECC 6.00 guideline

[Dart, Jocelyn]

Hi Florin, 
Filling the gaps from Mike's answer
1. Yes you definitely do.  Use the drop down list on Subscription Handler field in the subscription to see the existing examples.  There's an HR one that gives something similar to what you want. 
4. Logs can be viewed using transaction SLG1.
5. Standard - RSWUWFML2 did NOT do this. In Extended Notifications in your subscription set the Granularity to Multiple Notifications. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Mike Pokraka
Sent: Wed 20/05/2009 1:11 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Extended Notifications ECC 6.00 guideline



Hi Florin,

Apart from the first item, the rest is pretty standard stuff. I'll pretend
you numbered your items:
1. To sort out the first item you probably need to copy/enhance one of the
category classes and plug it in to filter out recipients who don't want it.
2. You define selection filters which are basically lists of tasks. Nothing
to it.
3. You can configure the priority of email addresses in general settings
4. Not sure, no time to check. Errors show up in the log but no
notifications I'm aware of.
5. Standard... I think even RSWUWFML2 did this....?

They are very extension-friendly, so it's quite easy to modify/enhance the
standard behaviour. The difficult bit (and it can take days) is figuring out
what/where/how to implement your change.

Cheers,
Mike

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Florin Wach
Sent: 19 May 2009 11:28
To: sap-wug at mit.edu
Subject: Extended Notifications ECC 6.00 guideline

Hello dear wuggies,

I'm looking for a guideline, how to setup the Workflow Notifications
SWN_SELSEN... for ECC 6.00, which is more like a summary (step/by/step) than
the documentation at the SAP Library, which I'm currently studying.

I have the following challenges at hand:
- Users like to switch off (with two levels) the notifications using their
own user-parameter-ID's
- Per process (one or more work items) various notification types are to be
used. This is: One process has notifications, where another doesn't
- eMail adresses are taken from the user master record (I think, this is
already standard)
- Failed notifications must be traceable. At least there shall be an error
log available or somewhere else an admin notification
- The notification is work-item-based, but several work items should be
combined (with all their different long texts) into one notification.  Uh..
gagah.

Okay, and I need this in proper word format with screenshots and
step-by-step...     just kidding, ... we're not at the SDN, or?


Any ideas to the different challenges are warmly welcome,
   Florin
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


__________ Information from ESET Smart Security, version of virus signature
database 4087 (20090519) __________

The message was checked by ESET Smart Security.

http://www.eset.com <http://www.eset.com/> 


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug