Calculation of Depreciation on pro rata basis

Hi,
i had posted aquistion of asset on 1.1.2008. and a subsquent asset aquisition on 1.4.2008 the system is calculation depreciation for the new aquisition from 1.4.2008 but the depreciation calculated is for the full year i.e. the date of original capitalization of the asset.
Can any one suggest a solution so that the system calculates the depreciation from 1.4.2008 and not from 1.1.2008.
Thanks & Regards,
Praveen.

Hi Ramesh,
i did try the period control, this only controls the start date for calculation of depreciation. The system calculates depreciation from the date of original capitalization date  and not the susequent acquisitions date, and it posts from the start date mentioned in period control.
Regards,
Praveen.

Similar Messages

  • Calculation of depreciation value

    I have to calculate depreciation on an asset on a prorata basis and then on rate of 20% over the next five years. I have config a depreciation key for the same for which the config is:
    1. Multi Lev Method - is from the capitalization date and teh rate maintained inlevels is 20%
    2. Base Method - Specified Ordinary Depreciation and stated percentage
    The system is correctly calculating the pro rata dep in acq year and the following years on pro rata basis except for the last year in which it is not calculating the value as required. The system is showing the value on a pro rata basis whereas in the last year also it should reduce the entire value. The asset acquisition value is Rs 500000 and the date of acquisition is 21.11.2006.
    Regards
    Sanil Bhandari

    Sanil.
    In multi level method, in base value field give 24 (net book balue) and not 1.
    Full points if you are ok.
    Thanks,
    Sujai C

  • Calculation of depreciation and interest for a particular asset class

    Hi,
    I have a problem with the calculation of depreciation and interest for a particular asset class. The assets are financial leases. The depreciation key defined is LEAS. The following are the attributes of this key:
    Dep/int             phase     base met dec-bal prd cont mult lvl chn ov
    Ord.depreciation     1     0011     001     006     001        5
    Ord.depreciation     2     0002     001     003     003
    Interest             1     0028     001     003     010
    An example of an asset is:
    Aquisition value: 1041552.71 (as migrated on 01.04.2007)
    Ordinary dep already posted: 56243.88
    Net book value: 985308.83
    Scrap Value:729086.90
    Useful life: 50 years
    Expired useful life: 9 years 1 month
    Remaining useful life: 40 years 11 months.
    Depreciation start date: 28.03.1998
    Interest calculation start date:30.03.1997
    Depreciation calculated by the system:6261.83
    Interest calculated in the year:15682.68
    I'm not able to undersatnd on what basis the system calculated the interest. I will be thankful if anyone can help me resolve this. An early reply will be greatly appreciated as I'm facing major problems due to this issue.

    Hi Mahesh,
    As per my analysis of the case the interest rates are as under
    Acq. Year                                                    Int.Percent
    9999     4          01     10.%
    9999     7          01     5.%
    9999     25          01     2.5%
    9999     999     12     01     2.5%
    As per this the Acquisition value less the Scrap Value Rs.312,465.00 @ 2.5% p.a will be Rs. 7811.64.
    Based on the above you analyse for which period interest is calculated.
    Hope it will help.
    Regards,
    Vijay

  • Calculation of Depreciation based on Remianing Useful Life

    Hi
    I have a scenario in which depreciation percentage should be derived based on remaining useful life and it should remain same through out the remaining useful life.
    For eg,
    Take over date = 30.11.2010
    Acquisition Date= 01.04.2009
    Acquisition Amount = INR 200000
    Depreciation Till 30.11.2010 = 70000 INR
    Net Book Value as of 30.11.2010 = INR 130000
    Total Useful Life = 4 Years or 48 months
    Expired Useful Life = 1 year 9 months or 21 months
    Remaining useful life = 27 months
    Required Depreciation Per Month = 130000/27=4815
    Derived Percentage = 4815/130000*100=3.71%
    I have created a Base Method for calculation for Depreciation with Depreciation Method as "% from Remaining Life calculated from Depreciation Conversion Date". In Multilevel methods, I have assigned the Base Method as 24, Net Book Value
    and maintained the check box for Remaining useful life.
    However, the system is not calculating the  rate as expected.
    Regards
    Sanil Bhandari

    Hi Sanil
    Have you done any settings in OAYF - recalculate dep for previous years (IMG> AA > Asset Data Transfer > Parameters for Data Transfer > Options)
    For current year, it always does produce some difference due to rounding off, which should not be a big amount
    Ajay M

  • Quota Generation not happen's on Pro data basis .

    Dear experts,
    Time evalution status - 1.
    1.Employee service 0 - 5 years - 24 Days entitlement
    2.Employee service 5 - 10 years  - 29 days  entitlement.
    when generating quota for employee less than five years its calculating correctly.when come's  to employee more than 5 years its not calculating on pro-data basis of employee joining month. Instead of Month it's looking at the year and calculating it.
    DOJ of employee
    Mar-09
    Year
    TOTAL quota accrued
    2009
    20
    2010
    24
    2011
    24
    2012
    24
    2013
    24
    Client requirement
    System calculation as of now
    2014
    28
    29
    Calculation part.
    below screen shot show how system calculating and how client needed.
    how this  scenario can be configured.
    Regards
    Vinodh

    Check the Deduction rule for that Quota
    once check the Groupings for ESG and PSA
    V_001P_ALL
    V_503_ALL

  • Pro Rata calc. based on monthly period of 30 days every period

    PY - NL:
    Hi,
    I want to create a pro rata calculation based on a 30 days calendar. So every month has 30 working days. I know that table T510H offers posibillities combined with operation KDIVP, ADIVP and SDIVP. Can I use the above mentione operations instead of operation TSSOLL or does SAP not support this at all?
    How must I use it and what effect will it have, If a WPBP split accurse on 28th of February or 31th of January ?
    Can anyone help me?
    PS: I know it will also effect the time part of customizing.

    Did u checked the Processing Classs 10  and Specification 1
    for Prorata caluculation
    and also check the Sub rules  XPPF thru PE02  take the hlep of F1
    Prorate will happen automatically if u set the PCL  10  specification 1 
    Check and let us know ur feed back

  • How do I add a negative to a calculation in Acrobat 10 Pro?

    How do I add a negative to a calculation in Acrobat 10 Pro?
    I am using Acrobat 10 Pro in Windows 7.
    I have a form with columns of numbers (Millions, Thousands, hundreds) that I concatenate and then perform simple calculations on (addition, subtraction, division, etc).
    I have a new section of the form that has a column for a negative sign. The calculation is simple addition but it is possible for the numbers to be negative as symbolized by the minus sign in the negative column:
    Line 23 adds lines 20 + 21 + 22 and displays the sum. If any of lines 20-22 have the minus sign in the Neg column, I need the calculation to see that and add the negative number, essentially subtracting it.
    NOTE: the neg column is so formatted that the only possible entries are null and "-"
    So, I see two ways to go, one is a script for each line that looks at the neg column and if the "-" is present, makes the entry a negative number. I have not had much luck with this.
    The other path is to do this all in the calculation in line 23. I have fiddled around with some "if" statements but no joy yet.
    NOTE: If it makes it easier, I could change the column input to a drop-down box with "-" or null as the options if that makes it easier to call out somehow.
    any thoughts out there?
    Steve

    You can use a custom JavaScirpt calculation or the simplified field nation calculation, if your field names follow the required convention, with the "-" operator.
    If you are using the "The field is the ____ of the following fields:", you need to create a hidden field with a default value of "-1", a second hidden field that calculated the product of the "-1" field and the field you want to subtract. You can then use that second hidden field in the calculation.

  • Calculation of Depreciation for Tax for India

    Hi
    In India, there is a requirement that the Depreciation for Income Tax should be calculated based on the date of Acquisition. If an asset has been acquired before or on completion of 180 days of a Financial Year, than the calculation of Depreciation is allowed for full year. If the asset has been acquired after 180 days , depreciation is allowed only for 180 days. Hence for an asset acquired on 25/09/2009, system should allow calculation of depreciation from 01/04/2009, assuming that the fiscal year starts from 01/04/2009 and ends on 31/03/2009. However, if the asset is acquired on 07/10/2009, the system should allow depreciation from 01/10/2009. Sap has delivered standard depreciation keys for the same in reference chart of depreciation for India 0IN.
    But if the asset has been acquired on 01/10/2009, still the asset has to be depreciated from 01/04/2009, since the asset has been acquired for less than 180 days into the fiscal year. The system is working fine for asset capitalized on 25/09/2009 and 07/10/2009. But we are not able to map the same if asset is capitalized on 01/10/2009 and 02/10/2009. For these two dates, the depreciation should start from 01/04/2009.
    I have checked the period control setting and calender assignments and everything seems to be in place. How can we tackle the issue?
    Regards
    Sanil K Bhandari

    Hi
    The same has been resolved.I Created a new assignment in Period Control IT for my fiscal year variant. For month 10, i added a new line item with no of days as 2 in addition to no of days as 31 for month 10.
    Regards
    Sanil Bhandari

  • Calculation of Depreciation on Sub Number.

    Hi,
    Pl. provide your valuable remarks for the below 2 points.
    1. What is sub number? In which cases we should use this.
    2. In cases of heavy repairs & maintenance of assets, when amount will be capitalized, whether it will be treated as a separate asset or sub number.
    As I have tried, the Sub-Asset calculate depreciation from the date of capitalisation of Main Asset rather than calculating the depreciation from the date when it is actualy capitalised because thereis no option to change the any field in Depreciation Area when creating Asset Sub-No. vide T-Code AS11.
    Thanks
    Deb

    Hi,
    Go to below path
    SPRO->IMG->FA->AA->MASTER DATA->SCREEN LAYOUT->Define Screen Layout for Asset Master Data
    Choose Define Screen Layout for Asset Master Data
    Select your screen layout rule, which is assigned to your asset's asset class.
    Double click on ligical field groups, and then select 2 Posting information and double click on field group rules
    There for field group 10. capitalisation date deselect check box for mn no and select check boxes for SbNo and Copy.
    SAVE
    And now go to transaction AO21 and select screen layout 1000 and double click on field group rules and there for FG 03 (ord dep start date)  deselect check box for mn no and select check boxes for SbNo and Copy.
    This will resolve your issue.
    Thanks,
    Srinu

  • After 1 year earned leave should generate and pro-rata quota should generate next year on jan 1st.

    Hi Experts,
    Here is the client requirement and please let me know how to solve this.
    Earned Leave: after 1 year earned leave should generate and pro-rata quota should generate next year on jan 1st.
    Example: if employee joins on 01/07/2012 after 1 year i.e 01/07/2013 quota should generate 22 days next year on 01/01/2014 pro-rata quota i.e 01/07/2013, 11 days pro-rata quota should generate. Total 22+11 =33 have to generate on 01/01/2014. and next year 01/01/2015 (22+11+22)=55.
    Note: on 1/7/2013 = 22 days
    on 1/1/2014 = 11 days +22 days; total=33
    on 1/1/2015 = 33 days +22 days; total=55
    Conditions: if employee joins before 15th date of current month include the current month, if employee joins after 15th date exclude the current month.

    You will need 2-3 PCRs to address this.
    In one PCR you need to query the Date of Hire (from IT0041 - I guess you are maintaining this) using HRS=YDAYxx - where xx is the date type. You can then check it it is the first year anniversary or not by using HRS?01. If the condition satisfies populate a custom time type with 22 days.
    In another PCR, you need to check for 01 Jan by using HRS=BCURMO and HRS=BCURDY. In this PCR check again the length of service (see above). If it is more than 1, then proceed to give the pro-rata amount.
    If the pro-rata formula is simple you can use the second PCR or you would need a 3rd PCR to get the pro rata amount. Using HRS=Y**** operator you can query many date differences which will help.
    Regards
    Pramod

  • Why can't we have simple pro rata billing?

    I've been a BT Broadband customer for ten years, and I am sick of these sales packages with their prefabricated bandwidth allowances and telephone or TV options. It seems to me that the BT Broadband sales strategists have a philosophy more appropriate to selling fried chicken. It's comparable to "bargain basket, 3 pieces chicken plus chips; bumper basket, 5 pieces chicken plus chips and free drink, family basket, 7 pieces plus chips and relish pack." Hence the insultingly stupid photograph on the BT Broadband web page, of a young Internet TV consumer before a flickering screen, cramming chicken segments into his  mouth from a paper basket while laughing idiotically. BT's standard telephone service was never like this. You never found that if you didn't make 2 or more calls a month, you would be charged a non-use fee of £2, as happens with one of BT's Broadband plus phone packages. Nor did you get emails saying you had exceeded your allowance and would be charged a flat-rate fine, but "we know it can be confusing keeping track of your bandwidth usage; why don' you switch to a larger, more expensive package?" I suggest a simple solution: sack all the sales strategists and sell services with simple pro rata billing. Charge customers for what they use, plus a flat rate rental, just like you do with the simple phone service. You keep track of individual usage anyway, so that you can nag people about exceeding their allowances. So why not just charge pro rata and get rid of the sales packages? Or are you totally wedded to tricking people into paying for more than they need?

    Welcome to the forum, which is essentially a customer to customer affair and messages do not necessarily reach anyone in BT.
    As a fellow customer I couldn't agree more, except to say that it's not just BT. But you have to realise that we're ungrateful wretches, refusing to give thanks for the bountiful gifts of competition that were promised when telecoms and other utilities were thrown to the wolves of big business. The fact is though that when you're sending pretty much the same signals down the same wires, the same current down the same cables, the same gas through the same tubes, you've got to do something to snare more customers than the next firm. What better way than conning Joe Public into believing that your ever-changing, unfathomable price structure, all wrapped up in shoddy customer service from minimally-trained staff with little understanding and even less commitment, is better than anyone else's? If I was a cynic I could bang of for hours.
    You can click the white star next to this message if you think it was helpful.

  • Does Transfer Invoice Price Variance pro-rate for partial quantity ?

    We were planning on using Transfer Invoice Price Variance to Inventory but unfortunately, we find when there's an IPV for quantity that's partly issued - the variance is not pro-rated but entirely applied to the remaining quantity.
    Just wondering if this is desired functionality and if so, could we use SLA to ask the program to pro-rate the variance and for partial quantity, apply the pro-rated amount to the quantity remaining and the rest to the Cost Variance account.
    Thanks,
    Sanjib

    TIPV to Inventory doesn't pro-rate for partial quantity.
    It transfers the entire IPV to the remaining quantity.

  • Pro rate function in billing plan

    Folks
    Would any one know how i could pro rate the value for the last month of the billing plan cycle. You would think this is a standard SAP function
    I have looked, and i am not able to find a solution. Our customer does not want to do any code changes. Let me know if you know of any standard changes that can be done.

    Hi,
    Looks like you are not rewarding for the helpful responses.
    <b>Please do reward for the helpful responses.</b>
    SAP has <b>Retroactive Billing</b> funcitionality
    Use
    New pricing agreements that you make with your customers may affect billing documents that have already been processed and settled. If a new pricing agreement is effective before the pricing date of the billing documents, you can perform retroactive billing to call up a list of these documents and reevaluate them with the new price. You can then create additional billing documents to settle any differences.
    Integration
    Retroactive billing is a special billing function often used in  scheduling agreement processing.
    Features
    With the retroactive billing function, you can:
    Call up a list of documents affected by price changes
    Trigger the system to create the necessary retroactive billing documents directly from the list
    Create credit or debit memos directly
    Review any errors in a log
    Simulate the retroactive billing process for any document
    How does Retroactive Billing work?
    In this example, the system calculates the difference between the net value of the invoice ($100) and today's net value based on the new price ($90). It then creates a credit memo with the net value of $10 to be credited to the customer.
    Primary and Secondary Documents
    The system calculates retroactive billing values for primary documents. It can use secondary documents to help calculate this value.
    Invoices are always primary documents.
    Other billing documents, such as debit or credit memos, can be primary or secondary documents. This depends on the order reason entered in the billing document.
    For more information on how the order reason is used to control primary and secondary documents, see Order Reason in Retroactive Billing. This section will also provide a more detailed example of how retroactive billing works.
    Primary Documents
    Primary documents are:
    Invoices
    Credit memos that refer to returns
    Credit and debit memos in which you have entered the relevant order reason
    You can also assign an order reason to a memo request which then passes it along to the referenced credit or debit memo.
    Secondary Documents
    Secondary documents are the following billing documents in which you have entered the relevant order reason:
    Credit and debit memo requests
    Credit and debit memos
    The system displays such a document only when it has been created with reference to the invoice and when the currencies in both documents match.
    If you create a credit or debit memo (or memo request) without reference to an invoice, you will not be able to see in the retroactive billing list if the invoice has already been billed retroactively.
    When you create a credit or debit memo request which is relevant for retroactive billing as a secondary document, the system will use it to calculate retroactive billing for the referenced document.
    The system does not take into account whether or not a request has been rejected, partially billed, or billed using another pricing procedure. Also, it does not take into account any changes in the payer, sold-to party, sales organization, billing date, or material.
    <b>Reward if helpful.</b>

  • To Pro-Rate or not to Pro-Rate

    Apple has given me two options for my replacement MBP.
    Since I still have 2/3rds left of my Apple Care Warranty, they would pro-rate and refund it. Then I would buy a new one at regular price (but at a sort of discount considering the other was refunded.)
    They also will simply transfer the old one over as if i never got a new computer.
    The problem is apple said they can't tell me how much money I'd get back from the old plan until I actually cancel (includes $25 cancelation fee)
    I think the extra year might be nice (get me through 4 years of school then) but at the same time I don't want to do t if its to pricy.
    What do you guys think?

    Isn't applecare a set price thing only available from Apple stores/apple stores online?
    Nope. While you can't obviously haggle with the online Store, physical stores and Apple Store phone agents can play to a certain degree with pricing when it comes to price matching. Asking for a discount on its own will get you a big fat no.
    Anyone who can sell a Mac can sell AppleCare so it does pay to shop around. While margins on AppleCare for retailers aren't anywhere near as good as they once were (around 50%) there's still room to move.

  • Pro rata billing in SAP FE-FX

    Hi,
    Can anybody tell me how can the pro rata billing in RE-FX can be done. What config setting we have to do for pro rata billing. and the invoice can be generated in RE-FX.
    Is there is any link for configuring the billing.
    Thanks,
    Shailendra

    Hi,
    I have exactly the same requirement. Making the value 'M', does not adjust the price automatically.
    Currently I have as below (dates in dd/mm/yyyy) in the billing plan schedule item level.
    11/01/2010 to 31/01/2010 - $3100
    01/02/2010 to 28/02/2010 - $3100
    01/03/2010 to 31/03/2010 - $3100
    01/04/2010 to 30/04/2010 - $3100
    01/05/2010 to 31/05/2010 - $3100
    01/06/2010 to 30/06/2010 - $3100
    01/07/2010 to 22/07/2010 - $3100
    What I would like is to have as below,
    11/01/2010 to 31/01/2010 - $2100   "Adjusted for 21 days of the month
    01/02/2010 to 28/02/2010 - $3100  + $520 
    01/03/2010 to 31/03/2010 - $3100  + $520
    01/04/2010 to 30/04/2010 - $3100  + $520
    01/05/2010 to 31/05/2010 - $3100  + $520
    01/06/2010 to 30/06/2010 - $3100  + $520
    01/07/2010 to 15/07/2010 - $1500      " Adjusted for 15 days
    " Additional $520 is the amount distributed equally among all entries except first and last, so that the net amount that will be billed to customer remains same.
    Please share some ideas on how I can achieve this - either through configuration or in coding.
    Thanks
    Vinoth

Maybe you are looking for