太太药业PRINT7.DOCVIP

    Data transfer from a legacy system is usually the first activity you need to perform in a new productive system after configuration and asset classification. You can either transfer data automatically from an old system using a batch input procedure, or (with a very small asset portfolio) you could manually enter the data using a transaction for old asset data. Three methods are available according to the quantity of old assets data to be transferred: (1.) small quantity: Create old asset (dialog transaction) (2.) large quantity: batch-input procedure (RAALTD01) (3.) very large quantity: direct data import (RAALTD11) Please note that in all cases only the relevant asset master data and line items in Asset Accounting are updated and not the general ledger accounts in Financial Accounting. Balance reconciliation with the relevant general ledger accounts must therefore take place separately. You start the date transfer by setting the company code to the status for old assets data takeover. In this status no posting is possible, only data transfer.  You can transfer old assets data from a legacy system for any date in the past. The transfer date represents the cut-off point in time for the transfer of old assets data from the legacy system. In the R/3 system no old assets can be created before this date. This ensures that the data transferred from the legacy system is consistent on the transfer date. The transfer date can either be at the end of the last closed fiscal year, or in the fiscal year following the last closed fiscal year Data to be transferred: Year-end transfer and transfer during fiscal year: master data, cumulative values as of the end of the last closed fiscal year (1) Transfer during fiscal year (only): in addition to the master data and cumulative values of the last closed fiscal year (1), depreciation posted and asset transactions posted in the current year (2) have to be transferred ( Transfer Parameters). The transfer of the balances f