Wrong depreciation calculated for base value 04 + EA-FIN activated

Hi,
after activating EA-FIN, depreciation for assets using base value 04 (= half of replacement value) is calculated wrong.
While AW01 for a particular asset shows depreciation values based on the FULL replacement value (like it would be base value 03) AW01_AFAR (the u201Coldu201D asset explorer) shows the correct depreciation for base value 04.
The wrong base value can also be seen using the "display depreciation calculation" button in both transactions.
There are no enhancements for base value determination active.
I didnu2019t find any SAPNET notes nor SCN entries regarding this case, any ideas?
Best regards, Christian

For what it's worth, I did a search and didn't find anything either. 
It sounds like you've already tried this, but if the base value (the actual $$ value) is different in the trace on both tcodes then you have a problem.  I would be sure to recalculate the values when you enter AW01 and AW01_AFAR to ensure that it's correct before looking at the trace.
The formula for the replacement value is: 
( u_ganlc-kansw + u_ganlc-answl +
               u_ganlc-kmafa + u_ganlc-mafav + u_ganlc-zusma +
               u_ganlc-mafam + u_ganlc-mafal +
               u_ganlc-kaufw + u_ganlc-aufwv +
               u_ganlc-aufwp + u_ganlc-aufwl ) / 2 .
I'd look at ANLC for the asset and do the calculation yourself to confirm the value. 
You've probably done all of that so I predict an OSS message in your future !
-nathan

