Changing the deadline date/time in a test system for an exist ing workitem

Allard, Carol CAllard at MassMutual.com
Tue Nov 5 08:37:18 EST 2002


I go into the workflow log and select the work item that has the deadline
monitoring.  Brings you to the Display Work Item screen.  There you select
Edit/Change.  This brings you to Change Work Item Screen where (if you have
the appropriate authorizations) you can change the Deadline Data.  Press
Save after and you should be all set.
 
I did have an issue where if I was just changing the time (and not the date)
it wasn't working.  Not sure if this has been fixed.  I got around it by
changing the date, saving it, then changing it back thanks to a suggestion
from someone in this mailing list! You shouldn't have this issue, though,
since you're probably going to change the date from 21 days to 1 day in
addition to possibly the time.
 
-----Original Message-----
From: Branco Marcina [mailto:Branco_Marcina at national.com.au]
Sent: Tuesday, November 05, 2002 1:27 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Changing the deadline date/time in a test system for an
existing workitem
 
 
Dear workflow gurus,
 
I need your advice on some deadline monitoring. We are running on a 4.6C
system.
 
We have workflows that have modelled deadlines. The deadlines are invoked
21 days after workitem creation. When the deadline is activated, we have a
background step which adds an agent to the workitem by calling function
module SWW_WI_AGENTS_CHANGE.
 
In our development system I have tested this (for the 21 days !) and it
works fine. I have also in the meantime changed the workflow to invoke the
deadline processing after 10 minutes and this worked also.
 
My question is how we can test the deadline monitoring in the TEST system
without changing the workflow. We will be transporting the workflow to the
TEST system with the deadline delay of 21 days.
 
I tried in our development system to change the deadline date/time in
transactions such as SWI1, SWIA and even in the inbox SBWP transaction.
However, the deadline came and went and the escalation step did not get
invoked.
 
What I found was that when creating a workitem which has a deadline
associated with it, an entry in table SWWWIDH is created. eg:
WI_ID WI_DATTYPE WI_DATE    WI_TIME  WI_ACTION                WI_ESC
===== ========== =======    =======  =========                ======
4790  DE         05.12.2002 17:20:59 SWW_WI_DEADLINE_CALLBACK
 
If left alone, and the permanent deadline monitoring job ran after the
deadline time, the entry is deleted from the table and the modelled
deadline step runs OK.
 
When I went into transactions such as SWI1, SWIA or SBWP to change the
deadline date/time, the workitem would be represented as follows in table
SWWWIDH.
WI_ID WI_DATTYPE WI_DATE    WI_TIME  WI_ACTION                WI_ESC
===== ========== =======    =======  =========                ======
4790  DE         06.11.2002 08:20:59 SWW_WI_DI_CREATE
 
When the deadline job next ran, I was initially having problems (shown as
error WL 840 in transaction SM58). I applied OSS note 547738, and now I
just get a log of the message in SWWLOGHIST. The entry disappears from
SWWIDH but no deadline step in my workflow has run.
 
I tried manually changing the date/time in table SWWWIDH and leaving the
action as SWW_WI_DEADLINE_CALLBACK. When the deadline job ran, the entry
was deleted from SWWWIDH and success messages appeared in SWWLOGHIST, but
alas the deadline step was not invoked.
 
Is there anything I should be doing different to get the deadline date/time
changed on a workitem (after the workitem has been created).
I am reluctant to transport a '10 minute' version of my workflow to the
TEST environment, or indeed to have different calculations for the deadline
date/time in the TEST environment.
 
Does anyone have any ideas on what I should do in this situation?
 
 
 
Regards,
Branco Marcina
Extension:  66815    (or 61 3 8641 6815 externally)
Building:   505 Bourke Street, Melbourne, Australia
Floor / Desk:     14/113
Mobile:           0418 958 002
__________________________________________________________________________
The information contained in this email communication may be confidential.
You
should only read, disclose, re-transmit, copy, distribute, act in reliance
on or
commercialise the information if you are authorised to do so. If you are
not the
intended recipient of this email communication, please notify us
immediately by
email to NABpost at national.com.au or reply by email direct to the sender
and then destroy any electronic or paper copy of this message.  Any views
expressed in this email communication are those of the individual sender,
except
where the sender specifically states them to be the views of a member of
the
National Australia Bank Group of companies.  The National Australia Bank
Group
of companies does not represent, warrant or guarantee that the integrity of
this
communication has been maintained nor that the communication is free of
errors,
virus or interference.
 
------------------------------------------------------------------------------
This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies.
 
 
 =============================================================================
 


More information about the SAP-WUG mailing list