[trunk/7.0/6.1] [account_asset] bad asset and move lines data

Bug #1019932 reported by Carlos Vásquez (ClearCorp)
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Low
OpenERP R&D Addons Team 3
OpenERP Community Backports (Addons)
New
Undecided
Unassigned

Bug Description

Several concept errors:

1. When the asset is created from an invoice, the asset reference is assigned as the invoice number. The correct thing to do is link the invoice to the asset, and let the invoice have it's sequential number (or custom user assigned number)

2. When the asset is created manually, the reference is filled because there is no sequence or sequence type created by default at module installation. The sequence code is there, but the user has to know to create at least one sequence with the specific code set to "account.asset.code".

3. When the move is created for a depreciation line, the date used is the purchase date (if asset is marked as prorata), or today. If the depreciation line already has a date, it must be used. Otherwise it is misleading for the user. The correct dates are already calculated when the depreciation lines are created. The move line creation must use those data.

4. The depreciation moves should use the default journal sequence for number (name), the reference (ref) can have some info about the asset and the depreciation line. The same applies for the move lines.

Tags: asset

Related branches

Revision history for this message
Cristian Salamea (ovnicraft) wrote :

Hello,

1. so you must take in care asset comes from supplier invoice and needs keep a ref, supplier invoices dont get a seq number it comes from account move related (you can check action_number method in invoice).

2. Always you need to setup the modules, remember its an ERP system, the complex stage is configuration.

3. There is a reported bug around you can check it for more details.

4. i check the depreciation and moves are numbered with sequence defined in journal.

Regards,

Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Carlos Vásquez (ClearCorp) (cv.clearcorp) wrote :

Hi,

Keeping the same points:

1. That's exactly my point. Assets coming from a purchase invoice should have a reference indicating so. But you never use the invoice number as asset code. And text references aren't a good choice. It is better to have a m2o to the purchase invoice, and to keep a consistent sequential code. This is what you want in almost every case.

2. Agreed, but this is not a reason to avoid proper default configuration at installation. The non programmer user would never know to set the sequence with the appropriate seq code if there isn't a default one.

3. Yes, it is also linked in my branch and merge proposal.

4. The depreciation moves have a code like this: asset_id/depreciation_seq, for example: 456/35. How will the use know which one is asset 456 as a table id? It is better to have a more informative move reference and get the move number from the journal seq.

I don't see how this bug is incomplete, and there is a merge proposal to clarify even more. I am marking it as new again.

Changed in openobject-addons:
status: Incomplete → New
Changed in openobject-addons:
importance: Undecided → Low
status: New → Confirmed
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
Revision history for this message
gmarcon (gmarcon) wrote :

Regarding point 3. and 4. I confirm the bug exists also for version 7.0 of account_asset, see bug #1099818.

Revision history for this message
Amit Parik (amit-parik) wrote :

Hello,

Comment 3 is proper. we need to fix this on v7 as well as trunk.

Thank you!

summary: - [6.1] [account_asset] bad asset and move lines data
+ [trunk/7.0/6.1] [account_asset] bad asset and move lines data
Amit Parik (amit-parik)
tags: added: asset
Revision history for this message
xavi (xgilest) wrote :

Hi,
this bug has been more than one year opened, is there any chance that you will solve it soon.
Thank you.

Revision history for this message
Pedro Manuel Baeza (pedro.baeza) wrote :

I have posted an specific bug for the point 4, to try to focus each problem:

https://bugs.launchpad.net/openobject-addons/+bug/1258237

Regards.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.