UPDATE: No receiver entered

[Becker Stephan (extern)]

Tim,
 
neither solution sounds too exciting to me, to be honest.. executing a
second time is dodgy enough, but just erroring out is of course even worse.
Silly question, but why don't you check the return code of the external
function, create a method exception with exit_return and then loop/wait and
try again?
 
As per the error messages, that seems to be a "feature" of SAP in general;
when a function goes belly up, the "real" error message often gets lost in
the process, and the last or just any old message is displayed to the user..
if you are unsure, a table element where you collect all messages while
running a method is a good way to collect everything; you will have all
messages in the container of the workitem after the fact. This worked for me
nicely when a call transaction failed in a method, and it took all messages
into the deep blue at first when failing..
 
Stephan
 
-----Original Message-----
From: phillips, tim [mailto:tim.phillips at SERuk.com]
Sent: Montag, 4. Februar 2002 17:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: UPDATE: No receiver entered
 
 
Previously in 'No receiver entered':
 
virendradapt wrote:
 
>>>> Susan:
>>>> Although I don't know if this is the answer to your problem,
>>>> since I was just there yesterday, the config is fresh in my mind.
>>>> It sounds as though you may be missing the assignment of an agent
>>>> to the document type.
 
>>> Timbo:
>>> Thanks for the quick reply,
>>> as well as for the useful screenshot.
>>> That part of the workflow hadn't yet been configured -
>>> it seems to be new to 4.6c;
>>> typically I'm more used to the SOA3 transaction in 4.0b.
>>> However, I'm still encountering the same problem,
>>> and am still getting 'No Receiver Entered' in the
>>> workflow log.
 
>> Virendra:
>> Just a thought, is the task made "General Task" ?
 
> Timbo:
> Yes, I was sure to make this setting.
 
_______________________
 
 
Timbo:
After another morning in the debugger,
I've made another discovery, which, hopefully,
some of this group may be familiar with.....
 
The problem appears to be the results of an
extra line of code in 4.6b,
which hitherto was not present in 4.0b -
the level of SAP with which I am most familiar.
 
I've reached the conclusion that SAP have
tightened up their Inbox coding,
particularly in the case of workitems whose
execution involved contacting an external system.
 
Previously, if the external system was not present,
I just used to click on the workitem a second time
in order to execute - and it worked fine!
 
Not in 4.6b;
it would appear that if the communication fails,
the workitem is rendered worthless
and must, henceforth, be deleted logically.
 
Conversely, if the connection is successful,
the receiver is found and everything works OK.
 
I must admit: it still seems a bit odd -
particularly the error reporting -
'No receiver entered' was way off the mark!
 
Any comments?
 
Regards,