AW: Deleting workitems in a productive system

[Schmidinger, Heinz (Unaxis IT BZ)]

Hello Michael,
 
maybe I can give you some of my expirence in this point:
 
I have done both ways: If a user was very late with WI's (IDOC-ERRORS) =
I
used the Deletion Job to reduce the ballast sppecially if they were not =
in
Status Completed or DELETE which is a must for die Archiving Job.
 
For all my WF's I do a definition of late rArchviing in the project =
from
begin.
WF's which must we have historical I archive with connection to Archive =
Link
and ArchiveInfoSystem (existing in 46B too, also the documentation says =
no).
 
Workflows we don't need anymore I archvie too, but without connection =
to
ArchvieLink. Ss they were removed correctly from the Database and the
ArchvieFile is written to the Operating System, wher they are deleted =
by the
BasisGroup.
 
 
The Disadvantage of my Solution is, that I have to change the =
AL-Customizing
always between AL-Connection or not.
 
I'm thinking about to do this by a litte programm running before and =
after
the archiving-runs.
 
Regards
 
Heinz
-----Urspr=FCngliche Nachricht-----
Von: Michael Pokraka [mailto:workflow at quirky.me.uk]
Gesendet am: Donnerstag, 13. Februar 2003 15:23
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Deleting workitems in a productive system
 
Greetings all,
I have a requirement that's a bit conflicting:
Client is generating a lot of workflows which have no historical
significance (They are mostly for processing documents after creation).
 
Now, we can use archiving, but something irks me about archiving a =
large
amount of data (we're talking in Gigabytes/month), the majority of =
which
is useless.
Some alternatives come to mind: deleting, 'split' archiving, or just
biting the bullet and using standard archiving. Some random thoughts on
this:
 
 - Deletion via RSWWHIDE and RSWWWIDE is not recommended by SAP or
   'The Book' (and also in a recent post by Jocelyn :)
   Here I would create and thoroughly test a set of variants to be run
   regularly. However I'm curious as to what (if anything) might not be
   covered by these jobs.
 - Archiving these seperately. I'm not exactly an archiving expert and
   have no idea if it's feasible to split/create variants of the
   WORKITEM archiving object - one to archive the 'real' workflows and
   one to archive the 'transient' ones into an electronic dustbin. I
   don't see any selections based on any specific tasks.
   If possible, this would be the favoured approach as I believe
   archiving has a lesser impact on system load.
 - Biting the bullet and just using normal archives. I have no idea
   apart from storage requirements if there is any impact on things =
like
   retrieval or anything else. Out of principle it's a bit irritating
   though :-)
 
Any input would be greatly appreciated.
Cheers
Mike