> if (percScrapFactor.compareTo(bdHundred.negate()) > 0 &&
> percScrapFactor.compareTo(bdHundred.negate
> ()) < 0)
>
When the above condition fails,
> oneChildNode.setScrapFactor(percScrapFactor);
>
will set the scrap factor as 1, thus ignoring the original scrap factor
value.
This is a bug.
BJ Freeman wrote:
>
> you should still get a value from the try
> oneChildNode.setScrapFactor(percScrapFactor);
> what was the
> BigDecimal percScrapFactor = node.getBigDecimal("scrapFactor");
>
>
> james_sg sent the following on 2/20/2010 7:42 AM:
>> I think the reason why the scrap factor is not used because the following
>> code in BOMNode always returns to false.
>>
>> if (percScrapFactor.compareTo(bdHundred.negate()) > 0 &&
>> percScrapFactor.compareTo(bdHundred.negate()) < 0) {
>>
>>
>>
>> james_sg wrote:
>>> Hi,
>>>
>>> I have set the scrap factor for a product component in BOM, but this
>>> scrap
>>> factor is not reflected when doing the BOM simulation.
>>>
>>> This problem occurs in both the trunk and 9.04 release.
>>>
>>> Regards,
>>> James
>>>
>>
>
>
>
--
View this message in context:
http://n4.nabble.com/Scrap-Factor-tp1562477p1563330.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
