Deadline monotoring buggy ???
Dart, Jocelyn
jocelyn.dart at sap.com
Sun Dec 9 18:22:38 EST 2001
Hi Marc,=20
Please report this to OSS but before you do, double check the
actual deadline times assigned to your work items in the work item =
display
and also the scheduling of your SWWDHEX job to monitor the deadlines. =
I'd also watch out for timezone problems - e.g. are the expressions
used in your deadline calculated based on system time or on local
timezones?
Regards,=20
Jocelyn Dart=20
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow) =
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>=20
Tel: +61 412 390 267
Fax: +61 2 9935 4880
=20
-----Original Message-----
From: Giesinger Marc [mailto:Marc.Giesinger at egger.com]
Sent: Friday, 7 December 2001 6:46 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: Deadline monotoring buggy ???
hello diane
this was the first thing i did :-)=20
... nothing
-----Urspr=FCngliche Nachricht-----
Von: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Gesendet: Donnerstag, 06. Dezember 2001 16:14
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Deadline monotoring buggy ???
Check the OSS Notes. I saw some notes on WF deadline monitoring on 4.6 =
the
other day. You might find some help there!=20
Diane H. Nobles=20
SDE PM Team=20
(757)380-7250=20
------------------------------------------=20
Do not render evil to anyone, but pursue=20
good both for yourself and for all.=20
1Thess 5:15=20
-----Original Message-----
From: Giesinger Marc [mailto:Marc.Giesinger at egger.com]
Sent: Thursday, December 06, 2001 7:47 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Deadline monotoring buggy ???
hi folks=20
i have a little question using deadline monitoring on 46C/patch23
we created a helpdesk (customer service) scenarion via workflow within =
two
eskalations using a "selfmade" role resolution function module.
for the escaltion we use the deadline LATEST START and LATEST END.
we calculate for each workitem depending on the users location (getting =
the
factory calendar for germany, england, italy, ...) and the priority of =
the
message the escalation date and use this variable as expression in the =
tabs
for start / end.=20
escalation time is between 3 hours and 5 days.
everything is working fine (we get correct date / time information and =
the
monitoring is shown on the workitem in the log
when the "first level support" (normaly a couple of users) recieve the
workitem.=20
so i thougt if one of the members from the CS group catches the item =
first,
the monitoring should be over (for latest start) because the latest =
start is
pointing e.g. to 06.12.2001 but the user processed the item 05.12.2001
but im worng ... :-( the monitoring is going on and will send on =
06.12.2001
an (first) escalation message to the chief of the CS group saying =
nobody
processed the item !!!=20
so i think the WF system is buggy in this case, because the status of =
the
items changes from ready to started ???????
so please: anyone experience with this options and can give me a hint =
????
=20
thanks in advance=20
Marc
Mit freundlichen Gr=FC=DFen
Marc Giesinger
IT EDI&Workflow
Fritz Egger GmbH&CO
Spanplattenwerk
Weiberndorf 20
A-6380 St. Johann in Tirol
Tel: +43/50600-10348
Fax: +43/50600-90348
e-mail: mailto:marc.giesinger at egger.com
Internet: http://www.egger.com
More information about the SAP-WUG
mailing list