[
https://issues.apache.org/jira/browse/OFBIZ-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850640#comment-13850640 ]
Christian Carlow commented on OFBIZ-5420:
-----------------------------------------
I decided to create the OrderItemBom entity to handle this functionality. I created a bom.ftl to support BOM item pricing the same way that productdetail.ftl is used to support Virtual item variant selection. When the bom.ftl page is displayed, the component products description and price fields should be set to their default values.
I think much of the logic contained in ShoppingCartItem.updatePrice() should be used for each of the BOM components to determine the default price. Because ShoppingCartItem.updatePrice() ends up setting the the list, base, display, and specialPromo prices for the item, those fields might need to be added to BOMNode since the BOM components are associated with the item as a List<BOMNode> class member. Adding surveyResponses might also need to be added to BOMNode since it is used in the price calculation or ShoppingCartItem.
> Add ability to separately price BOM elements for orders
> -------------------------------------------------------
>
> Key: OFBIZ-5420
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5420> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: SVN trunk
> Reporter: Christian Carlow
>
> I have a scenario where a company individually prices BOM elements of assembled products ordered. So if an item is manufactured from 2 component products, the company needs to be able to specify prices for both of the components to made up the total parent product cost.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
Locked
