WL821 error, when executing customized user decision
Garcia, Carlos
carlos.garcia at sap.com
Fri Feb 9 13:18:11 EST 2001
Hi Philip:
=20
I used a copy of TS40007902, and this time the decision works jut fine.
I also tried your advice about deleting the bindings but it continues =
giving
me the same error.
About the OSS note you're talking about seems to be 0155129 Single step
task: binding can not be deleted.
=20
R/3 note no. 155129 09.02.2001 Page =
1
=
________________________________________________________________________=
=20
Number 0155129
Version 0003 from 02.06.1999
Status Released for customer
Set by Patrick Schmidt on 02.06.1999
=20
Language EN
Short text Single-step task: Binding can not be deleted
=20
Administrator Patrick Schmidt
Component BC-BMT-WFM SAP Business Workflow
=
________________________________________________________________________=
=20
Long text
Symptom =
=20
If you define a new single step task and switch to the binding between =
=20
task container and method parameter container, then binding is =
displayed=20
even if there had previously been nothing entered or something had been =
=20
deleted. =
=20
This binding is automatically created in the change mode. =
=20
This underlying binding generation also occurs for a copy of the =
generic=20
decision task (TS8267), however, the work item is not executable and =
=20
will produce an error. =
=20
This binding is not needed in most of cases, because, if no binding was =
=20
defined between task and method, the container is completely copied. If =
=20
all elements of the task container resulted automatically when you =
=20
entered the object method, they are identical and copying the =
containers=20
is harmless. =
=20
Additional key words =
=20
=
=20
Cause and prerequisites =
=20
=
=20
Solution =
=20
To delete the binding completely as to allow the container to be copied
choose "Binding" =3D>"Delete" in the Binding Editor menu.
It should be noted that this operation is not possible for method
parameter containers with mandatory parameters.
It should also be noted that binding is repeatedly regenerated when you
call the Binding Editor in the change mode.
Source code corrections
________________________________________________________________________=
=20
Valid releases
=20
R/3 standard 45A - 45B
40A - 40B
300 - 31I
=20
________________________________________________________________________=
=20
=
=20
=20
Thank you very much.
=20
Regards.
=20
Carlos Garcia
SAP M=E9xico.
=20
-----Original Message-----
From: Kisloff, Philip (CH - Basel) [mailto:pkisloff at dc.com]
Sent: Viernes 9 de Febrero de 2001 5:48 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WL821 error, when executing customized user decision
Hi Carlos,=20
You have to delete the all bindings (even if just spaces) with the =
object
method=20
using the delete function key. Any other way will not delete the =
bindings.
Every=20
time you view the bindings in change mode, you have to delete them =
again!
There is=20
an OSS note on this somewhere, and for this reason I guess the 4.6D
documentation=20
says not to create decison tasks by inserting the object into a new =
task,
but by=20
copying the standard task.=20
I lost many days trying to solve this one when I first met it.=20
Regards=20
Philip Kisloff=20
Deloitte Consulting=20
Oberwil-CH=20
=20
-----Original Message-----=20
From: Garcia, Carlos [ mailto:carlos.garcia at sap.com
<mailto:carlos.garcia at sap.com> ]=20
Sent: Thursday, February 08, 2001 11:32 PM=20
To: SAP-WUG at MITVMA.MIT.EDU=20
Subject: WL821 error, when executing customized user decision=20
Hi everybody=A1=20
I=B4m working on a Purchase Requisition Workflow (4.0B) with a =
customized user
decision (copy of TS00008267). Everything goes fine, the workitem is =
created
in inbox of the right person showing in the workitem description the =
BUS2009
attributes. But when I try to execute it, only changes the status from =
READY
to IN PROCESS, Checking the workitem history shows a WL821 error =
(unable to=20
execute method PROCESS from object DECISION). I already revised the OSS =
notes but i didn=B4t find one, which could solved this problem. The =
weird=20
thing is that if I use the standard user decision, it works.=20
Any advice or guidance will be very appreciated.=20
Best regards.=20
Carlos Garc=EDa=20
More information about the SAP-WUG
mailing list