transporting GENERAL TASK agent assignment

[Gregory Kowalik]

check if you have any entries in table T77TR.
This table is used to block certain HR relationships from being moved.
We have blocked this way user assignments to all positions (since you usually
have different user assignments in different R/3 systems)
This caused tasks attributes not to be transported as well.
 
Let me know if that helped.
 
Greg
 
 
 
 
 
 
Brian Bennings-BJ <bennings.bj at pg.com> on 07/31/2000 04:18:47 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  transporting GENERAL TASK agent assignment
 
 
 
Everytime I attempt to transport a newly created standard workflow task (TS)
with a GENERAL TASK agent assignment from our development box to another SAP
box, the agent assignment changes to GENERAL FORWARDING NOT ALLOWED.  We have
even created separate transports to correct this agent assignment, but the
results are the same.  Each time, we have to log into the target system and
manually change these tasks to GENERAL TASKS.
 
This is only a problem on tasks that were actually created in the development
system itself (source system of the transport).  The agent assignment transports
correctly for those developed by consultants and transported into our
development system.
 
Is there some trick that we are missing?
 
Thanks,
Brian