credativ team mailing list archive
-
credativ team
-
Mailing list archive
-
Message #01445
[Bug 900809] Re: account_asset - do not use account_move_lines
** Changed in: openobject-addons
Importance: Undecided => Wishlist
** Changed in: openobject-addons
Status: New => Won't Fix
--
You received this bug notification because you are a member of OpenERP
Framework Experts, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/900809
Title:
account_asset - do not use account_move_lines
Status in OpenERP Addons (modules):
Won't Fix
Bug description:
the assumption that historical account_move_lines are available is far
from reality.
def _amount_residual(self, cr, uid, ids, name, args, context=None):
cr.execute("""SELECT
l.asset_id as id, round(SUM(abs(l.debit-l.credit))) AS amount
FROM
account_move_line l
WHERE
l.asset_id IN %s GROUP BY l.asset_id """, (tuple(ids),))
res=dict(cr.fetchall())
for asset in self.browse(cr, uid, ids, context):
res[asset.id] = asset.purchase_value - res.get(asset.id, 0.0) - asset.salvage_value
for id in ids:
res.set
solution (alternatives)
* the historical depreciation lines must be stored for each asset ( IMHO many migrations will not be possilbe using this method becasuse of lack of historical data.)
* the depreciation must be calculated
book value of the previous year / remaining periods.
this works always and allows extraordinary modification of book values and remaining periods - which sometimes is required by tax authorities.
obviosuly book values of preceeding years can be stored, but it's not a requirement and only necessary if reopening of previous years is necessary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/900809/+subscriptions
References