Handling ad hoc notifications

Tue Jan 18 19:48:28 EST 2005

Margaret, 
You should also look at the ad hoc agent assignment options in your
system in the help.  Choose agent will work but its an old approach.  If
you are on R/3 4.7 or a basis 6.20 or above system then the new options
are worth considering. 
See the SAP Library help
Regards,
Jocelyn

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Hilsbos, Margaret A
Sent: Wednesday,19 January 2005 5:28 AM
To: SAP Workflow Users' Group
Subject: RE: Handling ad hoc notifications

Richard,

Thanks, I'll try that.

Margaret

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of rvmarut at earthlink.net
Sent: Tuesday, January 18, 2005 12:08 PM
To: SAP Workflow Users' Group
Subject: RE: Handling ad hoc notifications

Margaret,

You should be able to add additional agents into the list.

It sounds like you need each person in the list to process a work item.
If this is the case, you could then use business object SYSTEM and
methods DescribeAgents and LoopAtAgents (within the loop you mentioned)
to process through the list.

Richard...

-----Original Message-----
From: "Hilsbos, Margaret A" <Margaret.Hilsbos at dayzim.com>
Sent: Jan 18, 2005 9:42 AM
To: SAP Workflow Users' Group <sap-wug at mit.edu>
Subject: RE: Handling ad hoc notifications

Thanks, Maorriyan and Richard.

That seems to work fine for the initial selection.  Then, if I need to
allow the user to be able to subsequently modify the agent list ("notify
list"), I think I need to use a loop that allows the initiator to
repeatedly execute "Choose Agent" to append names to the list. This loop
is in a path of a fork, which completes when the form reaches the final
processing status (i.e. it is complete); so that then the "choose agent"
path is obsoleted and any work items are logically deleted.  

This is what I was thinking but it seems convoluted.  I haven't built it
yet...that is next. 

It sounds like you are confirming my approach.

Thanks,

Margaret

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Maorriyan
Sent: Tuesday, January 18, 2005 7:48 AM
To: SAP Workflow Users' Group
Subject: RE: Handling ad hoc notifications

Hi Margaret,
You can use Choose agent wizard step for easier way.

 --- Richard Marut <rvmarut at earthlink.net> wrote: 
> Margaret,
> 
> Business object WF_TASK will help you accomplish
> getting a list of possible
> agents to choose from. You will need to specify the
> step that the agents
> will be pulled from for the list that gets
> displayed. That step will also
> need to have possible agents assigned. I just did a
> test on the business
> object where I assigned an organizational unit to
> the task that I specified
> in method AllAentsOfTaskGetAndDispatch.
> 
> You can use the workflow wizard to create a step
> that will use the business
> object and method that I mentioned above.
> 
> Richard...
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Hilsbos, Margaret A
> Sent: Monday, January 17, 2005 8:43 AM
> To: sap-wug at mit.edu
> Subject: Handling ad hoc notifications
> 
> Hello all,
> 
> I was hoping someone could help me with the best way
> to handle this
> requirement.  We have a workflow where the users
> want to be able to specify
> a list of "interested users" that should be notified
> at each subsequent step
> of the process (approval, processing).  Currently,
> they are using a
> LotusNotes-based web site for this process, and they
> can access a pulldown
> to select users to add to the "notify" list.  I
> believe that they can do
> this at any stage of the request until it is closed,
> so that for example, if
> Mary Jones is added to the list after approval but
> before processing, Mary
> will be included in the recipients of a notification
> upon completion of the
> processing step.  This is a feature the users don't
> want to lose when moving
> to an SAP-based workflow.
> 
> 
> The workflow uses a start form and form steps to
> document the request,
> approval or rejection, and processing results.  We
> need the ability for the
> requester to add user names to the notify list when
> initiating the form, and
> also (hopefully) to access the workflow ad hoc
> before it is complete to add
> to the notify list.  The notification is only to
> tell the recipient that the
> step was completed.
> 
> We are on a WAS 6.20 but may also need to implement
> this in a 4.6C system.
> 
> I have thought of a few possible ways that might
> handle this but they all
> seem convoluted.  It seems like this would not be an
> unusual requirement so
> I'm wondering a) am I missing something obvious or
> b) how have other folks
> solved this?
> 
> Thanks for any help you can give!
> 
> Margaret Hilsbos
> (215) 299-5630
> 
> Day & Zimmermann
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>  

=====
Maorriyan

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

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

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

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