Re-evaluate Rules via header event doesn't replace the WI

[Mike Pokraka]

Hi Mark,

I've used header events, but not had a chance to use the rules one in
production, but it sounded like you answered your own question.

The reserved question is debatable but I would agree with you that
reserved items should be included in the reevaluation. In most scenarios I
could think of a reevaluation would supercede a reservation (escalation by
deadline, changing data making someone else responsible... anything
else?).

I'd see what OSS have to say on the matter.

Cheers,
Mike


On Tue, September 26, 2006 11:35, Mark Pyc wrote:
> No takers on this one? Does anybody productively use the header events
> with
> the 'Re-evaluate Rules of Active Work Items' option?
>
> Thanks,
> Mark
>
>
> On 9/19/06, Mark Pyc <mark.pyc at gmail.com> wrote:
>>
>> G'day Wuggers,
>>
>> ECC 5.0
>>
>> We are using the Reevaluate Rules via version-dependant header events to
>> handle our deadline escallations however this process doesn't seem to
>> Replace the Workitem. This means that if a Workitem is reserved by an
>> agent,
>> they go off sick, the deadline kicks in, the table used in the agent
>> expression is appended, the event raised, the agents are recalculated
>> but
>> the Workitem remains reserved by the original agent. This is very
>> disappointing!
>>
>> Is this how it works (or rather doesn't) or do I have an OSS issue on my
>> hands (I can't find a suitable note).
>>
>> If this is how it works then I'm looking at extending the Worktiem
>> object
>> and including a method to call SAP_WAPI_PUT_BACK_WORKITEM which would be
>> included in the Deadline path before the event raise for recalc. I'd be
>> interested to know what others have done.
>>
>> Any insights greatly appreciated.
>>
>> Have fun,
>> Mark
>>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>