AW: No agent assignment after Transports
Schmidinger, Heinz (Unaxis IT BZ)
heinz.schmidinger at unaxis.com
Mon Oct 20 02:43:09 EDT 2003
Hi Swami,
it is a nice idea from SAP, that these assignments are not transported. =
But there s report RHMOVE30 (and RHMOVE60). With theses reports you can
create a transport of WF-task-Assignments.
Look for the corresponding notes in OSS (I havn't the numbers in my =
mind)
for details.
maybe it helps.
regards=20
Heinz
-----Urspr=FCngliche Nachricht-----
Von: Swam_in [mailto:swam_in at hotmail.com]
Gesendet am: Sonntag, 19. Oktober 2003 19:38
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: No agent assignment after Transports
Hello All,
I had set some of the standard tasks to 'General task' in the new =
workflow
that I created and transported the same to other clients.
But all those tasks has no agent assignment in the target client after =
the
transport.
Any ideas / suggestions regarding how to fix this error in development
client ? ( Though the target client allows changing the attribute to
'General task'
without a request #, I would prefer doing it in the development client =
)
Thanks
Swami Bala
More information about the SAP-WUG
mailing list