AW: Decision method is coded to remember last option
Dave J Dartnell
dave_dartnell at uk.ibm.com
Wed May 29 11:17:31 EDT 2002
Hi,
I believe the OSS note is 329227.
regards,
Dave
ITS SAP Development
(UK) South Bank (44) 207 202 5364 int. 7-435364 Mobx
274365
(USA) Sterling Forest (001) 845 759 4713 int. 248 4713
=
=20
"Becker Stephan (extern)" =
=20
<Stephan.Becker.ext at mchw. To: SAP-WU=
G at MITVMA.MIT.EDU =20
siemens.de> cc: =
=20
Sent by: SAP Workflow Subject: AW: De=
cision method is coded to remember last option =20
<Owner-SAP-WUG at MITVMA.MIT =
=20
.EDU> =
=20
=
=20
=
=20
28/05/2002 05:21 PM =
=20
Please respond to "SAP =
=20
Workflow Users' Group" =
=20
=
=20
=
=20
Hi there,
I just came across this issue. It comes in two flavours:
When processing a user decision with confirmation, take out the functio=
n
module in the "WI display" tab of the activity maintenance in the WS, t=
hen
it'll work all right. The cause for this error is that variables are be=
ing
passed sloppily when processing user decisions inline in the inbox thro=
ugh
the said function module.. SAP say they will not fix this as it is seld=
om
When processing methods with result parameters and end confirmations (l=
ike
any old approval), something similar happens. This is cured by an OSS n=
ote
(number escapes me at present..).
Hth,
Stephan
-----Urspr=FCngliche Nachricht-----
Von: Kisloff, Philip B [mailto:Philip.Kisloff at astrazeneca.com]
Gesendet: Dienstag, 28. Mai 2002 17:25
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Decision method is coded to remember last option
Hi all,
We are in 4.6C, and when I cancel processing of a generic user decision=
task
using the confirmation prompt,
the workitem returns to my inbox as expected. What is not expected by m=
e is
when I re-process the decision
I can not change the original result - I am presented with the confirma=
tion
prompt again.
I checked the code and found the following. I think this was introduced=
as
standard because the object header does
indicate any modifications. I'm sure it never worked like this before, =
does
anyone know what's up? I understand from
colleagues this behaviour has been known about through several patches,=
we
are currently on SAPKB46C28.
*-{
SWC_GET_ELEMENT CONTAINER '_RESULT' WI_RETURN.
IF SY-SUBRC EQ 0.
IF NOT WI_RETURN IS INITIAL.
I_AM_ALREADY_PROCESSED =3D 'X'.
ENDIF.
ENDIF.
*-}
Regards
Phil
=
More information about the SAP-WUG
mailing list