Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

BOMPriceStd function incorrect

Description

The BOMPriceStd function in the Database is incorrect. Though it goes through the BOM Children of a product when the parent price is zero, it only takes children who are themselves parents or having further children. Thus this will only work partially in a 3 tier BOM but taking only the first two and in a 2 tier BOM, nothing.
By removing the isBOM and isVerified check solves it.
The attached patched function only applies for BOMPriceStd testing and if maintainer says OK can do so also for BOMPriceList and BOMPriceLimit.
It only removes these two lines:
AND p.IsBOM='Y'
AND p.IsVerified='Y'

Environment

None

Attachments

1
  • 17 May 2015, 08:48 PM

Activity

Show:

Dietmar Berlinger May 18, 2015 at 7:39 PM

is also necessary in
bompricelist
bompricelimit

thank you!

RedhuanO May 17, 2015 at 9:39 PM

To test this:
1. Create 2 products called BOMChild1 and BOMChild2 with Std Pricelist of 2.00 and 3.00.
2. Create a product BOMParent with zero price, with BOM box checked and in the BOM tab include the above two.
3. Create a Sales Order,
3.1 at OrderLine select BOMParent, the price remains zero.
Apply edited function to DB, repeat 3.1 and the price shows 5.00 which adds up the two child correctly.
You can also test with above steps by just making Patio Set as zero price and select it in Sales Order Line and you see the price only rolls up the PChair = 135, but after patch it is 225 which is taking the PTable into account also.

Fixed

Details

Assignee

Reporter

Priority

Created May 17, 2015 at 8:50 PM
Updated July 1, 2015 at 1:04 PM
Resolved May 20, 2015 at 6:01 PM

Flag notifications