web-erp-developers

[WebERP-developers] Inventory in Manufacturing

[webERP D. <web...@li...>]

We are using the BOM, WO and other capabilities of the Manufacturing Midule
and have the following challenges:

* We have items that contain batch or serial numbered parts.  If we create a
work order for a number of parts, and issue a number of serialized or batch
controlled items, there exists no means to force a specific component to a
finished part.  For example we have serial numbered item ABC as a component
of serial numbered part DEF.  When we build DEF we assign a unique serial
number and incorporate one of serial numbered item ABC.

There is no way to make sure that Part DEF Serial Number 123 contains
component ABC 888.

We need to trace back items by serial number and batch.  We recognize that
some of this information is in the transaction trail.  But the 1 to 1
relationship is not known.

If our work orders are for one piece then the relationship can be
maintained, but such is very onerous for all involved.

* We too frequently make mistakes issuing items to Work Orders of make data
entry errors on serial numbers.  The needs to be a way to "roll
back"/diassemble an item so the inventory is correct and proper item can be
built.

Bob Thomas



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Inventory-in-Manufacturing-tp4656561.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Inventory in Manufacturing

[webERP D. <web...@li...>]

Interesting, my use case is similar. I build electronic subassemblies in lots of 5, 10, etc and would need to assign connector serial numbers, sensor serial numbers, etc. to each subassembly serial number as assembled (or in one or more groups at stages in the assembly process).

Dale

On 2013-07-05, at 9:39 AM, webERP Developers <web...@li...> wrote:

> We are using the BOM, WO and other capabilities of the Manufacturing Midule
> and have the following challenges:
> 
> * We have items that contain batch or serial numbered parts.  If we create a
> work order for a number of parts, and issue a number of serialized or batch
> controlled items, there exists no means to force a specific component to a
> finished part.  For example we have serial numbered item ABC as a component
> of serial numbered part DEF.  When we build DEF we assign a unique serial
> number and incorporate one of serial numbered item ABC.
> 
> There is no way to make sure that Part DEF Serial Number 123 contains
> component ABC 888.
> 
> We need to trace back items by serial number and batch.  We recognize that
> some of this information is in the transaction trail.  But the 1 to 1
> relationship is not known.
> 
> If our work orders are for one piece then the relationship can be
> maintained, but such is very onerous for all involved.
> 
> * We too frequently make mistakes issuing items to Work Orders of make data
> entry errors on serial numbers.  The needs to be a way to "roll
> back"/diassemble an item so the inventory is correct and proper item can be
> built.
> 
> Bob Thomas
> 
> 
> 
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Inventory-in-Manufacturing-tp4656561.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers

Re: [WebERP-developers] Inventory in Manufacturing

[webERP D. <web...@li...>]

Hi Bob,

If you need tracability back to the item, then you need individual work 
orders. Or some other functionality to manage the tracing. I almost 
wonder if it may be better to maintain the components of each completed 
item as a separate exercise - perhaps as part of the completion - 
receiving finished items against a work order with serialised output 
items and input items. Perhaps a new table created that stores the 
components serial numbers for each serialised/batch controlled component 
for the serialised output item - and this process being added to the 
receiving completed items from the work order. A bit of work - but would 
resolve this issue for you. Would be a nice contribution :-)

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz
skype:daintree


On 06/07/13 03:39, webERP Developers wrote:
> We are using the BOM, WO and other capabilities of the Manufacturing Midule
> and have the following challenges:
>
> * We have items that contain batch or serial numbered parts.  If we create a
> work order for a number of parts, and issue a number of serialized or batch
> controlled items, there exists no means to force a specific component to a
> finished part.  For example we have serial numbered item ABC as a component
> of serial numbered part DEF.  When we build DEF we assign a unique serial
> number and incorporate one of serial numbered item ABC.
>
> There is no way to make sure that Part DEF Serial Number 123 contains
> component ABC 888.
>
> We need to trace back items by serial number and batch.  We recognize that
> some of this information is in the transaction trail.  But the 1 to 1
> relationship is not known.
>
> If our work orders are for one piece then the relationship can be
> maintained, but such is very onerous for all involved.
>
> * We too frequently make mistakes issuing items to Work Orders of make data
> entry errors on serial numbers.  The needs to be a way to "roll
> back"/diassemble an item so the inventory is correct and proper item can be
> built.
>
> Bob Thomas
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Inventory-in-Manufacturing-tp4656561.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>

