Difference between revisions of "Talk:Sponsored Development: Libero Product Configuration BOM"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(summarising my BOM tots.)
Line 8: Line 8:
  
 
jsSolutions advised me that the forms are all custom code.  They are defined in the sense that they are identified in the process table.  He advised me to look at some of the examples, like Payment Allocation in the process tab it will define the class or procedure that is called.  Create Lines Form was another he believed that is called from a button on Material Receipt.  Obviously I should be able to borrow heavily from the Drop BOM code.  What is still confusing me is how a product configuration BOM can be more than one BOM in hierarchy, but Victor told me this was possible and I would have to create indentations showing that Bom type structure.
 
jsSolutions advised me that the forms are all custom code.  They are defined in the sense that they are identified in the process table.  He advised me to look at some of the examples, like Payment Allocation in the process tab it will define the class or procedure that is called.  Create Lines Form was another he believed that is called from a button on Material Receipt.  Obviously I should be able to borrow heavily from the Drop BOM code.  What is still confusing me is how a product configuration BOM can be more than one BOM in hierarchy, but Victor told me this was possible and I would have to create indentations showing that Bom type structure.
 +
 +
:Tim, i wonder if u are extending the BOM Drop and BOM structure concept as in Compiere/Adempiere. It is an unlimited multi-level BOM concept where we can have as any levels of sub boms as possible under a single BOM parent. Also the sub BOM can be another parent thus it follows a generation of granny-daddy-son-grandson-and so on. The BOM attributes already cater for what i see as the Variant BOM concept where a BOM child can be part of any defined alternative package, optional for selection during BOM Drop. IMO the BOM Drop should be extended instead of discarded if possible. Its quite a familiar sight for many older users, and all it need is perhaps a Tree View version incorporated into it. regards! - [[User:Red1|Red1]] 01:46, 21 August 2007 (EDT)

Revision as of 22:46, 20 August 2007

Hello Tim Wight (XP_PRG), Marvellous writeup, indeed! A future killer! - Red1 19:50, 15 August 2007 (EDT)

I talked with jsSolutions about how to accomplish my task of creating a form that will come up when a product is chosen that is a product configuration master BOM allowing the user to configure the product configuration for the sale. I suggested that the approach I would take is:

  • define the form in the ad
  • then run GenerateModel.sh to actually make the code to bring the form up
  • then add a callout to the product selection field in the sales order line field of the sales order line tab

jsSolutions advised me that the forms are all custom code. They are defined in the sense that they are identified in the process table. He advised me to look at some of the examples, like Payment Allocation in the process tab it will define the class or procedure that is called. Create Lines Form was another he believed that is called from a button on Material Receipt. Obviously I should be able to borrow heavily from the Drop BOM code. What is still confusing me is how a product configuration BOM can be more than one BOM in hierarchy, but Victor told me this was possible and I would have to create indentations showing that Bom type structure.

Tim, i wonder if u are extending the BOM Drop and BOM structure concept as in Compiere/Adempiere. It is an unlimited multi-level BOM concept where we can have as any levels of sub boms as possible under a single BOM parent. Also the sub BOM can be another parent thus it follows a generation of granny-daddy-son-grandson-and so on. The BOM attributes already cater for what i see as the Variant BOM concept where a BOM child can be part of any defined alternative package, optional for selection during BOM Drop. IMO the BOM Drop should be extended instead of discarded if possible. Its quite a familiar sight for many older users, and all it need is perhaps a Tree View version incorporated into it. regards! - Red1 01:46, 21 August 2007 (EDT)
Retrieved from "http://www.adempiere.com/index.php5?title=Talk:Sponsored_Development:_Libero_Product_Configuration_BOM&oldid=33242"