Hi Enthusiasts,
Currently system is allowing one Customer Part Reference against a part. Means, Customer Part Reference cannot be duplicated, and if we try creating, then system will prompt error like “Customer Part Number Already Exists”. This error is coming from base.
But I need system to allow same Customer Part Reference with unique Customer Revisions. So, I can have duplicate Customer Part Number with distinct Customer Revision.
Any idea on this?
Unfortunately, I believe you are correct. Even though most other places in the system, the Customer Part XRef doesn’t require a Part Revision on your master part. I’ve never really understood this either.
The CustXPrt table includes:
PartNum
XPartNum
XRevisionNum
… but NOT Revision Num. So, you can assign a customer part & revision to the XRef, but it does not link it to a specific PartNum / RevisionNum.
I agree this does seem like a poorly executed piece considering they allow revision control everywhere else. If both companies revision their parts, then our part 12345 Rev 1 should match their 54321 Rev 1.
I would enter an “Idea” in Epicor to request this functionality.
Do these customer parts refer to actual part revisions on your side?
I don’t KNOW this, but my experience indicates that the Customer Part Cross Reference functionality is designed more for the Sales process than for the Engineering process. When a Customer calls up their sales rep and says “I want to order our PN 54321”, the sales rep needs to know what OUR part number that corresponds to… therefore there can only be a 1-1 relationship between XPartNum and PartNum.
On the Engineering side, it can be WAY more complicated. Just because a Customer changes their revision doesn’t mean WE have to change our revision… and just because WE change our revision doesn’t mean the Customer’s revision changed.
As @dcamlin says, this would be a GREAT place for an Idea.
Agreed… but it COULD, and we SHOULD be able to link those cross references accordingly?
If we sell two machines to a customer, one 10 years ago and one 5 years ago. A specific part on the machine has changed revisions in between those two installs. So part 12345 Rev 0 was supplied 10 years ago, 12345 Rev 1 was supplied 5 years ago.
The customer could send in an order for part 12345 Rev 0 (reasons for part revisions are up for debate… so, not going to get into that)… but they want an EXACT REPLACEMENT. Epicor allow us to have multiple approved revisions. They also allow us to choose the part revision on the sales order line. So, we know we need to make 12345-R0.
If the customer also revision-ed THEIR part number 54321 to match so they knew what they were ordering, but…
There is no way for us to tie customer part:
54321-R0 = 12345-R0 and
53421-R1 = 12345-R1
I think we all agree… the fact that Epicor allows for multiple approved revisions… and even allows us to track customer part revisions (they have the XRevisionNum column)… they could still keep it a 1-to-1 relationship, we just need a second (optional) key so PartNum / RevisionNum = XPartNum / XRevisionNum
May or may not be. I am not sure exactly. I got this requirement to check the technical feasibility.
For an instance, I have proposed another idea.
When user enter Customer Part in the newly added text box (UD field) and hit save button, we can concatenate the customer part number and customer revision and fill it into the original Customer Part Number text box.
Ex:
Customer Part (Custom textbox): PartABC
Customer Rev: 01
Customer Part (Original textbox): PartABC~01
But this proposal was unsuccess!