Re: [WebERP-developers] Inventory in Manufacturing

[webERP D. <web...@li...>]

Phil,

I think that changing the work order receive code is the way to proceed. 
The following scenario might possibly work:

1) Remove the material issue function.  It is only a means to allow for
tracking inventory location and issuing whole batches.  There are too many
problems with the batch issue to make it a viable solution.  If one needs to
keep batches isolated, the existing method might be somehow forced to work,
but the shop discipline is too difficult to implement.  One can only manage
one batch at a time.  The users must keep track to the side on the usage and
then issue the next batch.  Scrap is not handled at all.

2) If batch or serial numbered items are in the BOM, a special receiving
function is needed.  In the receiving function, the user would enter the
serial number or batch of the components used in the new serial/batch
controlled item.

3) A check should be made when creating a BOM that the item being created
matches the control type of the strictest component in the BOM, i.e. an
uncontrolled item can't require a controlled and a batch controlled item
can't require a serial numbered item.

Bob Thomas

P.S. I had submitted a simple change to item issue to code to insure that
only items that existed are available for issue.  The system always keeps a
record of where serial numbered items have been stored.  When an item is
removed, the location/serial number pair is set to quantity zero.

4.10.1 WorkOrderIssue.php

			$SerialNoResult = DB_query("SELECT serialno
										FROM stockserialitems
										WHERE stockid='" . $_POST['IssueItem'] . "'
										AND loccode='" . $_POST['FromLocation'] . "'",

Corrected Code:

			$SerialNoResult = DB_query("SELECT serialno
										FROM stockserialitems
										WHERE stockid='" . $_POST['IssueItem'] . "'
										AND loccode='" . $_POST['FromLocation'] . "'
										AND quantity > 0",



--
View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Inventory-in-Manufacturing-tp4656561p4656581.html
Sent from the web-ERP-developers mailing list archive at Nabble.com.

Re: [WebERP-developers] Inventory in Manufacturing

[webERP D. <web...@li...>]

Hi Bob,

Yes I have applied this change to the trunk already. Let me know if you 
want me to help with this...

Phil

Phil Daintree
Logic Works Ltd - +64 (0)275 567890
http://www.logicworks.co.nz
skype:daintree


On 09/07/13 03:46, webERP Developers wrote:
> Phil,
>
> I think that changing the work order receive code is the way to proceed.
> The following scenario might possibly work:
>
> 1) Remove the material issue function.  It is only a means to allow for
> tracking inventory location and issuing whole batches.  There are too many
> problems with the batch issue to make it a viable solution.  If one needs to
> keep batches isolated, the existing method might be somehow forced to work,
> but the shop discipline is too difficult to implement.  One can only manage
> one batch at a time.  The users must keep track to the side on the usage and
> then issue the next batch.  Scrap is not handled at all.
>
> 2) If batch or serial numbered items are in the BOM, a special receiving
> function is needed.  In the receiving function, the user would enter the
> serial number or batch of the components used in the new serial/batch
> controlled item.
>
> 3) A check should be made when creating a BOM that the item being created
> matches the control type of the strictest component in the BOM, i.e. an
> uncontrolled item can't require a controlled and a batch controlled item
> can't require a serial numbered item.
>
> Bob Thomas
>
> P.S. I had submitted a simple change to item issue to code to insure that
> only items that existed are available for issue.  The system always keeps a
> record of where serial numbered items have been stored.  When an item is
> removed, the location/serial number pair is set to quantity zero.
>
> 4.10.1 WorkOrderIssue.php
>
> 			$SerialNoResult = DB_query("SELECT serialno
> 										FROM stockserialitems
> 										WHERE stockid='" . $_POST['IssueItem'] . "'
> 										AND loccode='" . $_POST['FromLocation'] . "'",
>
> Corrected Code:
>
> 			$SerialNoResult = DB_query("SELECT serialno
> 										FROM stockserialitems
> 										WHERE stockid='" . $_POST['IssueItem'] . "'
> 										AND loccode='" . $_POST['FromLocation'] . "'
> 										AND quantity>  0",
>
>
>
> --
> View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Inventory-in-Manufacturing-tp4656561p4656581.html
> Sent from the web-ERP-developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>