Batch Input and Direct Input 

For the legacy data transfer of fixed assets, you have the standard functions of the Data Transfer Workbench at your disposal. The following contains information on the batch input and direct input procedures for legacy data transfer that are specific to Asset Accounting.

Legacy Data Transfer Using Batch Input Procedure (Program RAALTD01)

When you use the batch input procedure, the system creates a batch input session containing the legacy data, and automatically processes this session. This method supplies the legacy data transaction of the Asset Accounting (FI-AA) component with data. The system writes any transfer records that have errors to an error session for later manual processing.

Legacy Data Transfer Using Direct Data Input Procedure (Program RAALTD11)

When you use the direct data input procedure, the system writes the legacy transfer data directly to the appropriate tables in the Asset Accounting component. The system writes any assets that have errors to an error file. This procedure normally offers improved performance, as compared to the batch input procedure. However, there are certain limitations as regards the input data and errors. For more information, see Direct Data Import.

When the number of legacy assets is fewer than  50 000  to  100 000  , you should carry out legacy data transfer using batch input, since this procedure is better able to ensure that incorrect data is not transferred to the SAP System. Depending on your hardware, the batch input interface is normally able to import approximately 150 asset master records per minute (including transactions) to the SAP System.

For large numbers of legacy assets, SAP recommends the direct input procedure, since it can increase performance by about 10 times in comparison to transferring using batch input.

Object-Specific Settings and Options

You use the activity category to choose either batch input transfer or direct data import.

Constraints

·        The Data Transfer Workbench limits the transfer structure to a maximum of  5 000 characters. Therefore, using the Data Transfer Workbench is possible only if you have fewer than 10 depreciation areas. When you have 10 or more depreciation areas, transfer structure BALTD (asset master data and values) can become longer than  5 000 characters. In that case, you have to carry out the transfer directly, either using report RAALTD01 (batch input) or RAALTD11 (direct data import) in transaction SE38.

You can use the Dictionary (transaction SE11) to find out the length of your BALTD transfer structure (choose Dictionary object → Display). To see a screen listing the header data and fields of the transfer structure, choose Utilities → Runtime object → Display. You see the character length of your transfer structure in the Len column in the header data.

·        Net book values cannot be transferred. You have to transfer gross asset values (APC and accumulated depreciation). The system then calculates the net book values.