Christian, The 'deliverable products' associated to a routing task are intended to be able to register by-products on a production run, leading to inventory change.
Follow this example: Suppose there is the production schema for manufacturing metal washers of 1mm thick from a bar of steel. The production schema consists of only 1 task, cutting steel bar. The bom has only 1 component per 1mm thick washer, namely 1.2mm of steel (coming from the bar of steel). Now when executing the production run of 1 washer, your input will be 1.2mm of steel (leading to the cost of production) and output is 1 washer (costing 1.2mm of steel + cutting cost). If that would be all, you would be done. But there is also the by-product, namely the steel cutting residue. This you can't set as output of the production run, as you can only define 1 end product. You can define manually it on a running task as output, but if you know that there will a by-product you better have registered on a predefined task so it won't be forgotten when the production is executed. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sat, Feb 1, 2014 at 9:44 PM, Christian Carlow <[email protected] > wrote: > > But, if your business process(es) regarding the quality inspection of the >>> products have the requirement that forms need to be filled out that are >>> specific to that process and need to be done by other persons than those >>> in >>> the manufacturing process then you will need something else than just the >>> functionalities in the manufacturing component. >>> >>> The inspection tasks do require forms to be filled out and I'm trying > to determine how this should be handled. Aren't "Deliverable Products" of > Routing Tasks supposed to link to forms, documents, etc? >
