Hi folks!
This HAS TO BE commonly irritating to us all I’m assuming, but thought I’d ask if there were any other observations.
For a part, why is there no basic “Name” field. Since the Description is used on sales orders and everything, it’s very inappropriate to actually put the verbose long description for a part in that box – that would be a mess!
Like most systems shouldn’t there be a part name and then a separate field for a verbose long description of the part??
Thanks!
We’ve tackled this using alternate languages.
So, you have your Part Number… the “engineering” description goes into the typical description field.
Then was created a custom language in Language Maintenance:
Then… on the Part Record, you can enter BOTH:
Next… set your Customer’s Language to your “Sales Description” language… and that is the description that will appear on your quote.
So, internally, our forms use the “Engineering Description”. But Customer facing documents use the “Sales Description”
This is super clever
I struggle with this as I believe that the description should be a short description and you have the MOM to understand the details. Why make such a verbose description when there are already details attached to the revision? If you enter a verbose description and then change the details of the MOM, who is actually going back and updating the description? For off the shelf parts, I always push to enter the manufacturer part number if it is a sole source or to attach mfg numbers/supplier numbers to the part number if there are multiple sources.
Now, if you are talking about retail goods, then yes, I agree there are not enough descriptions in Epicor to support what the customers are asking for.
Yes, normally reusing/repurposing Epicor fields seems risky, but in this case, it seems like it should be perfectly fine since he is creating his own ‘language’. Very clever.
For us, we are make to order, and we want a long description that contains every detail the customer gave us, so they can confirm we got all the details right, and then we want something more concise to fit on a tiny tag and only needs enough detail people can figure out which item it is.
Doesn’t necessarily need to be long and verbose.
The engineering description may contain propriety information that we don’t want the end customer to see.
If it is a resale part that we purchase from an outside manufacture and then sell to the customer… we don’t necessarily want them to see the original OEM part number. If they do, they’ll just buy direct from them next time and we won’t get the order.
We did discover that we can use the “English” language for this but didn’t want it to affect sales orders and customer facing documents where a customer was bound to that language.
However, creating a new language is the HOT TIP here! Kudos. We just tried it, creating a new language of “Sales/Technical Description” and added it to our relevant BAQ and we’re in business. 
Don’t forget to mark the solution 
Edit: ah you just did
That is when you use the Supplier/Manufacturer part number functionality.
