end of transaction does not terminate method

[MacPherson, Graeme (AU - Melbourne)]

Hi Patrick
 
In 31H this seems to be a problem. If the BDC session encounters an
abnormality (for example a screen has not been catered for or in BDC updates
the record is locked) then the object method completes the processing (as
much as possible) but the work item status does not get updated. Typically,
the BDC return code is 1001.
 
Try to debug the object method and use BDC call mode = 'A' so that you can
see if the BDC screen sequence etc is correct. You will probably find a
screen pops up under certain conditions which does not require input (and
thus allows the posting) but the call transaction return code is not 0
because the screen has not been included in the BDC session.
 
Cheers
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph: +613 9208 7100
Mob: 0414 473 554
 
 
-----Original Message-----
From: Patrick Pant - USA [mailto:patrick.pant at ixos.com]
Sent: Thursday, 9 November 2000 8:19
To: SAP-WUG at MITVMA.MIT.EDU
Subject: end of transaction does not terminate method
 
 
Hi CoFlowers,
 
we are encountering the following problem:
 
Release 31H, Kernel 31I
Symptom: In a custom implemented method the transaction FB10 is called in
batch input mode. upon returning, the message table is checked and depending
on the messages, the variables for the binding back to the workflow are
filled.
 
The method and the associated task has worked well in two different r/3
systems, but on the current consolidation system, the workitems very often
(not always) get stuck, meaning, the workitem does not turn to status
completed, although the invoice gets posted in FB10 and the method doesn't
stop. The code after the call transaction does not loop or anything, so
there is no chance it could get stuck in our code.
 
Any suggestions would be highly appreciated!
 
regards
 
Patrick
IXOS Software Inc.