Yes... The bug is that the BOM flag stays on for the part
even if the latest revision has no bom and routing. Then
when you do a rollup, the parent tries to get the cost from
the methods of the child which do not exist. Right now
the only way to fix this is with Provision and take the
BOM flag off. You can easily test this yourself.
Eric Tolliver wrote:
even if the latest revision has no bom and routing. Then
when you do a rollup, the parent tries to get the cost from
the methods of the child which do not exist. Right now
the only way to fix this is with Provision and take the
BOM flag off. You can easily test this yourself.
Eric Tolliver wrote:
>
> Joe,
>
> Did you have a set of standard prices set up for the part, and or a purchase
> price set in the part master?
>
> Eric Tolliver
> IT\MIS
> Continental Industries Inc.
> 5456 E. Mcdowell Rd.
> Mesa, Az 85215
> http://ciirelays.com/
> mailto:e.tolliver@...
>
> -----Original Message-----
>
> FYI...
> ------------------------------
> 11-06-2000
> Joe,
>
> I have submitted this to development as a bug. I will let you know what
> they decide, if it is a bug or an enhancement.
>
> part tracker - new revision changed a manufactured part to a purchased
> part
> - unapproved old revision - BOM still marked as yes - cost roll up
> doesn't
> roll up when this part is entered into another BOM - tested on 00_MFG
> part
> number
>
> why does the bom flag stay on when the most current revision does not
> have a
> bom - it has been changed from a mfg to pur part
>
> MFG parts being changed to PUR parts and the flag stays marked as BOM
> yes -
> If you use this pur part as a material in a BOM underneath a parent part
> the
> cost comes in as 0 when you do a cost roll up.
>