"Start Workflow" of Generic Object Service

[Dart, Jocelyn]

Hi Kim/Phil,
The message makes it sound more complicated than it really is...
 
You just need to:
 
1. Set up your workflow with a mandatory input container element
for the appropriate object type.  Don't make anything else
mandatory as it's too confusing for SWUI.
 
2. Make sure your users have access to SWUI - of course.
 
3. Make sure you users are possible agents of the workflow itself
- i.e. they are allowed to start it ad hoc. (This doesn't mean
they are allowed to perform any of the tasks within the workflow of
course - the agent assignment for the workflow and for tasks called from
the workflow are completely separate.)
 
4. Create a start workflow transaction ((or start form - depending on your release).
This lets you provide extra help or let users enter input data and attachments before
the workflow starts.
 
Remember generic object services is always specific to a certain
object type.  If you can't figure out what object type is being used
for a particular transaction, suggest you put in a query via OSS.
 
The start workflow requirements are documented in the SAP library in the
workflow "reference" section under "starting tasks and workflows".
 
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
 
-----Original Message-----
From: Kisloff, Philip B [mailto:Philip.Kisloff at astrazeneca.com]
Sent: Friday, 18 October 2002 6:10 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: "Start Workflow" of Generic Object Service
 
 
Hi Kim,
 
There seems to be a whole lot needs to be done, and the only documentation I
ever found was an error message long text (WI116). Even then it does not
mention everything:
 
The start workflow transaction can be called from the main menu (SWUI) or
from within a transaction (GOS). If from within a transaction, only one
mandatory input container element must be present for the workflow (not
task), with the same object type as describes the transaction. No mandatory
input elements are allowed if stated from SWUI.
 
Also, the user must be a possible agent, by making the workflow general task
or assigning some org management object. Finally, the authorisation to start
the SWUI transaction must be present in the profile as well as to start the
workflow (Authorization object S_WF_WI, Activity 16 (start task) Type F) You
may also want to restrict this to certain workflows by classification (in
the IMG).
 
Regards
 
Phil
 
 
 
-----Original Message-----
From: Kim, Go Joong [mailto:go.joong.kim at sap.com]
Sent: 15 July 2002 09:25
To: SAP-WUG at MITVMA.MIT.EDU
Subject: "Start Workflow" of Generic Object Service
 
 
Dear Experts,
 
There is 'Start Workflow' function in the Generic Object Service.
And the related workflows are determined automically by the system according
to the online document.
 
But I don't know how these are determined.
 
Who knows how related workflows are determined?
What rules or criterion is used to determine?
 
Any opinion will be appreciated.
 
Regards,
Steve Kim