BDC session not processing next record if error occurs

[Former Member]

Hi ,

Before posting this thread I tried searching google and forum but not able to trace right solution.

I have written BDC program for transaction QM01. When I process the BDC session it halts on the first record saying notification no already exists.

If notifcation no already exists then BDC session should skip it displaying error and should process next record but it is not happening.

I executed program using call transaction with all screen mode and I found same problem. Program displays the error message and do not proceed further.

I do not have any clue, can anyone guide me ?

Thanks ,

Narayan

[Former Member]

Hi,

BDC cannot proceed once it encounters an error message. You will have to do the recording of the transaction in such a way that it will not encounter any error message.

So that it will not halt the whole BDC session. And if the error message is unavoidable, then BDC cannot be used under these cirumstances. You might have to go for BAPI.

Thanks,

Archana

[Former Member]

Hi,

Please check in your program if the notification exists in table QMEL.

If it doesn't , then only populate the BDCTAB and process the BDC session.

Regards,

Srini.

[Former Member]

Hello,

Try using BAPI_QUALNOT_CREATE instead of recording.

Hope it helps

Regards

Sachin

[Former Member]

Please pass messages in message table in the call transaction ....

call transaction 'QM01' mode 'N' update 'S' MESSAGES INTO itab.

Regards,

Lalit Mohan Gupta

[Former Member]

What is your display mode? If not 'N'-None, the BDC session will stop, and you must enter the /bend command to proceed to the next call transation block in the BDC table. In N-None, an error should result in bdc session being flagged as an error....at the end of BDC processing, you will then have a good transaction count and an error transaction count. SAP supports reprocessing of the errirs BDC sessions, usually done in foreground, so that the user can step through the screens and correct the data errors.

[Former Member]

closed