openerp-india team mailing list archive

[Carlos Vásquez (CLEARCORP) <carlos.vasquez@xxxxxxxxxxxxxxx>]

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

-- 
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/1019932

Title:
  [6.1] [account_asset] bad asset and move lines data

Status in OpenERP Addons (modules):
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1019932/+subscriptions