AW: Trip workflow

Giesinger Marc Marc.Giesinger at egger.com
Thu Mar 14 02:56:57 EST 2002


sorry Patrick
 
is a standard taks without any binding !
so everything looks ok so i ask again :-)
 
maybe the method not "web-able" ??
 
thanks Marc
 
-----Urspr=FCngliche Nachricht-----
Von: de Valensart Schoenmaeckers, Patrick
[mailto:deValensartSchoenmaeckers.Patrick at pmintl.ch]
Gesendet: Mittwoch, 13. M=E4rz 2002 17:49
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Trip workflow
 
 
Marc,
 
Your task TS20000118 must be a copy of the standard decision task
TS00008267. Copies of that task musn't normally have any binding
taskcontainer-methodparametercontainer. So the trick to make it work is =
:
enter the task in change mode, enter the binding OM, select menu path
Binding > Delete, go back until the system asks you to save the task =
(but do
not save it before the system asks you to do so, otherwise it will
automatically put default binding back). This is to be done every time =
that
you enter your task in change mode.
 
This is how it works in 40B, but still, I guess it is worth to try it =
in
your 46C system.
 
Hope this helps.
 
---------------------------------------------------------
Patrick de Valensart
Information Services
Philip Morris S.p.A.
Via Salandra, 18, 00187 Roma, Italy
---------------------------------------------------------
 
 
 
-----Original Message-----
From: Giesinger Marc [mailto:Marc.Giesinger at egger.com]
Sent: Wednesday, March 13, 2002 5:38 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Trip workflow
 
 
dear workflow`ers
 
ever had this problem ?
 
we=B4re using (on 4.6C) the SAP standard Trip WF which has an decision =
step
TS20000118 - Approve travel request - inside.
 
we create trip WF (requester) via ITS - ESS  which works fine ...
but when the approver gets the item for decision (the standard task
TS20000118 - Approve travel request) he / she won`t be able to process =
it
via ITS inbox service:
 
the system means "could not find workitem"  (=3Dnever had a message =
like this
:-)
 
the method of the task is PROCESS from object DECISION. if this method =
is
not processable via web (as i think) im wondering what SAP thougt while
creating this templete: the first step can be done via web but NOT the =
next
ones ???
 
maybe im wrong with the method or forgot something else ??
 
anyone uses this templete also ?
 
thanks=20
 
Marc =20
 


More information about the SAP-WUG mailing list