Skip to Content

Contributors

Re: Project consumable (v14.0)

I've seen that module and this is why I've chosen to not use it:

* I'm not sure it's the same purpose
* I do not require to enforce consumable to be linked to a specific task only to the project
* I'm not sure we need an extra model (`project.task.material`)
for my needs and I'm a bit afraid about keep consistency between such model
and `account.analytic.line`. Or do you agree that I move `project.task.material` to
use `account.analytic.line` instead ?
If so I can change the behaviour and provide a migration script to smoothly go ahead.

Let me know what you think !


Le mer. 19 mai 2021 à 10:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
I would go with using and expanding if needed project_task_material.

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
Pierre

by Pierre Verkest - 10:41 - 19 May 2021

Reference

  • Project consumable (v14.0)
    Hi there,

    I've the need to follow the analytic cost of consumables per project.

    As far when consumables are purchase we don't know how they will be used and while creating the quotation we don't know how exactly how many consumable to be sale, I'll create a new module probably called project_consumable in oca/project repo that will let users to record used consumable that will create relevant analytic account line linked to the consumable product and project (likes hr_timesheet which record time per project/task). I'll take care we get proper analysis.

    I plan later to generate sale order (I know this is not very suitable. Add products in the generated invoice would make more sense in odoo... could be done in different modules anyway ) from some of those account move lines.

    Are there already such efforts? I'll be happy to hear your comments :)

    regards,

    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

    by Pierre Verkest - 10:01 - 19 May 2021