Similar Messages

  • Wrong depreciation calculation for upload assets

    Hi
    I am uploading for US company with FY as Jan to December.
    I have to upload assets with value as on 31stJuly 2010. It means SAP should calculate depreciation from August 2010.
    Depreciation is on life basis
    One asset purchased on 01.11.2009 with Value $ 585.59. WDV as on 31st July is 355.21. Total life is 23months. In AS91, depn start date is 01.11.2009 with useful life as 01 year and 11 period. In expired life, its showing as 94 under period column.
    Now in asset transfer config, i gave the transfer date as 31.07.2010 and last period of depreciation in previous system, i gave it as 7th period of year 2010 (ie. July 2010)
    Now when i saw depreciation in AW01n for august 2010, it shows that remaining depreciation is fully written off in august 2010.
    Its not flowing to next month.
    Any idea why is writing off depreciation fully in next month itself

    Hi..
    After transfer old asset to new asset system automatically transfer all the balance to the new asset including depreciation Up to July
    After that please check in the new asset master in the depreciation area tab depreciation start date...it must be 1st August
    So based on that date depreciation will be calculate 
    I hope you will get some idea based on this suggestions.
    Thanks and Regards
    sudharshana vamsi

  • Depreciation calculation for Indian Tax Depreciation Area - Fixed Assets

    Can any one of you kindly advice how to setup the Multi levels methods and Period controls for Tax Depreciation key in Indian Tax Depreciation area.
    My Leading ledger Fiscal year: Jan u2013 Dec (Year dependend)
    And Non-leading ledger (India) Fiscal year: April u2013 March (Year dependend)
    I was able to post correct depreciation for leading and non-leading ledger Depreciation areas with a stated percentage. But the calculation of Tax depreciation area is incorrect.
    As per client requirement, Tax depreciation area is setup only reporting purpose and no Depreciation posting.
    Required Depreciation Calculation for Tax Depreciation Area:
    For Acquires & Additions,
    Rule1:
    If it is >=180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation as stated percentage. Eg: 10%
    Rule2:
    If it is <180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation of 50% on stated percentage. Eg: Stated percentage is 10%, then it should be 5%.
    Early responses will be appreciated.
    Thanks much for the help.
    Regards,
    Bapu

    Hi JBC,
    please search this Forum, I think basic questions about Indian tax depreciation have been asked dozen of times in this Forum here. You should find some answers in earlier threads.
    Regards,
    Markus

  • Depreciation calculation for Indian Tax Depreciation Area

    Can any one of you kindly advice how to setup the Multi levels methods and Period controls for Tax Depreciation key in Indian Tax Depreciation area.
    My Leading ledger Fiscal year: Jan u2013 Dec (Year dependend)
    And Non-leading ledger (India) Fiscal year: April u2013 March (Year dependend)
    I was able to post correct depreciation for leading and non-leading ledger Depreciation areas with a stated percentage. But the calculation of Tax depreciation area is incorrect.
    As per client requirement, Tax depreciation area is setup only reporting purpose and no Depreciation posting.
    Required Depreciation Calculation for Tax Depreciation Area:
    For Acquires & Additions,
    Rule1:
    If it is >=180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation as stated percentage. Eg: 10%
    Rule2:
    If it is <180 days (as per Non-leading ledger Fiscal year) the system should calculate depreciation of 50% on stated percentage. Eg: Stated percentage is 10%, then it should be 5%.
    Early responses will be appreciated.
    Thanks much for the help.
    Regards,
    JBC

    Hi JBC,
    please search this Forum, I think basic questions about Indian tax depreciation have been asked dozen of times in this Forum here. You should find some answers in earlier threads.
    Regards,
    Markus

  • Wrong calculation in base value while capturing Excise IV(IMPORT)

    Hi all,
    any provision to correct base value while capturing EX IV for <b>imports</b>, in ECC 6.0
    as note was released  by sap for earlier versions.
    will it hold good  for this version also?
    regards
    Krishna

    Hiii Santosh,,
    After applying the Notes still the Excise Values are not captured??
    Please tell if any other Notes to be applied???
    Regards,
    Kumar Rayudu

  • Asset depreciation calculation for prevous year  when legacy data transfere

    Hello,
    Asset Legacy Data transfer has made as on 31.12.2006. so, for the first period asset depreciation calculation has done wrongly  i.e. on the first period of 2007. but it was not noticed at that point of time, now after 2 years, the cumulative difference is coming out very big.
    for 1st period, in Asset Value Tab of AS03,  for period 01 , 2007 when i am checking right now it shows for dep. Area 01 right now that Amt to be post (14.48) instead of that in the next line for Dep. area 20 and in the next line it shows, Amt. to be posted ( -0.28). hence, for next period only differnce amount is posted in G/L side instead of actual it should be posted as 14.76.
    so, now because of this error, my G/L and AA sides are not matching up.
    eventhough i post manual reversal entry via FB01, when i will run ABST2 there will be problem.
    if i run manual unplanned depreciation, then will my problem of not matching of Asset side and GL side will be solved. ?
    also, please provide suggestion from your end in order to solve this issue.
    Thanking you for your help.
    Jigs.

    We cannot post any depreciation to previous fiscal year 2008 as no planned depreciation is envisaged for the previous year 2008. The transfer date for Legacy asset data transfer is maintained as 12/31/2008 and takeover values are uploaded accordingly. Hence, 2009 is a first year for Asset Accounting of the company code.
    However, Depreciation posting program checks for previous period log while executing for the current period. The logs are stored in u201CTABAu201D table. For new company code there will not be any entries in TABA table.
    Due to missing functionality, System is checking for previous year depreciation posting logs even though the current fiscal year is first year for planned depreciation and giving error message AA 687.
    As per SAP Note 144441 this error can be rectified with the help of correction program ZACORR_TABA_ENTRY_CREATE.
    Steps to Rectify the Error:
    1. Copy correction program from SAP Note 144441 into SAP System.
    2. Execute the program with transaction code SA38
    3. Check the values in test mode
    4. If the table is updated with documennt number , remove the test mode tick and execute again
    5. Execute the deprecation
    Edited by: Ramesh Reddy Nalamada on Jul 25, 2009 1:17 AM

  • Pricing - Requirment / calculation type / base value

    Dear Friends,
    Thnaks for the support and guidance provided by you for my previous posts
    In Pricing Procedure we give Requirment, Calculation type and Alternative formula for condition base value, I would like to know where do we exctly define all this?
    Or are they standard? If standards where we can see how they works?
    Regards
    Vishal

    Hi,
    go through the below Examples for better understanding ..
    Example: 1
    Condition Type: PR00
    Requirement 2 Item with Pricing
    Purpose:
    This is an example of a pricing requirement.  This requirement is met if the document item category is relevant for pricing and no previous condition in the pricing procedure has set the condition exclusion flag. This requirement can be assigned to condition types in the pricing procedure to avoid unnecessary accesses to the database when an item is not relevant for pricing or a condition exclusion indicator has been set.
    Example: 2
    Condition Type:  Net value
    Calculation Type: 2 Net value
    Purpose:
    This is an example of a condition value formula.  This type of formula can be used to influence the value shown for the condition in pricing.  A condition value formula is assigned to a condition type or value line in the pricing procedure.
    Formula '2' sets the value equal to net value that has been calculated so far for the item in the pricing procedure.  It contains the amount excluding taxes.
    Example: 3
    Condition Type: R100
        Alt.Condition Base Value: 28 (100% Discount)
    Purpose:
    This is an example of a condition base value formula.  A condition base value formula can be used to influence the basis the system uses when computing a pricing value.  A condition base formula is assigned to a condition type in the pricing procedure.
    Formula '28' sets the rate of the condition to a 100% discount.  This formula was delivered with condition type R100 to support free goods functionality.
    Reward if it is useful,
    Chandramohan

  • Wrong tax calculation for minimum sales order scenario

    Hi all! We are trying to use minimum sales order value for our sales order processing in CRM. The sales order value and the calculated tax looks fine when the sales order is created. Eg.
    Quantity = 10
    PR00   $4 each    Total value of $40
    AMIW  $50
    AMIZ   $10
    MWST $6.25 (tax of 12.5%)
    When we create the billing document in CRM, the net value is shown as $50. However, when we look at the Conditions, the tax is calculated based on a tax base value of $100 and hence ended up with $12.50.
    Quantity = 10
    PR00   $4 each    Total value of $40
    AMIW  $50
    AMIZ   $10
    0TTE   $0
    MWST $12.5 (tax of 12.5%)
    Does anyone know what I might have missed out that would cause this problem?
    Any comments would be very much appreciated.
    Cheers!
    SF

    Hi Devi,
    If you want to do the billing in CRM, then you need to use the billing pricing procedure in CRM. Below is the list of the configurations I usually do:
    1. Create new transaction type if needed
    2. Create new item catagory if needed
    3. Assign item category to transaction type if 1&2 is created
    4. Create new document pricing procedure
    5. Assign pricing procedure to sales organisation and new document pricing procedure
    6. Create new billing type if required
    7. Creat new billing category if required
    8. Assign billing item category
    9. Assign revenue account for sales transactions
    10. Assign accounting document type to billing type
    11. Create new sales order type in R3 if 1 is done
    12. Create new item category in R3 if 1 is done
    13. Make sure that item category is assigned to the new sales order type in R3
    14. Create delivery item category in R3. This has to be the same item category as that in the sales order as the system copies the item category of the sales item into the delivery.
    Hope that helps.
    Regards
    SF

  • Condition Records not to be calculated if base value is negative

    Dear all
    I have configured a pricing procedure which is being used while performing DP90 with reference to service order. Now the values are getting populated in condition type EK02 and based on this value various other charges like service tax, supervision charges are getting calculated.(condition records have been maintained for condition types related to these charges). Is it possible that these charges do not get calculated if the value in EK02 is negative?????

    You can create a routine where you can put the check. And assign it to pricing procedure for all the condition types you don't want negative value for.
    Thanks

  • How to skip depreciation Calculation for one year

    Hi Experts
    I got requirement from One of My Client.
    Scenario:
    Fixed Asset Value: 100000
    Useful life: 10 years
    Per year depreciation: 10000
    Asset Purchase date: 01.04.2014
    Depreciation posted up to: 31.03.2015
    Depreciation not required from date: 01.04.2015 to 31.03.2016
    Again Depreciation Start date: 01.04.2016 based on life of the asset.
    Question: As per above information From period 01.04.2015 to 31.03.2015 not required any depreciation posting for this we assigned Asset shutdown in asset master data. if deselect the asset shut down check box again it considering for depreciation.
    As per my scenario we don't want whole one year depreciation.
    Regards
    Madhan Mohan

    Hi
    you should to add two interval in the asset master data under shut down tab " on main asset No. only "
    the first interval in start form 01.04.2015 and click on shutdown box beside this interval.
    and create another one from 01-04-2016 and remove he asset tick on shut down to allow the asset to operates again after the shutdown period elapsed ..
    Regards
    Mahmoud EL Nady

  • Unplanned Depreciation not reducing Base Value

    Hi all,
    Assets created in SAP. At a point, these assets had stopped
    depreciating in sub-ledger but seems as if depreciation continued to be
    provided for directly in the GL manually (via a jnl).
    User wishes to re-capture the revised APC and Accumulated Depreciation
    values back into the asset sub-ledger so that SAP will automatically
    depreciate the assets according to their remaining useful life.
    User has used a Write-up transaction to load the APC value. After
    write-up posted, depreciation ise being calculated as expected. To get
    the Accumulated Depreciation value into SAP, the user has posted
    Unplanned Depreciation (TTY Type 640). However, when this is posted,
    depreciation is not being calculated evenly over remaining useful life
    of asset. For Year 1, depreciation is being calculated from Write-Up
    (APC) values ONLY, and the Unplanned Depr (representing Accumulated
    Depr) has NOT been taken into account. Unplanned Depr is only taken
    into account from Year 2. This is leading to dis-proportionate depr
    values in comparison from Year 1 to subsequent years across the
    remaining life of the asset.
    Have been testing period controls, and depr key set up but no luck.
    Any ideas or suggestions will be much appreciated.

    Dear Dattatray,
    The issue here is not with the fact that no depreciation values have posted.  The issue is with the values that have been posted.  Let me illustrate by way of example.
    Asset start date for depr:  Changed to 01.01.2008
    Useful life of asset:  3 years, 4 months (40 months)
    Write up of asset posted March 2008:  EUR 135,492.18
    Unplanned Depr of asset posted March 2008 EUR 93,605.12
    Therefore, Net Book Value = EUR 41,887.06
    Depreciation run happened in March after ABAA entry.
    Expectation:-
    Based on this NBV of EUR 41,887.06 you would expect depr to post at EUR1,047.18 per month (41,887.06 / 40 months) over the remaining life of asset.  In this case, 3 months would be caught up in March as asset depr start date is 01.01.2008, and balance of EUR1,047.18 to be posted per month until asset written off 3 years and 4 months down the line.
    What is happening in SAP:-
    Depreciation for FY 2008 is only being calculated on the write-up value of EUR 135,492.18 and not the NBV.  Therefore, for FY2008, depreciation is being calculated at EUR 3,387.30 per month (EUR135,492.18 / 40 months).
    If i look at FY2009, the Unplanned Depr value of EUR 93,605.12 is now taken into account.  Therefore, NBV at start of FY2009 is Write up 135,492.18 less Unplanned Depr 93,605.12 less Depr in 2008 (12 months) 40,647.60 = NBV EUR1,239.46.  This new NBV over remaining life which is now 28 months is EUR 44,27 per month, or EUR 531.19 for the year.
    So in FY2008, Depr posted = EUR 40,647.60 (3,387.30 per month)
    In FY2009, depr posted = EUR 531.19 (44.27 per month)
    In FY 2010, depr posted = EUR 531.19 (44.27 per month)
    In FY 2011, asset gets written off.
    You can see that year 1 is highly inflated and Years 2 thru remaining life is smoothed.  This is not correct.  We would expect the depr to be smoothed every month from the start i.e. EUR 1,047.18 per month or 12,566.11 in FY2008, 12,566.11 in FY2009, 12,566.11 in FY 2010 and then written off in 2011.
    I hope this helps to explain the current problem.
    Thanks.

  • Tax Depreciation Calculation for Malaysia

    Hi Guys,
    We have a requirement to calculate Tax Depreciation for Malaysia with reference to the Capital Allowance.The scenario is like this:
    For Asset Class say Office Equipments Initial Allowance is 20% and Annual Allowance is 10%
    That means depreciation will be calculated @20% on the acquisition value immediately upon acquisition for one time. Again depreciation @10% per annum will be calculated on the acquisition value for the entire useful life of the asset from the date of acquisition.
    Example: Asset is capitalised at MYR 10,000 on 1.1.2010
    First Initial Depreciation would be: 20% on 10000= 2000
    Annual Depreciation for 2010 would be : 10% on 10000= 1000  and this will be same for next 8 years.
    Depreciation Method is SLM
    In this case changeover should happen within the year.
    Can you please suggest how to create a depreciation key in SAP for this.
    Early respponse would be appreciated.
    Regards,
    Chandra

    Hi Chandra,
    Have you found the solution for this scenario?
    Thanks

  • Pricing Procedure calculation for Net value

    Hi Gurus,
    I have  issue with pricing procedure for net price.
    My pricing procedure is as follows.
    Step    Cond.type       from    to      Subtotal        req.type        cal.type        Basetype
    10      CPLF    0       0               0       0       0
    20      CA              0       0               0       0       0
    30      CPY             0       0               0       0       0
    40      CWE             0       0               0       0       0
    50      CPY1    30      40              0                           601 0
    60      PCP             0       0               0       0       0
    70      NCC            50       60              0       0       0       0
    80      Subtotal 1      70                      1
    90      VC              0       0               0       0       0
    110     FPA             0       0               0                          600  0
    150     INCR    0       0               0       0       0
    160     BINC    0       0               0       0       0
    170     PINC            0       0               0       0       0
    180     CINC            0       0               0                           602 0
    190     PRIN    0       0               0       0       0
    200     FINC
    210     Subtotal 2      200                    2        0       0
    220     ADT             0       0               0       0       0
    230     FTAX    0       0       0                                           603 0
    240     Subtotal 3      210                     3       0       0
    My query is when i am doing pricing for line items
    1) For line item 1 net value of the item will be subtotal 1
    2) For line item 2 Net value should be through condition type calculation.
    3) For line item 3 net value should be through calculation of routine
    4) For line item 4 net value should be Subtotal 2
    5) For line item 5 net value should be Subtotal 3
    So please tell me who to do?
    regards
    Srinivas

    Hi,
    Can you please explain what type of pricing you want to for your sales order.
    I am confused with your line items.
    Can you explain what kind lines item you are entering in your sales order.
    Are they proper material for which you have maintained condition record in MM01.
    Because for all the line item system will calculate price by the pricing procedure which you have shown.
    So in short system will calculate different price for different line item.
    After calculating the whole price it will make the total of net amount of all the line item.
    And that net amount will be shown in the header data of the sales order.
    Regards
    Raj.

  • Wrong taxes calculated for KY0D

    We have tax area KY0D (Metro Louisville/Jefferson County) set up for tax type 51 & 53 for residence tax and 50 & 51 for work tax.  If the associate only works a percentage of the time in KY0D (say 65%), taxes are calculated correctly for all tax types when payroll is run. 
    Now say the associate works the other 35% of the time in a tax area that also has tax type 51. When payroll is run, the taxable earnings for tax type 51 for KY0D are 65% of 65% of the total earnings.  This is incorrect.
    Does anybody have any idea why this is happening?  It only happens if the associate has that second tax area that also has tax type 51.
    Any help is appreciated.
    Thank you!
    Mary

    Hai,
    As per your condition type - Calculation type their is no restriction for line items in general.
    In case if you want to include the value (fixed or calculated) has to go only for line item 10,
    1. create a access sequence with line item (POSNR)
    2. Attach the sequence for the conditon type
    3. By maintaining condition record it will allow the taxes only for the first line item.
    Regards,
    Mani

  • Why does Airport Admin Utility show wrong IP address for base station?

    After setting up my new MacBook Pro (and apparently updating Airport Extreme firmware in the process) running OS X 10.4.5, whenever I try to access the base station (IP 10.0.1.1) from my PowerBook G# (Firewire) running OS X 20.2.8, Admin shows 254.128.0.0. I cannot access the configuration windows, getting an error message "An error occured while reading the configuration."
    I am also currently unable to pringt from the Powerbook and an iBook (also running OS X 10.2.8).

    I just tried the hard reset, and nothing has changed. I had to rename the base station and network, and change the passwords, but I still see the wrong IP from the PowerBook, and I still can print only from the MacBook Pro, where I also see the correct IP address for the AEBS.

Maybe you are looking for