workorder with nested BOM's

[opto]

I have nested BOM's:

part A
part B consisting of 10 A's
part C
part D consisting of 2 C's and 2 B's

I make a workorder for 2 part D.
Should'nt this also create workorders for the B's necessary to manufacture the D's?
Any help is appreciated.


Also, where do I set the status for workorders?

Klaus

[Nathan Gray]

On 7-Jul-09, at 10:55 AM, opto wrote:

>
> I have nested BOM's:
>
> part A
> part B consisting of 10 A's
> part C
> part D consisting of 2 C's and 2 B's
>
> I make a workorder for 2 part D.
> Should'nt this also create workorders for the B's necessary to  
> manufacture
> the D's?

Depends.

I know that if B and C are pseudo (not real), no work order will be  
created.  We use this for assemblies that are logically grouped  
(handle assembly, side panel) but are assembled on line.  We don't  
actually build, put in inventory, pull from inventory, then attach a  
handle assembly.  This may be similar for you.  Do you have completed  
Bs and Cs sitting around?

My opinion is that the B and C should probably be added as lines on  
the original work order, so you can keep them together, but I don't  
think this happens currently.  If you want, please let me know any  
other details or options, I'll try to add this in.


> Also, where do I set the status for workorders?

Depends.
If you're not using workflow, you don't get much choice of status, the  
options are:
- Pending: Entered, but no start date
- Scheduled: Start date entered
- Completed: Finished production
This is because without workflow, pERP cannot track your work order  
through your production process.  It all happens at once, "In  
production" lasts about 0.2s as all inventory is consumed and the work  
order is completed.  This works fine for small shops, where the  
overhead of keeping the status up to date isn't worth it.

If you are using workflow, see this reference:
http://www.projecterp.org/mediawiki/index.php/Setting_Up_Workflow
After you're set up, you can move your work orders through the process  
with the 'Move To' dropdown on the Work Order List.
I hope to get a more automated solution (line scanners) done soonish.

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/blackberry
_______________________________________________
Perp-developers mailing list
Perp-developers@...
https://lists.sourceforge.net/lists/listinfo/perp-developers

[opto]

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

[Nathan Gray]

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

[Nathan Gray]

On 9-Jul-09, at 2:01 PM, K.Buecher wrote:

> Hi Nathan,
>
> I would find this more realistic:
>
>> 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.

Ok, that one made more sense to me as well.

> Contrary to weberp, inventory should be booked out at WO creation or  
> better WO start (maybe print a list of stock components to be used  
> for the WO).

pERP currently reserves the inventory at work order creation.
We often sell replacement parts, and if we don't reserve the  
production parts, someone will try to sell them.  Production doesn't  
like that.
The list of components (bill of materials) for each item can be found  
from the Edit Work Order page.

> ...
> Would also be good to flag WO's as waiting for stock (idea stolen  
> from openerp).if not all subcomponents are available.

That sounds like a great idea.  Currently pERP will generate a list of  
missing stock on the work order detail popup:
Not enough 00644 - Screw #8x2" Deck on hand at Installs.
You need 10 , you have 0.
It would be good to see some kind of warning about that on the work  
order list.

> Waiting for stock should not block the start of a WO (one can do a  
> lot of work, even if the final screw is still missing).

You can still build even if the computer says the screws aren't  
there.  Nothing more annoying than having to stop production because  
somebody miscounted 2 months ago...

> What also would be interesting (saw this nowhere )is:
>
> consider a WO for D today, another tomorrow, another next Monday.
>
> Suddenly, I have three WO's for 2C each. I could combine them into  
> one for 6C, if the deadline of the three deliveries is pretty next  
> to each other. Production would love this.

This one I'm afraid I won't be able to find time to add in.  We  
deliberately keep things separate, to the point where an order for 20  
is filed as 20 work orders.
It's certainly possible, and if a good patch were submitted I would  
include it.

An alternative that might be worth testing, depending on your  
organisation, is pre-scheduling your work orders to optimum levels (if  
it's best to run 5 through at a time, for example).  The Sales Order  
section can automatically slice work orders and allocate 2 to one  
customer, one each to two other customers, one for on hand inventory.

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

[Nathan Gray]

On 9-Jul-09, at 2:26 PM, Nathan Gray wrote:
>
>> ...
>> Would also be good to flag WO's as waiting for stock (idea stolen
>> from openerp).if not all subcomponents are available.
>
> That sounds like a great idea.  ...
> It would be good to see some kind of warning about that on the work
> order list.

Done.  Some other errors and warnings are in there too, but the most  
common one is inventory shortage.

>> Waiting for stock should not block the start of a WO (one can do a
>> lot of work, even if the final screw is still missing).
>
> You can still build even if the computer says the screws aren't
> there.  Nothing more annoying than having to stop production because
> somebody miscounted 2 months ago...


In my investigations, it turns out there's a good reason to block  
production.  If there's no inventory, FIFO costing has issues.  Turns  
out the first item in an empty list is ... nothing.  Of course, this  
doesn't affect production at all, but when your example "screw" costs  
a few more dollars, this can throw off the cost of the item being  
produced by a noticeable amount, which causes accounting more work  
because they have to correct it.

In pERP, the 'final screw' is not an issue if you're using workflow,  
because that gives time for the screw to arrive before it needs to be  
used.  Without workflow, the entire build is done at once (usually  
after the work order has been physically built), so all parts need to  
be there.

I'm going to refine the stock shortage check, so that if you're not  
using workflow, it will block the WO.
Those using workflow will have a config option if they want to block  
workflow for stock shortages, but the default will be to let it go.

Nathan Gray
nathan at goarctic dot com


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Perp-developers mailing list
Perp-developers@...
https://lists.sourceforge.net/lists/listinfo/perp-developers