mrp_operation: Workorder 's costing should be based on working hours instead of number of hours.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Committed
|
Low
|
OpenERP Publisher's Warranty Team |
Bug Description
This bug is present in 6.1 and trunk:
1. Create a new DB with demom data and install mrp_operation (or take a db on runbot)
2. Go into Manufacturing > Work Orders
3. Select a work order from "Assembly Workshop" and launch it
4. close it something like 10 sec after.
5. go into your analytic accounting and open the analytic account "Costing Account For Hours of Assembly." which is the account for the hours for the Work Center of the Work Order.
6. In this account, I should have analytic entries (at least one) with the amount being : time spent on my work order * cost per hour. there's a bug here because the computation is total time defined on the work center * cost per hour. This is wrong because the "realized" time to finish your Work Order is (in 90% of the case) different than the theory time you've specified on your work center
Related branches
- Amit Parik (community): Needs Fixing
- OpenERP Core Team: Pending requested
-
Diff: 21 lines (+2/-2)1 file modifiedmrp/mrp.py (+2/-2)
- OpenERP Core Team: Pending requested
-
Diff: 21 lines (+2/-2)1 file modifiedmrp/mrp.py (+2/-2)
summary: |
- mrop_operation time amount not taken into account + mrp_operation time amount not taken into account |
Changed in openobject-addons: | |
status: | Confirmed → In Progress |
tags: | added: maintenance |
Changed in openobject-addons: | |
assignee: | OpenERP R&D Addons Team 2 (openerp-dev-addons2) → OpenERP Publisher's Warranty Team (openerp-opw) |
Hello Antonie.
I tried your same scenario at my end, and I got a correct result.
Analytic costing is calculated like Number of hours * Cost per hours (which is 3.61*0.10 = 0.36) which is correct (as I got).
I have prepare a video for this and attached with this bug report, So would you please check it and notify us where you faced the problem.
Or may I missed something.
Thanks and waiting for your reply!