Buying "Intelligent" part numbers

Yahoo Archive
1
We do something like this but with our products, not the products we purchase.Â
It required using two UD tables, one with "Base Pricing" and the other with
"Option Pricing". When a part is entered into a sales order (either manually or
through the configurator), the price is calculated from these two tables based
on the smart part number. It took a considerable amount of programming to get
it to work (BPM, 4GL, and customizations), but it was well worth the effort
considering just one of our base models could have thousands of permutations
based on available options.

I imagine the same approach would work in your case and probably would not be as
much work as what we did.




________________________________
From: Ken Williams <kwilliams@...>
To: "vantage@yahoogroups.com" <vantage@yahoogroups.com>
Sent: Wed, February 9, 2011 3:18:12 PM
Subject: [Vantage] Buying "Intelligent" part numbers

Â
A few of our products we purchase are based on an intelligent design. That is,
they share a common root, followed by extensions to denote size (copper wire for
instance to denote width). This would be similar to what the Product
Configurator offers for internal usage.

I've been asked "can Epicor allow us to put the base in with vendor pricing and
have it use that pricing regardless of the extension that follows?"

Our practice to this point has been to enter every part number - this has lead
to hundreds of numbers across all the product lines that this could be applied
to. Managing it is getting difficult at best.

I don't recall seeing anything like this for vendor/purchase direct
transactions. Am I missing something? Has someone come up with a clever way of
doing this?

Thanks for any ideas,
Ken Williams

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






____________________________________________________________________________________
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265

[Non-text portions of this message have been removed]
2
A few of our products we purchase are based on an intelligent design. That is, they share a common root, followed by extensions to denote size (copper wire for instance to denote width). This would be similar to what the Product Configurator offers for internal usage.

I've been asked "can Epicor allow us to put the base in with vendor pricing and have it use that pricing regardless of the extension that follows?"

Our practice to this point has been to enter every part number - this has lead to hundreds of numbers across all the product lines that this could be applied to. Managing it is getting difficult at best.

I don't recall seeing anything like this for vendor/purchase direct transactions. Am I missing something? Has someone come up with a clever way of doing this?

Thanks for any ideas,
Ken Williams


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