New to workflow

Thu Sep 13 00:27:23 EDT 2007

Jocelyn and Phil,

Thank you very much for the tips and I will not let the words "Mark For
Deletion" cross my lips ( or keyboard) again.

Ron Adkins

SAP Systems Analyst (And Newby WF fall guy)

ECC 5, Oracle, HP-UX

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dart, Jocelyn
Sent: Tuesday, September 11, 2007 5:30 PM
To: SAP Workflow Users' Group
Subject: RE: New to workflow

Those PM/QM/General notifications are seriously cool... especially if you
want to play around with Adobe Interactive forms. 

Ron - there are some standard workflows for business object type BUS7051 and
BUS7028 - if you call up the where-used list from transaction SWO1 and have
a look at those workflows you will see some background tasks that show you
how to update the notification's system status.  The workflows themselves
are slightly scary because they are so generic - but just check out the
tasks within them, that's what you need.  It's a different but similar
method for updating the  user status.

And yes as Sue says - please never suggest marking a work item for deletion
again (that's "wash your mouth out" territory).  The correct approach is to
have your workflow listen for e.g. a "manual approval" event and cancel the
work item in response.  You could still update the status if you need to
after receiving the workflow event. 

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
Kisloff, Philip B
Sent: Tuesday, 11 September 2007 11:26 PM
To: SAP Workflow Users' Group
Subject: RE: New to workflow

Hi Ron,

I recognize this as user status management for either quality notifications
or one of the other modules using notifications (which borrow a lot from
plant maintenance -PM). This are is not necessarily anything to do with SAP
Business Workflow, unless you plan to control your notifications with status
change events. The challenge here is not so much the workflow side, which
can be reduced to delivery of the messages or additional background actions
based on status events, but on the relevant application module knowledge and
your specific scenario.

I'll have a go at answering, nevertheless:

1. Marking for deletion allows the notification to be archived, as if it was
completed ? Also, surely you would want to log and restrict access to
approve/reject, while mark for deletion should only be accessible to
administrators.

2. Try SAP_WAPI_WRITE_CONTAINER

By the way, it's a area of interest of mine to see how notifications can be
used more widely to solve BPM-type problems, so good luck !

Phil

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of
Keohan, Susan
Sent: 11 September 2007 13:40
To: SAP Workflow Users' Group
Subject: RE: New to workflow

Hi Ron,

I don't know what release or application you are using - we don't have
transaction PMM8 on our 4.6c system, so I am not sure what it does.  What I
do know is that 'mark workitem for deletion' will likely cause a lot of
WFers out there to run for the hills.  

Please include release and/or application in order to generate a more
fruitful discussion.

Cheers,
Sue

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Ron Adkins
Sent: Monday, September 10, 2007 8:45 PM
To: sap-wug at mit.edu
Subject: New to workflow

Hello everyone,

I am new to workflow and have a couple of questions.  Thanks in advance for
your time.

1.	Mark for Deletion (PMM8)  vs Refuse Approval of  a Notification.
What are the downfall to letting our workflow processors Mark a workitem for
deletion versus a Refusal Approval? 

2.	If we have removed a step of approval from a new workflow, how can I
manually change the status to NOPR APOK in the container? 

Thanks,

Ron Adkins

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