Skip to Content
0

Asset legacy data posting to non leading ledger

Nov 01, 2016 at 08:30 PM

333

avatar image
Former Member

Dear All,

We have an issue with legacy data posted to leading and non- leading ledger and depreciation posted thereafter.

We have two different fiscal year variants for leading ledger 0L and non leading ledger UI- Income tax. We have posted legacy data for asset accounting in FI using transaction OASV on 31.07.2015. The postings were made to leading as well as non- leading ledgers.

However, when first depreciation run was done, depreciation of an equivalent amount got posted in non- leading ledger 'UI- Ledger for income tax' also, resulting into duplicate posting of depreciation amount.

We are trying to post reverse document using transaction OASV on 31.03.2016. But we are getting error F5 567 Period 03 is not allowed.

Can anyone suggest how to remove the impact only in non- leading ledger without impacting leading ledger transactions.

Best Regards,

Disha.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Sanil Bhandari Nov 02, 2016 at 01:38 AM
1

Hi

Is there any specific reason that GL were updated by you for income tax depreciation since generally not posted to GL Accounts?

That said, create a transaction type that should post only to tax depreciation area. Make sure you restrict it to specific depreciation. All both positive and negative values for depreciation and make a posting using the new transaction type for depreciation area as unplanned depreciation with the fact that it should be posted with positive values so that earlier depreciation posted should be nullified. Now run depreciation run and ASKBN as of 31.03.2016.

I guess this is probably the only option you have now. Try this first in a test system and share the results with your business for approval before posting this in production.

Regards

Sanil Bhandari

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello,

Thank you sir for a prompt response. GL for income tax was created post go- live and so no legacy data got posted to that ledger when OASV was run. However, the ledger existed as on the date of depreciation run. So depreciation value was correctly posted. Then when ASKBN was run, legacy values were posted in non leading ledger resulting into duplicacy of depreciation values.

We are however trying to post to non leading ledger directly using transaction FB50L. Will share the impact with business and proceed as per their suggestions.

Best Regards,

Disha Trivedi.

0
Mukthar Ali Ahamed N Nov 02, 2016 at 04:28 AM
1

Hi,

In addition to Mr.Sanil said, you can also change the dep.key as 0000 for the income tax dep.area and run AFAB in repeat. This will reverse the depreciation posted for the area at one go.

Regards,

Mukthar

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello,

Thank you for the suggestion. We will try to follow these steps if it is working.

We are however trying to post to non leading ledger directly using transaction FB50L. Will share the impact with business and proceed as per their suggestions.

Best Regards,

Disha Trivedi.

0

Hi

I do not think FB50L is a right approach at all. Anything which has to be adjusted should start from Asset Accounting with through put impact in GL, else you will create more problems for yourself at year end when asset and GL balances will not match and you will end up doing the same exercise at that time. I would suggest to use either my recommendation or one suggested by Mukhtar. These are the only feasible options for you at this point.

Regards

Sanil Bhandari

0
Bernhard Kirchner
Dec 05, 2016 at 04:01 PM
0

Hi Disha,

error F5 567 is a result of different posting periods in different areas.

I found simular cases where note 2077600 solved the problem.

best regards

Bernhard

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Dec 07, 2016 at 04:38 PM
0

Dear All,

Issue was because of different posting periods for two ledgers.

Note 2289378 resolved our problem.

Best Regards,

Disha

Share
10 |10000 characters needed characters left characters exceeded
Bernhard Kirchner
Dec 20, 2016 at 03:15 PM
0

Hi all, there is also a pilot note: 2006702 - Different fiscal year variants for various ledgers - modification

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Apr 04, 2017 at 10:22 AM
0

Hi Bernhard,

Could you please tell me if you could download 2006702? because i am getting error.

Thanks

Basavaraj

Share
10 |10000 characters needed characters left characters exceeded