AW: Keep workflow running even though error detected

[Kevin Yu]

Hi Stephan,
 
Thank you for your reply, could you be more specific on "general task
classifications"?  I think I set the task as "general task" with a ro=
le
using Releasecode and Purchase group as perimeter from the workflow t=
o
the role container.  It has to be the same as development because it'=
s
been working for about one and half days.  However, our system's BASI=
S
component is only up to  SupPack 26.
 
Best regards,
 
Kevin.
 
 
"Becker Stephan (extern)" wrote:
>=20
> Hi Kevin,
>=20
> have a look if the general task classifications are the same in pro=
duction
> as they are in development. The error messages you get are not alwa=
ys an
> indicator of the real problem.
>=20
> Also, check your hot package level, there are still transport probl=
ems in
> 4.6C with workflows (see OSS), with Basis patch level 28 I have had=
 no more
> of those issues.
>=20
> Hth,
> Stephan
>=20
> -----Urspr=FCngliche Nachricht-----
> Von: Kevin Yu [mailto:kevin.yu at its.monash.edu.au]
> Gesendet: Freitag, 3. Mai 2002 13:43
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Re: Keep workflow running even though error detected
>=20
> Hi Bodo,
>=20
> Thanks.  The workflow that have had problem is the PO release workf=
low
> and it's been running for one and half day.  It suddenly complained
> about the mandatory element Releasecode is missing and deactivated =
the
> linkage type.  We cannot simulate the problem in Development and
> Testing.  Do you think it's to do with the Buffer - such as not eno=
ugh
> buffer space?  Once re-activated, it comes again after a couple of
> hours.  I am not sure it's a genuine blank Releasecode or not.
>=20
> Is there anyone has had this problem before?
>=20
> Kevin.
>=20
> "LANGE, BODO" wrote:
> >
> > Hi Kevin,
> > usually the Event linkage is turned off if there is an error duri=
ng
> exchange
> > of data
> > between the Event Parameter container and the workflow container.=
 You
> should
> > check your
> > data types of your developed workflows and see if they have chang=
ed after
> > the upgrade.
> > Maybe you have a type or length mismatch in one of your parameter=
s.
> Simulate
> > your Workflow Event and check your Event log.
> >
> > Good luck
> >
> > Bodo Lange
> >
> > -----Original Message-----
> > From: Kevin Yu [mailto:kevin.yu at its.monash.edu.au]
> > Sent: venerd=EC 3 maggio 2002 8.46
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Keep workflow running even though error detected
> >
> > Hi,
> >
> > We are in 46C.  The upgrade just went live four days ago.  It see=
ms that
> > in 46C if there is any error detected the system will just switch=
 off
> > the Event Type Linkage.  In 40B, even though an error detected it=
 just
> > sent an Inbox to the workflow administrator and the workflow just=
 kept
> > on running.
> >
> > In 46C, the error message still sent to the Workflow administrato=
r but
> > the system will automatically unchecked the Type linkage active b=
ox in
> > the Event type linkage.
> >
> > Is there any way or config ..etc to set so that even there is err=
or the
> > system will not inactive the Type Linkage?
> >
> > Thanks,
> >
> > Kevin.