Never had a PRB acccepted and then rejected later (after 19 months). I guess I’m officially an old hack now.
So I’ll put this out there as informational. No need to put in a ticket if you encounter the same.
Here was the situation. Notice this is about a supplier part, not a customer part, that is affecting a sales order.
New sales order
Add line
Enter part number 750878 (this number is not in our Part Master)
Epicor replaces 750878 with part number 42298, and we cannot override it on the sales order
We don’t want to sell 42298. We want to sell 750878. But we can’t.
Incidentally, 750878 represents a truck costing tens of thousands of dollars. 42298 is a fitting that costs $7.38
I know the explanation: One of our suppliers uses 750878 as their number that cross-references to our 42298. But why should that stop me from selling something we call a 750878?
I tested this again in 10.2.300 and still find it to be the case.
It’s also tricky if I want to make 750878 a real part. I tend to create a new part in Part Entry by NOT clicking the New button but simply entering the new part number into the box on an empty form. In this situation, that doesn’t work; it just loads 42298 instead. I must use the New button in that case.
Another solution is just not using cross-references (technically it’s a Supplier Part, found in Supplier Price List). There are other drawbacks to that anyway.
I don’t doubt it’s happening but you said this was Sales Order Entry and not Purchase Order Entry. For giggles and shirts, see if you find that part number in CustXPrt. I’ve seen some of this behavior because this table is auto-populated when someone enters a customer part number. Maybe the Supplier XRef is doing something too. If so, you could remove that xref and add leading text to it like “supplier_name:750878”
Oh sure, there are ways around. What I hate is when I enter one thing and it gets transformed into something else with no warning pop-up or anything. Then we are asking,
“Why did you sell them a $7 fitting instead of a multi-thousand-dollar new truck?”
“I did it right, I promise! The system is crazy!”
“Sure…”
I’m really not concerned for myself. It hasn’t been an issue since then (March 2018). We set up procedures to avoid it and the xref happened to be a typo. I’m more likely to get a front-row spot at Walmart than see this problem happen to me again.
So I don’t want you to take time on this for my account. But if you are curious for other reasons, then sure.
What is the work around that you have for this? I have a client who paste inserts lines into their Sales Order and if there is a Supplier XRef then it uses this instead with no warning!
For us - and I think for anyone, right? - the problem is when you want a part on the sales order that is NOT in the part master. AKA a “part on the fly.”
We used to do that every day, using a POTF on a sales order. Now it is incredibly rare and when we do actually use a POTF, it’s like a sentence, like Trailer Refurb For TT1066. That’s the part “number,” not the description (though it’s probably identical to the number anyway) - so there is like no way that we accidentally hit a cross-reference.
If you are curious, the procedure used to be that sales would enter a (soon to be) new part number as a POTF on the order, and then Engineering would create the Part record for it. (It’s interesting, Part Entry grabs the description from Order Entry in that case.) Because Engineering would take an eternity to get around to making the number.
But now I just let the person in sales create the part herself before entering the order. She just duplicates an old one. Works fine. She hasn’t messed up since we changed it, what, two years ago?