2007 Jul 04 6:23 PM
hi friends...
could u plz tell me ater running a BDC Program in background, next day when i seethe result, few records are not updated(error records) what can i do then???
thanks in advance.
2007 Jul 04 6:27 PM
hi,
check out the internal table BDCMSGCOL if there are any errors
if the amount of erros is less create a session with those error records and process in foreground mode or no error mode..
if the amount of errors is more try to return the file to the customer giving the proper reason for the failure so that they will correct the data and send u the correct file.
But best option would be try to re run the session once again...
~~Guduri
hi friends...
could u plz tell me ater running a BDC Program in background, next day when i seethe result, few records are not updated(error records) what can i do then???
thanks in advance.
2007 Jul 04 6:27 PM
hi,
check out the internal table BDCMSGCOL if there are any errors
if the amount of erros is less create a session with those error records and process in foreground mode or no error mode..
if the amount of errors is more try to return the file to the customer giving the proper reason for the failure so that they will correct the data and send u the correct file.
But best option would be try to re run the session once again...
~~Guduri
2007 Jul 04 7:15 PM
hi,
if you are using SESSION method for migrating legacy system data to SAP R/3 you follow these steps...........
1) goto SM35 ( tr code for session)
2) here select your SESSION name
3) now select LOG tab option and click on that tab
4) it will dispaly's the LOG file with error records.
5) you can correct those errorrecords.
6) and process the session
<b>or</b>
if you are using SESSION method, by using executable program<b> RSBDCLOG</b> you can down load the error records and analyse the problem for raising error and correct the error records and process the session.
<b>frequently occured errors while working with SESSION method.</b>
1) required data has to missing in batch input session
2) invalid data has to be processing
3) there is scope for variations of screen sequences in BDCDATA table and orginal transaction.
<b>or</b> if you are working with DIRECT INPUT method for migrating data from legacy system to SAP R/3.
for handling and correcting error records, you must activate the restart mechanism for that one you work with tr code BMV0.
regards,
Ashok Reddy
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |