Public bug reported: This bug is related with assets in OpenERP v7.0. Specifically, in button 'Compute' at Depreciation Board with option 'Prorata Temporis' in asset configuration.
In this board, the next depreciation date (estimation) is based on purchase date. But, for example, in case when purchase date is 31/12/2013, next depreciation will be 1/1/14 and then 28/2/14, but from that date, next depreciation will be 28/3/14 instead of 31/3/14. Also, it exists a problem with months composed of 30 days: For example in June depreciation would be 28/6/14 instead of 30/6/14. The estimated of next depreciation date doesn't 'respect' or not estimate correctly the final date of each month, depending if the month has 28, 30, 31 days. When February is processed, all depreciation dates are estimated based on 28 or 29, it means that since that date, estimate date ignores purchase date as beginning and replace it with 28/2 or 29/2. As following, we show some images with the error. Both images describe the configuration and then, the error in depreciation board. Asset configuration http://i.imgur.com/UODLdnO.png Depreciation board http://i.imgur.com/PUUQjgE.png ** Affects: openobject-addons Importance: Undecided Status: New ** Tags: asset openerp ** Attachment added: "Wrong depreciation Board" https://bugs.launchpad.net/bugs/1306149/+attachment/4080074/+files/Selecci%C3%B3n_008.bmp ** Attachment removed: "Wrong depreciation Board" https://bugs.launchpad.net/openobject-addons/+bug/1306149/+attachment/4080074/+files/Selecci%C3%B3n_008.bmp -- You received this bug notification because you are a member of OpenERP Indian Team, which is subscribed to OpenERP Addons. https://bugs.launchpad.net/bugs/1306149 Title: Next depreciation date doesn't estimate correctly when purchase date is different than the first date of month Status in OpenERP Addons (modules): New Bug description: This bug is related with assets in OpenERP v7.0. Specifically, in button 'Compute' at Depreciation Board with option 'Prorata Temporis' in asset configuration. In this board, the next depreciation date (estimation) is based on purchase date. But, for example, in case when purchase date is 31/12/2013, next depreciation will be 1/1/14 and then 28/2/14, but from that date, next depreciation will be 28/3/14 instead of 31/3/14. Also, it exists a problem with months composed of 30 days: For example in June depreciation would be 28/6/14 instead of 30/6/14. The estimated of next depreciation date doesn't 'respect' or not estimate correctly the final date of each month, depending if the month has 28, 30, 31 days. When February is processed, all depreciation dates are estimated based on 28 or 29, it means that since that date, estimate date ignores purchase date as beginning and replace it with 28/2 or 29/2. As following, we show some images with the error. Both images describe the configuration and then, the error in depreciation board. Asset configuration http://i.imgur.com/UODLdnO.png Depreciation board http://i.imgur.com/PUUQjgE.png To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-addons/+bug/1306149/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
