BDC session method Background Processing - Error occurs randomly

[Former Member]

I am updating Tcode VB12 using BDC program in which i used BDC session method and then

used Fm: Open_job , Submit RSBDCSUB..., FM close_job.

The Problem is that sometimes the Session is not processed successfully. In Error log it contains messsage 'No batch input data for Screen ....' and when i rerun this session in Foreground it works fine. This happens randomly and not everytime.

I can't figure out why it is ok for some sessions and not for others.

It seems that something going on in its memory or something like that ?

Can any one figure out this?

[Former Member]

when you process in the foreground , somewhare you get this error 'No batch input data for Screen ..

again you press the enter its going to process..

when you get and regarding which field getting this error and why this is occured

its may be data problem or recording problem...

[Former Member]

Hi,

Th error 'No batch input for the screen' is because it is expecting some input value or the field is not there but in the file your passing the value for that field. So out of these two cases any one be the reason...so please check the data first and then if the problem persists still please let me know.

Hope this will help.

Regards,

Rohan.

[Former Member]

Hi

well try to find the patterns in the reocrds when BDC is giving the error message .

It might be coz of data ,in some cases coz of your data some additional screen or check box might be coming in the transaction and that might be missing from your bdc recording.

Regards

Neha

[Former Member]

The status 'No Batch input dat for RV13D900 1000 ' stops my session to process in background.

I tried your suggestion.

I see a check box appears on screen, when i go into se51 and open the screen layout. But this Check box is invisible in transaction.

when passed this checkbox value as X / Space and passed to BDc table it isn't working and throws status message Field XXX.. do not exist in screen RV13D900 1000.

Do you have any idea?

[Former Member]

Solved..this is due to session interaction and time lag kept between individual sessions.