Virtual attribute as ad-hoc object.

[Lücking Claus]

Thanks Jocelyn, I will report the problem to OSS, and have a look at
Alternative Bindings.
 
Claus.
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]=20
Sent: 6. november 2003 10:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Virtual attribute as ad-hoc object.
 
 
Hi Claus,=20
If you don't want two tasks you could also look at using the =
"Alternative
binding" option.=20
 
But I'd suggest taking up that particular example with OSS and getting =
the
developers to look at it specifically.=20
I know Alon's asked before but it helps to let them know the pain =
points
with very very specific examples.=20
Regards,
        Jocelyn Dart=20
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"=20
SAP Australia
email: jocelyn.dart at sap.com=20
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: L=FCcking Claus [mailto:clucking at danfoss.com]=20
Sent: Thursday,6 November 2003 7:44 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Virtual attribute as ad-hoc object.
 
 
Alon,
 
you was right, the note didn't helped me. Implementing the work around =
you
suggest would be something like having two almost identical tasks, =
where the
binding is missing to one of them, and then in a condition step before =
the
two tasks investigate the content of the attribute? - or do you see a
solution, where one task would be enough?
 
Thanks in advance.
 
Claus.
 
-----Original Message-----
From: Alon Raskin [mailto:araskin at 3i-consulting.com]=20
Sent: 5. november 2003 14:16
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Virtual attribute as ad-hoc object.
 
 
Hi Claus,
 
I could be wrong but I don't think that this will fix the problem you
describe. Your problem is (as I understand it), that the workflow =
errors if
you bind in an 'empty' attribute (ie. An attribute which legitimately =
has no
value) you get syntax error messages.
 
I have taken this issue many times with OSS and they have repeatedly =
denied
that the problem is theirs.=20
 
Anyway, the work around to fix this is to do an existence check before =
you
bind in your attribute. You can do this using a Condition step in your
workflow.
 
I could be way off base with what your problem actually is... so =
forgive my
ranting if I am wrong.
 
Regards,
 
Alon Raskin
3i-consulting Group
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
L=FCcking Claus
Sent: Wednesday, November 05, 2003 1:03 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Virtual attribute as ad-hoc object.
 
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