Depreciation percentage rate

Dear Forum,
in afams (multilevel method), there is a column called percent which is depreciation percentage rate.
I would like to know this percentage is percentage value of base value or it is the depreciation value?
Say I have asset costed at 10,000.00 and for the first 4 year, the percentage is 5% each year.
This 5% or 500 is a base value or 500 as the depreciation value?
thanks

Hi Srina,
Have a look at the documenation in the F1 Help of this field AFPROZ in AFAMAS.
However, if you have APC of 10,000.00 and a percentage rate of 5% in AFAMAS, and lets say Base value is 24 (Netbook value), useful life 4 years: then the calculation is as follows:
1st year:  APC 10,000.00       -> 5% = 500  depreciation in 1st year
2nd year: NBV now 9,000.00  -> 5% = 475  depreciation in 2nd year
3rd year:  NBV now 9,025.00  -> 5% = 451.25  depreciation in 3rd year
4th year:  NBV now 8.574,00  -> 5%  = 429,00 depreciation in 4th year
If you want to fully depreciate your asset then you would need to create another phase obviously. Else, in my example here, the asset will have remaining NBV after the 4 years but no more depreciation will be calculated.
I hope this example helps to understand better field AFPROZ in AFAMAS.
Kind regards,
Brigitte

Similar Messages

  • How to Include VAT percentage rate in the Invoice Print Output

    Hi All,
    I have a question here. My client wants the VAT rate in percentage form to appear in the invoice print output. But, I have no idea where to pull out the vat percentage rate from or which table I should refer to.
    Appreaciate all of your inputs.
    Thanks a lot!

    Hello,
    You can fetch the VAT rate either from the Sales order or the Billing document
    Getting it from Billing document is more relevant.
    First goto the Table  VBRK and get the KNUMV  field from the vbrk
    Then goto KONV table which is the pricing table for conditions and give the input values as the KNUMV and KSCHL
    KNUMV  is the DOCUMENT CONDITION which is independent for each document
    KSCHL is the condition type ( in this case it is your VAT condition type )
    You can get the Rate from the  the field  KBETR.
    KBETR is the RATE % of the KSCHL in KONV
    Hope it is clear.
    Regards,
    santosh

  • Which table stores the Tax percentage rate of commercial invoice?

    Which data base table stores the tax percentage rate of the items in a commercial invoice? Or which FM can return the tax percentage rate?

    HI,
    Don't post the duplicate threads for same requirement...it against to the SCN rules. Moderator can delete this thread.
    Report to Moderator!!!

  • Update decimal places in sales and use tax percentage rate [FTXP]

    i need to update the decimal places in the tax percentage rate.  i've gone through all of the tax configuration in the img several times and it is not there.  have searched the internet for an answer to this, and am not finding it. need to update from four digits to the right of the decimal to five digits to the right of the decimal point.
    for example, adjusting a tax rate field of 5.1234 to 5.12345, where the field will allow 5 digits.

    Hi,
    SAP has hardcoded in the program MF82TI00 to pick only the three places after decimal. Rest will be ignored.
    In case this is your legal requirement, I will suggest to rather create an OSS message with SAP.
    Regards,
    Gaurav

  • VK154 - Tax indicator T1 has percentage rate

    Dear Friends,
    1. While doing FV11, error messages "Tax indicator T1 has percentage rate- 2.000 "(VK154) is triggered.
    Can someone help me to change this to Warning.
    2. How can i get the FTXP into change mode in Production client(which object shall i make use of to make it to change ?)
    Thanks
    Ivy

    Hi,
    If a tax code alreday maintaioned with tax condition types with tax rate--why you are chnaing tax rate now for that tax code as system may have tranactions data for that tax code with fixed tax rate!!!
    Now as you want new tax rate with  tax condition types, better create a new tax code and maintaion (FV11)the  tax rate with tax condition types. Now go for new PO creation and goods receipt.
    Yes, there is a option to change tax rate in t.code:FV12 for tax code with condition type,but check the nature of Access sequence is JTAX. Is your Access sequence JTAX  well defind with condition keys.....ie..... where Access sequence JTAX  have Validity Period in it.If Access sequence JTAX  is a copy of Access sequence JST1,then you can maintaion to change tax rate with validity period.
    NOTE:
    Validity Period available for tax condition types which have access sequence JST1 not access sequence MWST
    Regards,
    Biju K

  • Percentage rate settlement and amount settlement

    What is the difference between percentage rate settlement and amount settlement and how does this impact settling orders?

    Order cost will be settled to some settlement receivers.
    1. If you maintain Percentage, based on the percentage entry, cost will be distributed among different receivers.
    2. If you maintain Amount, directly amount can be entered & will be settled.
    For example, order cost is 1000 & settlement receivers are 4 different cost centers. We have cost center as CC1, CC2, CC3 & CC4.
    Settlement % for each cost center as follows:
    CC1 -> 20%
    CC2 -> 10%
    CC3 -> 35%
    CC4 -> 35%
    Then cost will be calculated accordingly, settlement will happen.
    Also you can enter amount against each cost center.

  • Settlement percentage rate of a rework order

    Hi
        Is there any Tcode to check the total settlement percentage rate related to the rework order rasied.
    regards,
    PradeepM.

    Hi Pradeep,
    1 )  In  CO02 / CO03   from the Menu  Drill down from the Header -
    > click on settlement rule over view there you will find settlement %
    2 )  Enter table " COBRB "  input object number Prefix OB00**********   to get 14 digit and Plant you fill find list of orders having
          settlement %
    3)  Use Transaction KOB1
    Regards,
    JayaVimal

  • Depreciation percentage

    Dear All,
    Please let me know the t-code to change the Depreciation percentage maintain agst the Depreciation Key.

    AFAMA Maintain Depreciation Key
    AFAMS Define Multi-Level Methods

  • Condition percentage rate

    hi,
    may i know e1edp05-kperc can be mapped to which component in bapicond?
    thanks
    rgds

    Hi
    Based on the The field CALCTYPCON type (H or I  means Percentage) the field
    CONBASEVAL will hold the values.
    see the reference
    KONV table which stores the same type of values
    based on the field KRECH the value KAWRT is maintained
    Regards
    Anji

  • Regarding percentage methods

    hi all
    my client is indian based i need clarificafication regarding calculation of
    percentages on different assets like buildings, plants,machinaries,and furniture,computers.
       my question is :is there any pre defined percentages for these assets to calculate depreciation,on what basis we calculate that means tax,p&l,balnsheet
    pls clarify my query
    regards
    chandra.

    Hello
    Multi-Level Method
    Use
    Base methods for certain depreciation calculation methods (Stated percentage and Total percentage in concessionary period) use either a total percentage rate or a periodic percentage rate to calculate depreciation. You can divide these calculation keys into as many levels as you like. A level, in this sense, represents the period of validity of a certain percentage rate. This percentage rate is then replaced by the next percentage rate when its period of validity has expired.
    Features
    Period of Validity for the Individual Levels
    You determine the validity period for the individual levels of a key by specifying the length of time in years and months. You can choose whether the defined validity period begins with
    The capitalization date
    The start date for ordinary or tax depreciation
    The original acquisition date of the asset under construction
    The changeover year
    The defined time periods of a key always have a common start date. This means that the period from the start of one key to its end will overlap with the next period, which has the same start date but a longer validity period. Therefore, you have to enter the validity periods for the levels in cumulative form.
    There is a special indicator you can use when you work with non-calendar fiscal years. The indicator allows you to specify that the definition of the levels applies to the fiscal year and not to the calendar year. However, be aware of the considerations involved when using shortened fiscal years (see Shortened Fiscal Years ).
    Depreciation Percentage Rates
    How you enter the depreciation percentage rate is dependent on the depreciation calculation method being used:
    When using the Total percentage in concessionary period depreciation calculation method, you also have to enter the depreciation percentage rate in cumulative form (see example).
    When using the Stated percentage depreciation calculation method, you do not enter the percentage rate in cumulative form.
    The following example shows the definition of five levels, each one of which should last for a year. The Total percentage in concessionary period depreciation calculation method is being used. The depreciation percentage rates in the individual years are 60, 10, 10, 10, and 10%.
    Validity period
    Percentage
    1 year
    60
    2 years
    70
    3 years
    80
    4 years
    90
    5 years
    100
    In addition, you can limit the levels according to specific acquisition years. This enables you, for example, to observe certain legal requirements that place time restrictions.
    Suresh

  • Problem with computation of depreciation

    Hi SDN forumers,
    We have a concern regarding the computation of the depreciation to be posted next month. Here is the scenario.
    We capitalized an asset last October 2008 with depreciation start date 10/01/2008. We processed the depreciation run for the month of October 2008 and at this point, the depreciation posted was correct based on October's Net Book Value. Come November 2008, we made some asset adjustments via F-90 (asset acquisition) which would increase the asset's net book value and at the same time adjust the depreciation per month.
    I noticed though that the depreciation to be posted for November 2008 includes that of the unposted depreciation from October 2008 (due to the increase in Net Book Value in November). This means that the depreciation to be posted for November 2008 is significantly higher than that of December 2008. What I was expecting was that (NBV + Additions / remaining life = depreciation) and that the amount to be posted would be equal every month after the acquisition.
    Is there a way we can adjust how the system computes depreciation? Thanks and best regards to each and everyone of you.

    >
    Markus Bredel wrote:
    > Hi Patrick,
    >
    > in this case you have to check your depreciation key, I would recommend to check the documentation in the SAP Help Portal concerning keyword "depreciaiton methods". I propose to use a depreciation key which depreciates according to method "net book value over remaining useful life". I think you should consider this option and test it out.
    >
    > Regards,
    > Markus
    HI Markus,
    Thanks for your continous help. I checked our existing depreciation key being used and at the same time checked "Depreciation Methods" in the SAP Help Portal. The SAP Help Portal suggested the following:
    Straight-Line from the Book Value over Remaining Useful Life
    +Use+
    The book value of the fixed asset is distributed in uniform amounts over the remaining life. However, unlike straight-line depreciation over the total useful life, this method ensures that post-capitalization and subsequent acquisitions do not lead to an extension of expected useful life. Post-capitalization or subsequent acquisitions after the expiration of the specified expected useful life do, however, cause problems in this depreciation method. In such cases, the changeover key in the depreciation key used has to provide for another method after the expiration of the expected useful life.
    +Calculation :+
    Depreciation = net book value / remaining life
    APC: 1000
    Useful life: 10
    Net book value: 500
    Remaining useful life: 5
    Depreciation = 500 / 5 = 100
    You can represent this depreciation method in the system, for example, with a depreciation key that calculates a depreciation percentage rate from the remaining life, due to the depreciation calculation method Percentage from the useful life being set in its base method, and the Rem. life indicator being set in the multi-level method. Furthermore, the base value indicator "24" in the multi-level method ensures that the net book value is the basis for depreciation. The net book value and the remaining life are related proportionally, which results in straight-line depreciation. In the event of acquisitions after the expiration of the expected useful life, the depreciation key switches to a new phase after the planned end of useful life. The new phase is set up for straight-line/remaining life/pro rata/to zero/to end of life. As a result, these subsequent acquisitions are also depreciated completely.
    I checked our depreciation keys and the settings are the ff:
    Base Method: Percentage from the useful life
    Multi-Level Method: 001
                                 Remaining Life indicator? Yes
                                 Base Value indicator: 24
    The following settings follow that of the suggestion in the SAP Help Portal. Anything wrong with my settings? Thanks a lot for your help.

  • Incorrect posting in asset accounting after legacy asset transfer

    I have an issue in Asset accounting.
    The depreciation key used is LINA (with a base method 0009 and Dec. bal. method – 001 straight line depreciation)
    My question is:
    An asset was acquired 02/01/2005. It has an expected useful life of 1/11.
    Under AS93.
    I see the asset  ***. acquisition value 205,695.00
    Accu.ord. deprec  - 78,784.06
    The asset was transferred to SAP  at 03/31/2007.
    Now In aw01n  I see the following:
    Legacy data transfer Per – 3 Ord. deprec – 10,143.87
    Posted Per – 4 – 13,364.13
    Posted 5 – 5877.00
    Posted 6. 5877
    Till 8th month posted 5877.
    The posted values are wrong. Since it was transferred to SAP it has a useful life
    of 1 year. At this rate it will go for 3 years.
    What can I do to rectify this error?
    Why is it posting 5877?
    Thanks,

    Hi Roma,
                 The useful life has to be the Total Useful life of the asset.
    Since your useful life is less than the expired usefull life the system is calculating depr. for after the end of useful life, which for base method 0009 is curbing.
    <i>Curb
    With depreciation beyond the planned useful life, the depreciation percentage rate can be derived, not only from the planned useful life, but also from the actual useful life. This method produces a declining-balance effect instead of a straight-line effect (curb).
    Use Base Method 0007, this does not curb.
    Kind regards
    An asset that originally had a useful life of 10 years is depreciated in year 11 by 1/11 = 9.09 %, in year 12 by 8.33 % and in year n with 100/n %.
    When you use below-zero depreciation with a curb, the system determines the percentage rate, after the end of planned life, to the exact period and not to the year.</i>

  • Sum of the year digit method and declining balance method

    Hi,
    My Client want Deprecation methods Sum of the year digit and declining balance method for tax purpose. This requirement for Colombia Country.
    Which Deprecation Area I activate and how will configure above two methods.
    Regards
    Venki

    Sum-of-the-Years-Digits Method of Depreciation
    Use
    For each year of the expected useful life, the system notes the remaining useful life for the assets and totals the figures in each year. In each fiscal year, the remaining life is divided by this total in order to calculate the depreciation percentage rate for that fiscal year. This method leads to depreciation amounts that are reduced progressively by the same amount each period.
    Since the remaining useful life is no longer defined after the end of the planned useful life, this depreciation method does not allow for depreciation after the end of the planned life. However, you can change to another method after the expected useful life has expired.
    Acquisitions after the depreciation start year or post-capitalization will necessarily lead to a positive net book value at the end of planned life. For this reason, such transactions are not allowed when using the sum-of-the-years-digits method of depreciation. With this method, you have to handle subsequent acquisitions by creating sub-numbers. It is also a requirement that the acquisition year is the same as the depreciation start year.
    Calculation :
    Depreciation = APC * remaining useful life (current period) / total of remaining useful life (over entire useful life)
    APC: 1000
    useful life: 4
    Total remaining useful life: 10 (= 4 + 3 +2 +1)
    Depreciation 1st year = 1000 * 4 / 10 = 400
    Depreciation 2nd year = 1000 * 3 / 10 = 300
    Depreciation 3rd year = 1000 * 2 / 10 = 200
    Depreciation 4th year = 1000 * 1 / 10 = 100
    Declining-Balance Method of Depreciation
    Use
    For the declining-balance method of depreciation, the fixed asset is depreciated by a progressively falling rate. A constant percentage rate is calculated from the expected useful life and a given multiplication factor. This is multiplied with the falling net book value of the fixed asset. For mathematical reasons, the net book value will never reach zero using this method. You change over to straight-line or complete depreciation under these conditions:
    Declining-balance depreciation < straight-line depreciation
    Net book value < x percent of acquisition value
    Net book value < fixed amount
    Net book value < straight-line depreciation
    The changeover method is specified in the internal calculation key.
    Calculation :
    Depreciation = net book value * percentage rate from expected useful life and factor
    APC: 1000
    Exp. useful life: 10
    Net book value: 700
    Multiplication factor: 3
    Depreciation = 700 * (100% / 10 * 3) = 210
    OR You can use following link
    http://help.sap.com/saphelp_45b/helpdata/en/4f/71de3b448011d189f00000e81ddfac/frameset.htm
    http://help.sap.com/saphelp_45b/helpdata/en/4f/71de3b448011d189f00000e81ddfac/frameset.htm
    Regards,
    ANJIREDDY
    Edited by: ANJIREDDYA on May 8, 2010 12:09 PM
    Edited by: ANJIREDDYA on May 8, 2010 12:10 PM

  • Base Method 004 - Ordinary: Decl balance over total life (Japan)

    Dear Forum,
    Could any one help in explianing what is the logic behind Base Method 004 Ordinary: Decl balance over total life Japan.
    We notice in one of the Depreciation Keys, this method has been used.
    Thanks for help.
    Regards

    Hi,
    This is the combination of declining balance (written down balance) and useful life method.
    For eg.
    APC: 1000,  Scrap value: 10% and Useful life: 10 years
    Depreciation percentage rate will be
    1 - ((1000/10000) whole power 1/10 ) = 20 %
    Best Regards,
    Madhu

  • What is difference between asset smoothin , catch up and curb?

    Hi all
    Cuold u pls help me regarding this Asset smoothing, catch up and curb?
    Thanks in advance
    reg
    vishnu

    Hi
    With the smoothing method, the annual depreciation amount determined is distributed equally over the periods from the current posting period to the year end.
    With the catch-up method, depreciation due on a transaction within the fiscal year (from the depreciation start date, according to period control, up to the current period) is posted in one total. The depreciation posting program posts this amount in the period in which the posting date of the acquisition lies.
    With depreciation beyond the planned useful life, the depreciation percentage rate can be derived, not only from the planned useful life, but also from the actual useful life. This method produces a declining-balance effect instead of a straight-line effect (curb).
    An asset that originally had a useful life of 10 years is depreciated in year 11 by 1/11 = 9.09 %, in year 12 by 8.33 % and in year n with 100/n %.
    When you use below-zero depreciation with a curb, the system determines the percentage rate, after the end of planned life, to the exact period and not to the year

Maybe you are looking for

  • Fax not detected,C​omm error, fax run test is all PASS,

    Hi Good Day! Im Using a HP color Laserjet Pro MFP M177fw. The Problem is sending fax messages. I do all the updates you need to installed. but the problem with my hp fax machine is still there specially i still receive a fax not detected issue,comm.e

  • Security of online payments

    Can I key in amounts from an on-screen keyboard when paying bills online to make the payment more secure? If so how, please? Janet

  • Two accounting document during PGI

    Hi, We are facing the following issue: At the time of creation of delivery, there are two accounting documents are getting generated in the system & following accounting entries are getting generated: 1. COGS   a/c   Dr.     To Finished Goods 2. Fini

  • Want to upgrade 9i to 10g without downtime

    Hi Experts I have a 9i database which is running our ecommerce database it is a database which is running smoothly now , however i need to update it to 10g database as all our other databases are in 10g , is there a way without downtime i can achieve

  • Modeler start iwth IE7

    Hi, experts, after updating my Internet Explorer to IE7 I can't start the Modeler ( Transaktio RSPLAN -> Modeler). The error-message is :   Application error occurred during request processing.   Details:   com.sap.tc.webdynpro.services.exceptions.WD