Yes, I think it is a good idea. Thanks for working at this. Jacopo
On Apr 19, 2010, at 6:37 PM, Bob Morley wrote: > > When you create a new production run for a particular product, a clone of the > routing template work effort tree is created for the new production run. In > doing this any WorkEffortPartyAssignment entities are also copied along with > the BillOfMaterials information (into WorkEffortGoodStandard). > > My question is why do we not also clone the WorkEffortCostCalc. If we were > to do this, tasks that were created via the routing template OR manually > created could be handled consistently. We would also have the ability to > update the WorkEffortCostCalc for that specific ProductionRun. I assume > this latter point is the reason why we are copying WorkEffortPartyAssignment > so that different people can be assigned the task without affecting the > routing template itself. > > What I would like to do is start cloning these records for the new > ProductionRun and then change createProductionRunTaskCosts so that it will > simply use the WorkEffortCostCalc entities associated with the specific task > (rather than potentially using the associated routing task). > > Very interested in hearing from anyone with practical experience with > ProductionRuns to see if I am missing something (or any developers that > worked in this area). > -- > View this message in context: > http://n4.nabble.com/Copying-WorkEffortCostCalc-as-part-of-a-ProductionRun-tp2016212p2016212.html > Sent from the OFBiz - User mailing list archive at Nabble.com.
