AW: FIPP.COMPLETED problem in 4.6c

[Becker Stephan (extern)]

Have you tried the system log for entries for the times when you should =
have
been getting these events? I've just had the case where a short dump
intermittendly interrupted background processing, and we only knew what =
was
causing it (a GUI error believe it or not) when we started looking at =
the
dumps and comparing times..
 
Hth,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Susan R. Keohan [mailto:skeohan at MIT.EDU]
Gesendet: Freitag, 29. M=E4rz 2002 01:27
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: FIPP.COMPLETED problem in 4.6c
 
 
Forwarded on behalf of Rob Bates...
 
>
>To:       SAP-WUG at mitvma.mit.edu
>cc:
>From:     Rob Bates/ITnet
>Date:     03/27/2002 03:14:32 PM
>Subject:  FIPP.COMPLETED problem in 4.6c
>
>Hello everybody,
>
>I'm currently engaged in a long-running discussion with OSS about a
>problem that
>I am having with the FIPP.COMPLETE event. The problem is intermittent, =
and
OSS
>keep trying to put me off - but I'm sticking with it! I was hoping =
that
maybe
>other people have experienced the same problem and have a solution - =
or
>you are
>also waiting for a solution and can keep me company in my misery! =
(This
>has been
>going on for 3 months and 4 support packs).
>The system is 4.6c with support pack 28.
>The problem is as follows:
>User creates a parked document using transaction F-65, and parks it =
without
>completing it.
>(Workflow starts and immediately hits a 'Wait for event - =
FIPP.COMPLETED'
>step).
>Later, a user changes the parked document using transaction FBV2 and =
saves
>it as
>complete.
>At this stage the FIPP.COMPLETED event should be published. However,
sometimes
>it is, and sometimes it isn't! I've checked this with the event log. =
There
>seems
>to be no pattern to explain when it works and when it doesn't. I've =
tried
>changing the actual data, or just saving unchanged data as complete. =
I've
done
>it through a variety of processes (change, save, change complete; =
change,
>save,
>no change, complete etc.). The Complete flag is always set correctly, =
and
>document changes shows the complete flag changing from blank to X. The
>FIPP.COMPLETE event is active, with no check function. The event =
instance
>table
>is full of unresolved FIPP.COMPLETED entries.
>
>Has anybody experienced the same problem?
>
>Thanks,
>Rob Bates,
>ITNET UK Ltd.
>
>
>
>
>
>***********************************************************************=
****
****
>****
>http://www.itnetplc.com
>
>Any opinions expressed in this email are those of the individual and
>not necessarily those of ITNET plc and/or its subsidiaries. This email
>and any files transmitted with it, including replies and forwarded
>copies (which may contain alterations) subsequently transmitted from
>ITNET plc and/or its subsidiaries, are confidential and solely for the
>use of the intended recipient. If you are not the intended recipient
>or the person responsible for delivering to the intended recipient, be
>advised that  you have received this email in error and that any use
>is strictly prohibited.
>
>If you have received this email in error please notify ITNET Customer
Service
>Centre by telephone on +44 (0)121 683 4043 or via email to
>csc.com at itnetplc.com, including a copy of this message.
>Please then delete this email and destroy any copies of it.
>***********************************************************************=
****
****
>****
>