Re: workorder with nested BOM's

hi nathan,

thanks for clarifying.

Now, our subcomponents are partly 'components', partly like your handle.

In any case, we need a way to show whether subcomponents are finished.
If we automatically create sub-workorders at time of production start (maybe also earlier to procure it), we can then finish these workorders. So this would allow for planning of the workorders and all production. Openerp does something like this, but has other problems for us. This is also somewhat related to the auto-issuing of components in weberp. But they do it only at receiving the product, which does not make sense either (e.g. at finishing the product i learn that i do not have enough subcomponents C...).

What is in favour for perp is that our project planning (dotproject) and our main crm (vtiger) are both in mysql, so it is easy to communicate between the applications using mysql triggers. Openerp seems to be a step further, but is in postgresql - no easy way to update data in mysql.

So, for example, we could add projects in dotproject upon workorder creation (containing the production steps and documents). And if we shift a project=workorder in dP, the start etc dates in perp could automatically be adjusted via mysql trigger.
Klaus