[
https://issues.apache.org/jira/browse/OFBIZ-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878284#comment-13878284
]
Christian Carlow commented on OFBIZ-5420:
-----------------------------------------
In my second to last post I asked if BOM items should not ever exist as virtual
products but have since found that the BOM Simulation app includes a virtual
column to indicate if any of the BOM is virtual. This seems to suggest that
BOMs should be able to exist as virtual products and if so there still exists
the problem of BOM variant selections not being supported.
Pierre your mention of BOM costs seems to be the correct way to calculate the
assembled product price. I guess instead of entering individual prices for
each assembly component to make up the total unit price of the final assembled
product, the users would instead need to run the BOM Simulation for the
assembled product and add up the BOM costs to determine the unit price which
would be used to override the auto-assigned order item default price? If this
is the case then one improvement that could save users time would be to add a
total line at the end of the BOM Simulation screen to provide the users with
the total without having to manually calculate it.
> 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
> Attachments: OFBIZ-5420-1.patch, OFBIZ-5420-2.patch, OFBIZ-5420.patch
>
>
> 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.5#6160)
