We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-acct] Depreciation Needs To Catchup Excess Values Of April And May Months In The Month Of June

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from ranik on Apr 20 at 1:14 AM
Thanks a lot Jack.
But my business is not willing to do the transfer of existing asset to new assets. It's a huge volume os assets; it's not a one or two assets. All the company codes they need this solution.
Thanks and Regards,
rani K

---------------Original Message---------------
From: Ranik
Sent: Monday, April 18, 2016 8:56 AM
Subject: Depreciation Needs To Catchup Excess Values Of April And May Months In The Month Of June

Hi Friends,

My Business required to change the depreciation key from SOY method to Straight line useful life method. Which is applicable from June 1st 2016(In Q2).

The depreciation key change need to adjust overall Q2'16 depreciation
costs, so no matter when it will be implemented or still in April or
June it still need to set whole quarter value to STR.
so even if we put in production this methodology in June, when April
and May were calculated and booked per current way of working
in June catch up for this 2 months need to be calculated.

Means if we implement on June then it should be catch up the April and
May month difference value in June month 2016. And it should not catch
up the 1st to 3rd Month 2016 (Q1)excess values.
Please check and provide me the solution for the above query.
Thanks in Advance.
Rani

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
© 2016 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
ranik  
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language