c2c-oerpscenario team mailing list archive

[YannickB <yannick.buron@xxxxxxxxxxx>]

Thank you for your answers,

>however,what you touched is NOT ovnicraft's work, but original authors'
and mine (see my wiki for authors' names). I do not want to minimise
ovnicraft's efforts, but for the time being he focused on the rest of
wizards, to upgrade them to the new way (see openerp doc for differences)

Sorry for it, please have my congratulations for the work.

>i fully agree, but i understand that this is an additional burden with
no direct benefits (well, we can talk about that, but no one will PAY
for doc)

Yes, this is why I don't like everyone (including me) in the openerp
community are professional who make their life with. We really need
communication campaign for uninterested contributor, like students,
users, experts etc... I am currently focus on it in France.

>thiswas the minimum I plammed for the first round, and I do believe that
calculations are correct. please just be aware that the progressive
depreciation method is mixed, once the value is lower that the
theoretical linear, it switches to linear. I think that this shoud be
split, into progressive and mixt (and linear, of course)

Unfortunately, I just can't understand because my expertise in asset is
not enough. My point is that it's impossible to guess how the
calculations is done and help to improve it just by testing the module.
You should write the formula somewhere, in the description or in the dia
file.

>this is how it works for the newly acquired asset (via invoice) so I see
no reason why it will be different for "direct" creation as you called it.

With the invoice, all the asset are completely automatically filled, I
will give you an example, in sale order line when you give the product
it will automatically filled the other field like UoM, unit price,
description, taxes etc... Here it is the same, when in direct input,
when you give the asset categorie or depreciation method it should fill
the others fields. This is an important ergonomic rule for the input. I
suppose it can easily be done with an on_change or something else.

>I will try, I will put it on the accounting experts discussion and in
the wiki. i am rather new to the dia program, so I might need help :-)

Don't hesitate, this is purely BPMN but I made some adaptations to use with OpenERP ;). 
Once again, thanks for your reply.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/777004

Title:
  My tests of account_fixed_asset, bugs, suggestions and diagram

Status in OpenERP Modules (addons):
  New

Bug description:
  Hi everyone,

  This bug is about the branch https://code.launchpad.net/~ovnicraft
  /openobject-addons/asset_refactor_wizards, especially the module
  account_fixed_asset.

  I am very interested by this module and so I'd like to improve it.
  First I found some bads bugs with the wizard :

  Impossible to create direct asset (Invoice field required and read-only)
  Impossible to use wizard "Initial Value" (Impairment account refer to account.acount and not account.account)
  Impossible to use wizard "Abandon" and "Suppress"(Field 'asset_id' does not exist in object 'browse_record(account.asset.method, 10)')
  Impossible to use "Change parameters" (global name 'ids' is not defined)
  Impossible to use "Reevalute Asset" ('account_asset_method' object has no attribute '_check_date')

  I manage to create asset with the invoice, and create periodical
  account entry, even if I'm not sure the calculation was right.

  If we have the possibility to create direct asset, I suggest to improve the input of the data by :
  In the asset, you should refresh Depr.Duration, Frequency of writing and progressive factor when Depreciation Method change, at least if these fields aren't already filled. 
  Also, you should refresh Depreciation Method and the account information when the Asset Category change, at least if these fields aren't already filled.

  Finally, I made a diagram about this module, joined to this bug report. I think this is really necessary because asset management is very complicated and technicals specifications should be very useful for the teamwork. 
  Please help me to fill the diagram, so next I could ask my devmen to help debug the module but I could only do it if I know exactly the way you want to implement the functionality. 

  Thanks for reading and good jobs, this is a huge and needed
  improvement of the asset management in OpenERP.