TS30001128 vs. TS00007869, Early Archiving Standard Tasks

[Phillips, Tim]

Hi Greg,
 
I've implemented projects using both these tasks before.
 
If you're using 4.5b upwards, I would strongly recommend switching from
TS7869 to TS30001128.
 
I had real problems getting the the workflow task to terminate properly
using TS7869 on a 4.6b system, something which only rectified itself when I
switched to the newer task.  I'd had no problems using the same task on a
4.0b system beforehand.
 
Obviously, you'll have to make changes to SOA0 to match this; I just created
new document types based on the old ones, rather than changing the SAP data,
then added new entries to OAC3 to match.
 
Regards,
 
Tim
 
-----Original Message-----
From: Greg Soltys [mailto:gregsoltys at hotmail.com]
Sent: 15 October 2002 20:48
To: SAP-WUG at MITVMA.MIT.EDU
Subject: TS30001128 vs. TS00007869, Early Archiving Standard Tasks
 
 
BlankHello everyone.  If anyone if familiar with the above single step tasks
I would appreciate any input and thoughts:
 
Basically, I need to understand what the difference between the two tasks
are with regards to functionality.  We are on a 4.5B system, and both tasks
are available for early archiving scenarios.
 
TS30001128: ImageAssingE "Enter document for document type"
- executes the method IMAGE.IMAGEASSIGNEARLY
- utilizes the standard role 126: "SAP ArchiveLink early arch. responsible",
which calls the f.m. ARCHIV_EARLYINPUT_RESPONSIBLE
 
TS00007869: ImageAssign "Confirm document type / enter document"
- executes the method IMAGE.IMAGEASSIGN
- utlizes the standard role 30000019: "SAP ArchiveLink early arch.
responsible", which also calls the f.m. ARCHIV_EARLYINPUT_RESPONSIBLE, just
with slightly different format of document type/org object container
definition
 
 
Thoughts:
TS30001128 appears to be a newer version, but does it replace in it's
entirety 7869?
Delivered SAP in 4.5B is still configured to initiate 7869 in the "Workflow
Document Types" in tx'n SOA0 (in our case, for document type FIIINVOICE.
The parameters and code between the methods .IMAGEASSIGNEARLY and
.IMAGEASSIGN differ greatly (obviously).
 
So, anyone with any thoughts/guidance?  We are indeed going forward with
early archiving and a Panagon solution, thus will be utilizing tx'n OAWD to
trigger the assignment via an IDM Desktop for R/3 viewer.
 
Thanks in advance to all,
Greg