mrp_operation: Workorder 's costing should be based on working hours instead of number of hours.

Bug #1021788 reported by Antoine(OpenERP)
24
This bug affects 4 people
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 (amit-parik)
summary: - mrop_operation time amount not taken into account
+ mrp_operation time amount not taken into account
Revision history for this message
Amit Parik (amit-parik) wrote : Re: mrp_operation time amount not taken into account

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!

Revision history for this message
Amit Parik (amit-parik) wrote :
Changed in openobject-addons:
status: New → Incomplete
Revision history for this message
Antoine(OpenERP) (ahu-openerp) wrote :

Hello Amit,

Thanks for the answer, but I think your video is showing how the computation is base on the "theoretical" side. When you define work center, you give the time taken to finish 1 cycle. This is what I call a "theoretical" value. You put it because you think it's the time it will take to finish your work order.

But Imagine this: Let's say I'm creating some elements like custom chairs. Every chair uses the same BoM and the same routing, and so, the work orders being created by the manufacturing orders are all the same. BUT, we could consider that the time taken to build and customize chairs is different for different manufacturing order (and the work orders in this manufacturing order). That's also why you have the ability to start and stop your Work Order.

Now let's say you define 1 hours for a work center, but that the work order took you 40 min to be finished. You don't want the amount for 1hour in your accounting but 2/3 of an hour. That's what I mean. The time used for calculating the cost in the analytic line should be based on the attribute "Working Hours" of your Work Order form, not based on "Number of Hours".

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

Hello Antonie.

Thanks for your good explanation on this.

I also agree with you, It should be consider "Working time/hours" instead of "Number of hours".

Thanks!

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Low
status: Incomplete → Confirmed
summary: - mrp_operation time amount not taken into account
+ mrp_operation: Workorder 's costing should be based on working working
+ hours instead of number of hours
summary: - mrp_operation: Workorder 's costing should be based on working working
- hours instead of number of hours
+ mrp_operation: Workorder 's costing should be based on working hours
+ instead of number of hours
summary: mrp_operation: Workorder 's costing should be based on working hours
- instead of number of hours
+ instead of number of hours.
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Jignesh Rathod(OpenERP) (jir-openerp) wrote :

Hello Antoine ,

Thanks for reporting.

This issue has been fixed following branch and rev no , rev id.

lp:~openerp-dev/openobject-addons/trunk-bug-1021788-jir

Rev No : 7009
Rev ID : 7009 jir@jir-desktop-20120710085303-roq2ngy21rxt1gy4

Thank you!

Changed in openobject-addons:
status: In Progress → Fix Committed
tags: added: maintenance
Changed in openobject-addons:
assignee: OpenERP R&D Addons Team 2 (openerp-dev-addons2) → OpenERP Publisher's Warranty Team (openerp-opw)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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