Problems with object delegation and workflow

[Vincze Árpád]

Hello,
  =20
  After the transport I generally activate the modified BOR type ( =
BUS2032
) on the target system.
  ( I know that is not normal, but useful)
 
  Regards
   =20
   =C1rp=E1d
 
-----Original Message-----
From: Flaig Matthias [mailto:M.Flaig at ProMinent.de]
Sent: Thursday, June 28, 2001 2:59 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problems with object delegation and workflow
 
 
Hi!
 
I've created a subtype ZBUS2032 of object type BUS2032 with an =
additional
attribute ZRequestedDeliveryDate.
The ZBUS2032 ist set up as delegation type for BUS2032 in SWO6.
 
Then I've used the new attribute in Workflows where I've a reference to
BUS2032 in the container. All works fine. I can use the new attribute =
in the
date-filed of an latest end expression. The F4 lookup shows the =
additional
attribute correct.
 
Until now all looks good.
 
Then I transported the new object, the delegation and the workflow from
development to the testing system. The Workflow and the object are =
imported,
SWO6 shows the delegation but if I open the workflow template I get the
error message:
"Attribute 'ZREQUESTEDDELIVDATE' not defined for object type 'BUS2032'
(Message no. OL 807)"
If I run a syntax check in the workflow builder there are also some =
error
messages indicating the the system isn't aware of the delegation. But =
SWO6
shows the delegation entry correct.
 
Has anyone an idea?
 
Is it possible that the delegations are bufferd and not activated at =
once
after the import? (Similar to the workflow definitions and SWU_OBUF).
 
Thanks,
Matthias
------------------------------------------------------------------------=
----
Matthias Flaig
 
ProMinent Dosiertechnik GmbH
Im Schuhmachergewann 5-11
D-69123 Heidelberg
Germany
 
http://www.prominent.de
Email: m.flaig at ProMinent.de
Tel.: +49 (6221) 842-542