Using Epicor 10.1.400.20, Is there a reason I wouldn’t use the same part number as the Customer’s Part Number and our Part Number?
I have a customer that uses their own part number for one part, but not the other parts they purchase. They want us to print special labels when shipping to them. That label needs to show both our part number and their part number. When I print the label for a part that doesn’t have a customer part number, it fails because it’s looking for a matching record in the Customer Part Cross Reference table. I was thinking I could enter our part number again as the Customer’s Part Number, but wanted to see if there’s a good reason not to do that before I do and mess something up.
So Epicor won’t have a problem with doing that? It seems so strange to allow the same number in both fields.
I’m using LabelVision. We are scanning our Part Number on the Material Queue Report and getting LabelVision to look up the customer’s part number in the Cross Reference table. There’s a filter on the label to look for the custnum for this customer and our part number and return the customer’s part number.
It’s a totally different table from the part master table. I don’t think it cares if the PartNum and the XPartNum field match or not. I’ve never used LabelVision myself. How does it get the information for the labels? Is it a SQL query, or a baq report or something? If it’s SQL I’m wondering if you can just get a left join so that it returns all of the PartMaster information, and if there isn’t CustXPrt table info, then it would just come back blank so you’re label wouldn’t fail. If it were me, I would investigate fixing that, because in the long run it will be less maintenance that copying over part numbers just to get the label to run.
