Virtual attribute as ad-hoc object.

[Lücking Claus]

Hi Alon.
 
Thanks for your reply.
 
I use a standard attribute, and it seems to me, that errorhandling is
standard implemented. I have found a new OSS note (667828) regarding =
this
problem in a way. I will implement this, and let you know if it works.
 
Claus.
 
-----Original Message-----
From: Alon Raskin [mailto:araskin at 3i-consulting.com]=20
Sent: 5. november 2003 10:41
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Virtual attribute as ad-hoc object.
 
 
Are you doing an exit_object_not_found if the attribute is empty?
 
Alon
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
L=FCcking Claus
Sent: Wednesday, November 05, 2003 9:41 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Virtual attribute as ad-hoc object.
 
Hi,
=20
In my WF definition, I have an object instance of BUS1001006 =
(Material).
This object type has a virtual attribute for linked documents (Object =
type
DRAW). Now I want to provide a task with this multiline objects as =
adhoc
object, but I receive an error in the log if no values are found for =
the
attribute. (Message W8 110 Syntax error in expression =
&MATERIAL.DOCUMENT&).
If documents are linked to the material, everything works fine. I have =
tried
different solutions: Binding to Adhoc_Objects, Binding to a new =
multiline
object element of same type in the task, and binding to a new WF =
container
element with a container operation belonging to it, but always same =
result.
=20
Is it just not possible, or what am I doing wrong ? - No errors when I =
check
the tasks, bindings and definition.
=20
Ver. 4.6C Supp.Pack 45.
=20
Best regards,
=20
Claus L=FCcking
SAP Manager
=20
Danfoss Marine Systems A/S
Aaderupvej 41
DK-4700 N=E6stved
Phone: +45 5578 7261
Fax: +45 5578 7272
E-mail:  <mailto:clucking at danfoss.com> clucking at danfoss.com
=20