SAPTechno

Note 550176 - FAQ note legacy data transfer asset master records

Header
Version / Date 7 / 2003-01-27
Priority Recommendations/additional info
Category FAQ
Primary Component FI-AA-AA-A Master Data
Secondary Components

Summary
Symptom
    1. Which legacy data transfer methods are available in Asset Accounting and how are they different?
    2. Why does the system not transfer some fields from my input file to the asset master records?Why does the system display error AY219 "Field &1 is not ready for input"?
    3. Can I subsequently transfer legacy data in a production company code?
    4. How can I create legacy group assets?
    5. How can I transfer assets under construction (AuC) from my legacy system and what must I consider in this case?
    6. How can I generate test data for the transfer via BAPI?Where is the documentation of report RAALTDBDBR, which is mentioned in the R/3 library?
    7. When I execute report RAALTD01, why does the system generate error 00352 "'LEAVE TO TRANSACTION' & is not allowed in batch input" although the input file is correct?
Other terms

-

Reason and Prerequisites

-

Solution
    1. Question:Which legacy data transfer methods are available in Asset Accounting and how are they different?

              Answer: the following is an overview of the legacy data transfer methods with additional information on the transfering legacy assets R/3 library.

  • manual transfer with Transaction AS91

           This works like Transaction AS01 and is suitable for transfering smaller datasets.

  • RAALTD01 transfer via batch input.

           This is suitable for the mass processing of larger datasets. The batch input session fills the fields of Transaction AS91 up to and including Release 4.0B or of Transaction AT91 for subsequent R/3 releases.Therefore, only the data fields of these transactions can be filled.

  • RAALTD11 Transfer via direct input.

           This is suitable for transfering very large datasets. It transfers the same fields as RAALTD01 does, however it only carries out limited field checks.So that you do not receive any incorrect datasets as a result, first test at random the assets to be transferred in AS91 or as of Release 4.5B with Transaction AT91.

           Furthermore, bear in mind that value fields are not converted. If, for example you specify a value field for an amount of money in euro in the BALTD-structure, you must consider the format. If, for example the value field has the format ###,## and you only enter 10 as a value, this value is interpreted as 0,10. Therefore you must specify 10,00 as value in BALTD.

           To achieve the high performance of RAALTD11, the writing of change documents was also dropped. When you go into the change document display of an asset that was created with this report, the system generates the message "Asset created with Transaction AS02" or " ... AS92" by mistake.

              Both RAALTD01 and RAALTD11 have not been enhanced since Release 4.5B.As of Release 4.6B, the legacy data transfer therefore is recommended via BAPI BAPI_FIXEDASSET_OVRTAKE_CREATE since this offers all of the transfer options of the new Transaction AS91 (as of Release 4.5B).The following methods use this BAPI.

  • Transaction AS100 data transfer with Microsoft Excel

           This is suitable for the transfer of smaller datasets (limited by the line count of your Excel version).This transaction is suitable in particular if you have mapped your Asset Accounting prior to R/3 using Microsoft Excel.However, you can create only main asset numbers.More restrictions are described in Note 303710.

  • Transfer via Workbench LSMW or SXDA

           BAPI_FIXEDASSET_OVRTAKE_CREATE is used by Business Object Method BUS1022->CreateInclValues, message type FIXEDASSET_CREATEINCLVALUES and IDoc type FIXEDASSET_CREATEINCLVALUES01.You can also call it for the legacy data transfer even from your own program.You can find more information in the documentation of the function module in Transaction BAPI.

    2. Question:Why does the system not transfer some fields from my input file to the asset master records?Why does the system display error AY219 "Field &1 is not ready for input"?

              Answer: Report RAALTD01 only transfers the fields that are ready for input in Transaction AS91 (prior to Release 4.5B) or Transaction AT91 (as of Release 4.5B).Check your screen layout control (in the menu via "Environment -> Screen layout").With Note 68802, you can determine the ready for input status of the fields in the takeover values screen.

              AS100 and the BAPI only transfer the fields that are ready for input in the new Transaction AS91 (as of Release 4.5B).Here you can display the ready for input status of the fields in the takeover value screen via the menu option "Extras -> Info- readiness for input".

    3. Question:Can I subsequently transfer legacy data in a production company code?

              Answer: Yes, this is possible with restrictions. See Note 49563.

    4. Question: How can I create legacy group assets?

              Answer: You can manually transfer legacy data of group assets using Transaction AS81.Also RAALTD01 and RAALTD11 provide the option to create legacy group assets.BAPI_FIXEDASSET_OVRTAKE_CREATE provides this function only after the corrections have been imported into your system from Note 530197 via Support Package.

    5. Question:How can I transfer assets under construction (AuC) from my legacy system and what must I consider in this case?

              Answer: The method for transfering AuCs is described in Note 107507. Consider Note 197919.

    6. Question:How can I generate test data for the transfer via BAPI?Where is the documentation of report RAALTDBDBR, which is documented in the R/3 library?

              Answer: As specified in the documentation, it is possible to generate test data with report RAALTDBDBR. This is described in Note 533802.

    7. Question:When I execute report RAALTD01, why does the system generate error 00352 "'LEAVE TO TRANSACTION' & is not allowed in batch input" although the input file is correct?

              Answer: Note 523427 describes the cause for this error.

Related Notes
584144Expired useful life legacy data trnsfer: Error BAPI1022 004
573526Intracompany transfer w/ legacy data transfer during the FY
533802Legacy data transfer: RAALTDBDBR
530197Asset BAPIs cannot create any group assets
523427Legacy data transfer termination (RAALTD01) w/ error 00352
303710Asset Accountng: Excel legacy data transfer (AS100)
197919Legacy data transf.AuC proport.values not open
107507Legacy data transf.:AuC (w.line item)&inv.incentive
68802Legacy data trnsfr: diff.fields n.ready f.input
49563Subsequent data transfer to FI-AA