Recalc of agents at deadline - use of local events

[Mark Pyc]

G'day Alon,

I didn't think FLOWITEM was going to cause me a problem as _WORKITEM has the
instance of the overall workflow. Raising the event works fine however it
seems that timing is an issue. It fails to create an entry in SWEINST and
therefore the event goes without reaction. I guess at the point when it's
adding the SWEINST entry it must not yet have assigned an instance value to
FLOWITEM, which I can understand. A pity though, it could have been a thing
of beauty.

Still, does anyone know if you can use local events?

I've since found another post from Jocelyn in 2003 that suggets that adding
an event to the primary object of the flow is the way forward. This does
work, but just doesn't seem as clean as it could be.

Have fun,
Mark


On 6/8/06, Alon Raskin <araskin at 3i-consulting.com> wrote:
>
>   Mark,
>
>
>
> I like your idea about adding the event to the FLOWITEM type. The only
> issue I can see with that is that you need the work item ID for the dialog
> task (or workflow) which *may* be difficult to obtain. Might be easier
> just to add it to the Business Object type. Though there could be an issue
> if you have multiple workflow instances for that business object. How do you
> know which instance that event was intended for?
>
>
>
> As far as local events, etc. I am sorry but I don't have access to ECC 5.0
>
>
>
> J
>
>
>
> *Alon Raskin*
>
> *e: **araskin at 3i-consulting.com* <araskin at 3i-consulting.com>
>
> *p: +1 207 409 4983*
>
> *f:  +61 3 8610 1239 *
>
>
>
> *The easiest way to integrate SAP with any mobile device*
>
> *http://www.themobileworkplace.com*
>
>
>  ------------------------------
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Mark Pyc
> *Sent:* 08 June 2006 06:30
> *To:* WUG
> *Subject:* Recalc of agents at deadline - use of local events
>
>
>
> G'day all,
>
>
>
> Below is an extract from one of Jocelyn's posts last year recommending the
> use of header events with re-evaluation of agents as a way of making metric
> info more accurate. A wonderful idea.
>
>
>
> Can anyone comment if it's possible to use local events for this purpose.
> In ECC 5.0 it seems not, but this seems crazy. I think this would be a
> perfect use for local events.
>
>
>
> Is it necessary to define an 'updateagents' type event on each object
> where you want to do this? Or maybe an alternative is to create the event on
> the FLOWITEM object.
>
>
>
> Happy for any and all opinions.
>
>
>
> Have fun,
>
> Mark
>
>
>
> But if you are on a Basis 6.20 (e.g. R/3 4.7 or above) then there's an
> even easier/better way:
>
>
>
> * In the basic data (look for the "hat" icon in the workflow builder) you
> can set up an event for the whole workflow, e.g. "updateagents" - mark it
> as having the effect "re-evaluate rules on active work items"
>
>
>
> * Before your step, save the original agent into a multiline container
> element of type wfsyst-agent (or similar)
>
>
>
> * In your step, assign the agents of your step as an expression pointing
> to your multiline container element
>
>
>
> * When the deadline occurs, raise a deadline event, e.g. "Latest end
> reached" and in the deadline path, add your new agent to the multiline
> container element, then fire off your "update agents" event.
>
>
>
> Very, very effective, quite easy, and has exactly the affect you are after
> - plus you keep a more accurate record of the time taken to action the work
> item because you still have the original work item and therefore the
> original work item creation date/time.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060608/8a0fb650/attachment.htm