Asset takeover: Depreciation posted although OAYC "last period posted in legacy" is in the future

[Former Member]

Dear SAP pros,

We currently do an asset takeover during the fiscal year. We've set the last period which was posted in the legacy system to 05/2012 in transaction OAYC.

After the takeover in the quality system, everything looked well in AW01N. Depreciation was planned to start in period 06/2012 for the migrated assets. We also see the special entry for "Legay takeover value" in period 05/2012 in the tab "posted values". Depreciation for period 03/2012 was not yet posted as the system is already live. So we did the depreciation run for period 03/2012 and expected no posting to the newly migrated asset. But to our suprise, SAP posted depreciation for the migrated assets. In AW01N, we can now see the posted values above the line for "legacy takeover value". Furthermore, SAP also wants post depreciation in periods 04 and 05 now.

The value for the year is still correct but we don't understand the posting. SAP tells in the documentation of OAYC that the depreciation will start after the period which is defined in OAYC but obviously it is doing the opposite.

Has anyone had this issue before?

Thanks and best regards,

Peter

[Former Member]

Hi Ravi,

I can exclude this possibility as I'm the only one who is currently working with this data.

But anyway many thanks for your help (points have been assigned :-)!

Best regards,

Peter

[Former Member]

Hi Ravi,

Yes, we have calendar year and also calendar months as posting periods.

Take-over date: 31.05.2012

Last period depreciation posted in legacy system: 05/2012

Looks fine for me.

Thanks and best regards,

Peter

[former_member182098]

I could not think anything else.

May be as a last check, please check if anybody has manipulated the expired useful life at the time of doing AS91. This is the only thing which can have impact. m

Regards,

Ravi

[Former Member]

Hi Ravi,

Yes, this was entered in AS91:

- Accum. depreciation until end of last year in the respective field

- Posted depreciation in legacy system in current year until period 05/2012 in the respective field

Everything was looking fine in AW01N before we did the depreciation run for 03/2012. There was no planned depreciation for periods 03/04/05. But after the depreciation, SAP started calculating and posting depreciation in periods 03/04/05. The strange thing is that the overall depreciation in these periods is zero but we would expect no posting at all as we defined in customizing that the depreciation until 05/2012 was posted in the legacy system.

Thanks and best regards,

Peter

[former_member182098]

Hi Peter,

I believe you are using calender year.

What is the cut over date configured?

There are only two things we should look into:

a) Take-over date (I would expect this you must have put as last date of your period 05) - Please confirm

b) Last period depreciation posted in Legacy system.

I do not see any other configuration affecting this.

Regards,

Ravi

[former_member182098]

It seems there is some problem with your cut over date configuration.

Ideally, the depreciation for the current year, which is posted in your legacy system should have been entered in asset loading through AS91.

You need to rectify your load in AS92.

I would expect you must have checked all these things in QA system before facing all the troubles in PRD.

Thanks,

Ravi

[Former Member]

Fortunately we are still in the quality system. I'm pretty sure that the date configuration as well as the entered data in AS91 are correct.

The problem seems to be that the depreciation wasn't posted until the last period before the takeover date. It seems that we'll not have this situation in the production system but I was wondering whether somebody has seen this before that the setting in OAYC is ignored by SAP.

Thanks and best regards,

Peter

[former_member182098]

What the date that is being mentioned for

Specify Transfer Date/Last Closed Fiscal Year

When you are taking the data through AS91, have you entered the depreciation posted during the current year has been account for. (not just the cumulative depreciation, but you should have entered the depreciation posted in the current year as well). Could be this is causing the issue?

Thanks and Regards,

Ravi