[ https://issues.apache.org/jira/browse/OFBIZ-5307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805175#comment-13805175 ]
Jacques Le Roux commented on OFBIZ-5307: ---------------------------------------- A quote from Swapnil on user ML {quote} Hi Rupert, Have you tried setting up the BoM between Washer (Produced after passing through required operations) and Pipe (as a BoM component or raw material) in ratio of 1 : 0.001. Once you associate the Washer with proper routing and create production run then you should be able to produce 1000 units of washers and stock them in inventory by consuming 1 unit of Pipe (assuming that scrap factor is 0%). I have not tested but MRP would also honor this BoM while generating the Procurement or Production requirement for Pipes based on demand for Washers from downstream operations or safety stock requirements or sales orders or forecast in the supply chain. Thanks, Swapnil {quote} > Reverse/Inverted/Breeder Bill Of Materials > ------------------------------------------ > > Key: OFBIZ-5307 > URL: https://issues.apache.org/jira/browse/OFBIZ-5307 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing > Affects Versions: SVN trunk > Reporter: Rupert Howell > Assignee: Jacques Le Roux > Priority: Minor > Labels: bom, breeder, inverted, manufacturing, reverted > Fix For: SVN trunk > > > Currently the system only allows for 1 product to be made up from multiple > other products. > A common process in manufacturing is to either manufacture multiple parts > from one part (e.g Chop a length of steel that has been ordered in from a > supplier and manufacture your own washers) or to disassemble a returned > manufactured item into its components and restock these components. > The BOM/MRP/ Manufacturing and production run functionality should be changed > to allow for production runs in both ways (assemble / disassemble) > [Associated Nabble > thread|http://ofbiz.135035.n4.nabble.com/Manufacturing-Washers-from-Pipes-td4643707.html] -- This message was sent by Atlassian JIRA (v6.1#6144)