‎2007 May 07 7:24 PM
helo experts plz answer this question?After running a BDC program in background, next
day morning when you see the results, few records
are not updated(error records). What will you do
then?
‎2007 May 08 5:18 AM
hi,
If you are using Session method you can check unprocessed records at SM35, check them and reprocess those records.
If you are using Call Transaction method pass those unprocessed records to a file , check them and reprocess them or open session for unprocessed records u can check them in SM35 and reprocess them.
‎2007 May 07 7:26 PM
Hi,
If you use session method for your BDC program, you can go to transaction SM35 to see the errors and reprocess them as well.
If you use call transaction method, you can go to SM37 to analyze and figure out the error messages and try torerun the BDC program for those errors only.
Regards,
Ferry Lianto
‎2007 May 07 7:46 PM
Collect those data to a error session. Next day, you run that data in foreground. You will get the reason of that error in the screen , correct that error and run the BDC for that record.
Check the error_session option of call transaction.
‎2007 May 08 5:18 AM
hi,
If you are using Session method you can check unprocessed records at SM35, check them and reprocess those records.
If you are using Call Transaction method pass those unprocessed records to a file , check them and reprocess them or open session for unprocessed records u can check them in SM35 and reprocess them.
‎2007 May 08 12:48 PM
Hi,
As per your Question, It depends like this.
If it an Session method, all the errors will be captured as an log and you can view it and process the error ones.
If it is Call Transaction, Obsivously, You have to maitain an Internal Of type BDCMSGCOLL, Which will capture all your errors. As Message id , Screen NUmber, Message type, Field name etc.
<b>As per your Questions, it seems to be that you are shcdeluing the BDC program.
If that is the case, You can see the Spool in SM37, which will contains, all errors as well as processed records.</b>
Thanks
Manju.