SRM 5.0 Alerting Workflow

[Baunach, Natasha R]

Thanks you very much for the pointers.

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Monday, April 10, 2006 10:57 PM
To: SAP Workflow Users' Group
Subject: RE: SRM 5.0 Alerting Workflow

 

Yes you don't need to use your old custom approach.  An SRM 5.0 is a
NW04s (basis 700) so you have the extended email notifications
(transaction SWNCONFIG) and that will handle that requirement if you
configure it appropriately. 

 

Using alerts to start workflow is ok - there's a standard one in SRM for
contracts.  I think in SRM they just called SAP_WAPI_CREATE_EVENT or
equivalent from BW.  But there's also some config where you can  use the
alert category to trigger workflow.  Ginger Gatling did a blog on it on
SDN which might give you some clues - it was about alerting and the UWL
but it will point you to the config for the alerting side of things. 

 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Baunach, Natasha R
Sent: Tuesday, 11 April 2006 9:58 AM
To: SAP Workflow Users' Group
Subject: SRM 5.0 Alerting Workflow

Hello,

 

We are on SRM 5.0, SAP_Basis 700, support pack 6.  Our requirement is:

1.	Invoice submitted for approval 
2.	Email notification is sent out to the approver (regular email
notification report for offline approval works fine here
RBBP_NOTIFICATION_OFFAPP) 
3.	If approver has not acted after three days, send another email
notification 
4.	If approver has not acted after six days, send another email
notification 
5.	If approver has not acted after ten day, auto-reject the invoice


 

I was thinking about using Alerting workflow (WS14500051) but cannot
find any clear documentation of how it needs to be set up.  I have found
OSS note 865249 that tells you how to use a custom alert notification
workflow.

 

Has anyone implemented these alerts?  Could you please provide our
experience?  Also, if you have a suggestion of how to accomplish these
requirements, please let me know.

 

(In our old 3.0 system, we have a custom batch job that monitors
SWWWIHEAD table and send notifications for items that are older than 3
days but are still in status ready.  It works OK but the performance is
very poor and I'd like to avoid such a solution).

 

Thanks much.

Natasha

 

 

Natasha Baunach

Sr. Application Developer, SRM Team

971-215-2276

866-272-3809

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060411/a3ad6d4c/attachment.htm