Difference between revisions of "Talk:Sponsored Development: Libero Product Configuration BOM"
| Line 1: | Line 1: | ||
Hello Tim Wight (XP_PRG), Marvellous writeup, indeed! A future killer! - [[User:Red1|Red1]] 19:50, 15 August 2007 (EDT) | Hello Tim Wight (XP_PRG), Marvellous writeup, indeed! A future killer! - [[User:Red1|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. | ||
Revision as of 18:16, 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.
