Product Configurator & Standard Cost

Yahoo Archive
1
Both solutions work well. I decided to use the GetPartDefaults().
Thank you for the input.


BB



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Kirstin Brandt
Sent: Wednesday, August 11, 2010 1:45 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Product Configurator & Standard Cost





If you need to stay at standard cost, you could try only including one
(middle-priced) part in your configured BOM instead of the subassembly
with all 25 parts, then replace it with the actual part needed in the
rules using: set field quotemtl.partnum = yourpart, set field
jobmtl.partnum = yourpart, and rule function GetPartDefaults().

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , Mark
Wonsil <mark_wonsil@...> wrote:
>
> Hi Bruce,
>
> > I have a new Product Configuration that chooses one of 25 part
numbers
> > from a lower level BOM based on the options chosen in the upper
level
> > BOM. Being a standard cost environment, the lower level BOM with 25
> > different configurations as materials rolls up with roughly 25x the
> > actual cost. I anticipate a few of these situations and want to
avoid
> > the cost getting rolled up inadvertently.
>
> We have taken the advice of others on the list and make our
> configurator BOMs AVG-costed parts. We still use standard costs for
> all of our purchased and manufactured and stocked sub-assemblies.
>
> Because the cost of metals has been fluctuating greatly these last
> couple of years, we changed our roll-up process. First we load the
> purchased parts but at their LAST price. We then pull in the
> manufactured parts at standard and then we do the cost-roll-up.
>
> Mark W.
>





[Non-text portions of this message have been removed]
2
I have a new Product Configuration that chooses one of 25 part numbers
from a lower level BOM based on the options chosen in the upper level
BOM. Being a standard cost environment, the lower level BOM with 25
different configurations as materials rolls up with roughly 25x the
actual cost. I anticipate a few of these situations and want to avoid
the cost getting rolled up inadvertently.



Is there a way to identify parts to be excluded from a manufactured cost
roll? For instance could I identify 24 / 25 parts as "Do not consider
part of parent cost"?



[Non-text portions of this message have been removed]
3
Hi Bruce,

> I have a new Product Configuration that chooses one of 25 part numbers
> from a lower level BOM based on the options chosen in the upper level
> BOM. Being a standard cost environment, the lower level BOM with 25
> different configurations as materials rolls up with roughly 25x the
> actual cost. I anticipate a few of these situations and want to avoid
> the cost getting rolled up inadvertently.

We have taken the advice of others on the list and make our
configurator BOMs AVG-costed parts. We still use standard costs for
all of our purchased and manufactured and stocked sub-assemblies.

Because the cost of metals has been fluctuating greatly these last
couple of years, we changed our roll-up process. First we load the
purchased parts but at their LAST price. We then pull in the
manufactured parts at standard and then we do the cost-roll-up.

Mark W.
4
If you need to stay at standard cost, you could try only including one (middle-priced) part in your configured BOM instead of the subassembly with all 25 parts, then replace it with the actual part needed in the rules using: set field quotemtl.partnum = yourpart, set field jobmtl.partnum = yourpart, and rule function GetPartDefaults().

--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> Hi Bruce,
>
> > I have a new Product Configuration that chooses one of 25 part numbers
> > from a lower level BOM based on the options chosen in the upper level
> > BOM. Being a standard cost environment, the lower level BOM with 25
> > different configurations as materials rolls up with roughly 25x the
> > actual cost. I anticipate a few of these situations and want to avoid
> > the cost getting rolled up inadvertently.
>
> We have taken the advice of others on the list and make our
> configurator BOMs AVG-costed parts. We still use standard costs for
> all of our purchased and manufactured and stocked sub-assemblies.
>
> Because the cost of metals has been fluctuating greatly these last
> couple of years, we changed our roll-up process. First we load the
> purchased parts but at their LAST price. We then pull in the
> manufactured parts at standard and then we do the cost-roll-up.
>
> Mark W.
>
5
We also pull in our last price for purchased parts. Right now we:

1) Run a report showing all purchased parts where last price <>
standard price

2) Export to Excel

3) Review significant differences

4) Grid Entry Cost Adjustments

We then run the mfg roll similar to you. Has using these multiple
methods (LIFO for purchased, Avg (or FIFO) for Product Configurator
parts, and Standard for everything else) caused any CPA / Audit
headaches?



Also, I am interested in hearing about your LIFO purchased parts
process.



Thank you,



Bruce B.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Wednesday, August 11, 2010 6:30 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Product Configurator & Standard Cost





Hi Bruce,

> I have a new Product Configuration that chooses one of 25 part numbers
> from a lower level BOM based on the options chosen in the upper level
> BOM. Being a standard cost environment, the lower level BOM with 25
> different configurations as materials rolls up with roughly 25x the
> actual cost. I anticipate a few of these situations and want to avoid
> the cost getting rolled up inadvertently.

We have taken the advice of others on the list and make our
configurator BOMs AVG-costed parts. We still use standard costs for
all of our purchased and manufactured and stocked sub-assemblies.

Because the cost of metals has been fluctuating greatly these last
couple of years, we changed our roll-up process. First we load the
purchased parts but at their LAST price. We then pull in the
manufactured parts at standard and then we do the cost-roll-up.

Mark W.





[Non-text portions of this message have been removed]