[
https://issues.apache.org/jira/browse/OFBIZ-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843568#comment-13843568 ]
Christian Carlow commented on OFBIZ-5420:
-----------------------------------------
I'm trying to determine how order item BOM component price info should be stored. BOM component quantity, prices, and descriptions will minimally need to be tracked. The quantities will of course will be calculated based on the parent product quantity and automatically set.
An entity such as OrderItemBom with orderId, orderItemSeqId, productId, productIdTo, price, quantity, and description as fields could be created to provide such functionality.
My other thought was to have BOM components be added to the order as order items and have OrderItemAssoc records for them relating each BOM component order item with its parent. For such cases an extra orderItemAssocTypeId such as "BOM_ITEM" would need to be used to adequately represent the relationship.
Using an OrderItemBom entity seems much easier. If OrderItemAssoc were used then logic dealing with getting the list of order items would have to be recoded to account for BOM order items that should be grouped with their parent order item instead of being lists as a normal order item.
Anyone have any thoughts?
> 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
