Legacy Asset Data Upload in mid/current fiscal year

[Former Member]

Hi Experts,

My client went live in Oct 2016 and wasn't ready to upload asset and GL legacy data only now. The current status is that my client Prod system already has created asset masters in the live system and continuing.

Please suggest if there is any downstream impact if we use a custom program to upload asset data using back end t code AS91 for master data and transaction values.

What step by step rules should we follow? I am aware of the steps but since this is mid year upload and in the current fiscal year, I wanted to make sure that there is no adverse effects of it. Please note that the take over date maintained in the configs is 03.10.2016 and we follow Apr - Mar Calendar.

Apart from the below steps, is anything else that needs to be taken care of:

1. Prepare inputs files.

2. Upload Asset master and transaction values.

3.Reset recon OAMK.

4. Perform recon OASV or ABF1 or F-02. Which is the best suited t code? What should be the exact journal entries to be passed? What GL accounts do we have to maintain before proceeding with legacy data upload? For eg. Asset conversion GL account etc

Thanks in advance!

[Former Member]

Hi Tanu,

your closed fiscal year will still be in line with Legacy data Transfer Date as you follow April- March calendar.

You can perform Standard SAP transaction for loading legacy system data. you can prepare LSMW for loading data through AS91 and perform migration of Asset master data and accumulated APC and Accumulated Depreciation values for assets which were maintained in your legacy system.

Regards,

Jignesh

[former_member205041]

Hi Tanu,

There is a high risk.

May I ask you for the reasons to use a custom programn and not SAP standard tools?

best regards

Bernhard