Receiver not entered error

[Mark Pyc]

It's hard to say without seeing your design, but I would assume that the key
of the object is changing mid-flow and if so I don't have an easy
answer. I've never had that situation myself.

However your description makes it sound as if you are starting a new
instance of the flow with the new key, but the wait for event is on the old
version - that sounds improbable, but maybe something weird is going on.

Sorry not to be of more help...

Have fun,
Mark


On 7/26/06, May, Kevin <KMay at petro-canada.ca> wrote:
>
>  Hi Mark, just got back to this.  You hit it right on the head.  There are
> two instances of the custom event('Reviewed'); one of type 'workitem' and
> one of type 'eventitem'.  The type 'eventitem' is the waiting version of the
> event and sure enough it has the right workitem id but the wrong key. I'm
> confused as to why it has the correct receiver key but yet the wrong object
> key.  It's almost as if it stored that last key used.  So how would I go
> about properly preparing the waiting event.
>
> Thanks much, you've been very helpful.
>
> Kevin
>
>  -----Original Message-----
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Mark Pyc
> *Sent:* Wednesday, July 26, 2006 7:29 AM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: Receiver not entered error
>
> G'day Kevin,
>
> If the event raised is 01 and the wait for event is expecting 00 then they
> won't match up. You can see which instance the wait for event is expecting
> either in Extras > Instance Linkage from the Wait Workitem, or from txn
> SWEINST.
>
> If the object key can change you need to ensure that any existing wait
> event is still logically correct.
>
> Have fun,
> Mark
>
>
> On 7/26/06, May, Kevin <KMay at petro-canada.ca> wrote:
> >
> >    Hi folks, I've got a bizarre sort of problem.  I've got a workflow
> > that seems to be error free end to end when I use the diagnostic tool.  In
> > practice it works fine as well however in one instance I get an error I
> > cannot understand.  The workflow has a 'wait for event activity', the event
> > it is waiting for is a custom event from a custom BOR.  The key of the BOR
> > are two char fields, one 20 chars long the other 2 chars.  In the second key
> > represents an iterative entry for example '00' and then '01'.
> >
> > The user typically will create a document with a key i.e. 'Some text' &
> > '00' and then submit it to workflow.  This works wonderfully and the various
> > steps and conditions of the workflow execute without error.  However when
> > the user makes a revision to the document resulting with a new key i.e.
> > 'Some text'  & '01' and triggers the workflow,  when the event is raised
> > from the custom BOR it goes into error with 'Receiver not entered'.  The
> > workflow stalls at the 'wait for event' step in the workflow.  I used the
> > workflow trace and all the containers appear to be loaded correctly, the
> > workitem is sitting with the correct agent.  I really don't understand why
> > when the event is raised for 'Some text' & '00' it works fine however when
> > it is 'Some text' & '01' it has the receiver not entered error.  Any help
> > offered will be appreciated.
> >
> > Kevin
> >
> >  ------------------------------
> >
> > This email communication is intended as a private communication for the
> > sole use of the primary addressee and those individuals listed for copies in
> > the original message. The information contained in this email is private and
> > confidential and If you are not an intended recipient you are hereby
> > notified that copying, forwarding or other dissemination or distribution of
> > this communication by any means is prohibited.  If you are not specifically
> > authorized to receive this email and if you believe that you received it in
> > error please notify the original sender immediately.  We honour similar
> > requests relating to the privacy of email communications.
> >
> >
> >
> > Cette communication par courrier électronique est une communication
> > privée à l'usage exclusif du destinataire principal ainsi que des personnes
> > dont les noms figurent en copie.  Les renseignements contenus dans ce
> > courriel sont confidentiels et si vous n'êtes pas le destinataire prévu,
> > vous êtes avisé, par les présentes que toute reproduction, transfert ou
> > autre forme de diffusion de cette communication par quelque moyen que ce
> > soit est interdite.  Si vous n'êtes pas spécifiquement autorisé à recevoir
> > ce courriel ou si vous croyez l'avoir reçu par erreur, veuillez en aviser
> > l'expéditeur original immédiatement.  Nous respectons les demandes
> > similaires qui touchent la confidentialité des communications par courrier
> > électronique.
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
> >
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060727/04d804c6/attachment.htm