Re: workorder with nested BOM's

On 7-Jul-09, at 1:53 PM, opto wrote:

> ...
> 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.

Ok, a few more details please.
Should these sub-work orders be created every time, as:
Somebody ordered a D, so create a W.O. for that, and WOs for 2C, 2B

Or should current inventory be taken into account, as:
You've got time?  Build us some B, we always use those.
Somebody ordered a D, so create WOs for D, 2C, 0B,  because we already  
have 7 B on hand that aren't reserved for another build.

> ...
> 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.

That's clever, I like that.

I have concerns if you take that too far, as much of pERP's  
functionality is in the code.  I'd hate to have you miss out on  
something.
Setting completion dates via a trigger, for example, would skip the  
part where all your inventory is consumed and costs allocated to the  
work order.

Nathan Gray
nathan at goarctic dot com


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Perp-developers mailing list
Perp-developers@...
https://lists.sourceforge.net/lists/listinfo/perp-developers