SWEL - Missing Receiver ID In Event Trace

[Dave J Dartnell]

We had a similar symptom some time back, missing entries in event creation
status management, transaction BSVW.
 
 
Dave Dartnell
Workflow team
 
 
 
 
 
                      "Nobles, Diane"
                      <nobles_dh at naptheon        To:       SAP-WUG at MITVMA.MIT.EDU
                      .com>                      cc:
                      Sent by: SAP               Subject:  Re: SWEL - Missing Receiver ID In Event Trace
                      Workflow
                      <Owner-SAP-WUG at MITV
                      MA.MIT.EDU>
 
 
                      16/07/2002 04:24 PM
                      Please respond to
                      "SAP Workflow
                      Users' Group"
 
 
 
 
 
I had this problem once, sometime ago.  Can't remember the exact fix, but I
believe it was a container issue.  Make sure your event container elements
and the WF container elements are the same.  Also check your WF version and
refresh the buffer.
 
Diane H. Nobles
SDE PM Team
(757)380-7250
 
 
 
-----Original Message-----
From: Ea, Ty [mailto:TEa at citgo.com]
Sent: Tuesday, July 16, 2002 10:12 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: SWEL - Missing Receiver ID In Event Trace
 
 
Workflowers,
We are experiencing a major problem.  When a triggering event is published,
under the event trace (SWEL), we can see that an instance was created with
the appropriate receiver type.  However, the workitem is not created
although we know is should be.  Although the event trace shows that an
event
was published and has a Receiver Type, there is no Receiver ID.  In
addition, a Receiver FM is present for each instance with the status of
'Receiver started correctly'.  Why is the Receiver ID missing?  Has anyone
experienced anything similar to this?  It appears to be system-wide and
sporadic.  We are in version 4.6C.
 
Thanks for any and all help!
 
Ty Ea
 
 
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.