When you transfer legacy data using batch input, the transactions that are triggered are carried out in the background. If there are no errors found, posting takes place. If errors are found, the transactions with errors are placed in the batch input session under the name you entered in the Name of the error session field. By processing this batch input session, you can later correct the transactions with errors.
Statistics are created for every transfer run. In the case of errors, the first error that appears (for each asset) is logged. By selecting the logged error, you can display the long text for the error message.
Causes of Errors
Serious comprehensive errors that cause a program termination are:
Errors that Cause Termination
If no database updates were made before the error occurred, the error causes a simple termination. Once the error is corrected, the transfer run can be restarted from the beginning.
If, however, assets were already processed and database updates carried out when the termination occurred, the system generates a log about the data records already processed, as well as the cause of the termination. You must now be aware of two things:
It is possible that errors already occurred in records before the termination. These are now recorded in the error session and must be reprocessed.
The key of the first data record that was not processed is displayed in the termination log. The cause of the termination has to be removed. You have to create an input file that contains the corrected data records, starting with (and including) the record at which termination occurred. After this, the program can process the newly created input file that contains only those records that were not yet processed.
As an alternate solution, you can reset the company code for Asset Accounting. If you reset the company code, you could then use the original input file with all of its data records.
In the test run, as well as in the update run, you can process the transactions in the foreground using the Transaction flow in the foreground option. In a test run, however, this only allows you to observe one transaction. This occurs because no actual posting takes place, and the system therefore always stops on the last transaction screen.
To be able to see more transactions during a test run, you have to leave each transaction by choosing 
Cancel when the transaction is finished (OK code field is blank). Choose No in the resulting dialog box.
