In Part Maintenance, we quite often use the functionality of being able to enter in a Customer Part Number and it will automatically resolve to and open Our Part Maintenance record in Epicor instead of prompting us to create a new part number every time.
So, for example, if we typed Customer Part Number: CustPart01 into the Part field of Part Maintenance, Part Maintenance would automatically pull Our Part Maintenance Record of F000RAC01 associated with that Customer Part Number in the Customer Part Cross Reference table.
Since we migrated from Epicor 9 to Epicor 10 it seems that only a handful of Customer Part Numbers are working and bringing through Our Part Maintenance record automatically even though these Customer Parts are in the Customer Part Cross Reference table.
Are we missing any sort of settings on these Parts or Customer Parts to setup this automatic connection between the two parts in Part Maintenance?
Thank you for any help you can provide!!!
-Heather
Heather,
I saw the same thing with some parts when moving from 9 to 10 as well.
I believe it is a known data conversion issue and Iām pretty sure Epicor Support provided a data fix. For awhile after upgrading I found odd data issues related to the case of letters and such.
Thank you @Rick_Bird! I will report this to Epicor as well and hopefully get a data fix for it like you did. I had a bad feeling it might be a data issue from our migration. I kept trying to find a pattern but was never able toā¦even if I delete the record and re-create it in the Part Cross-Reference table I still canāt get it to work. A little scary.
Thanks so much for the quick and helpful feedback! I appreciate it!
And request a Data Health Check from Epicor. It should help identify and fix some of the known issues after conversion. We just ran one on 10.2.100 and it found some cruft from 10.0.700 that we still had.
I wrote myself a note to request that in the near future but the future is NOW! So I will request a Data Health Check and see if it helps us out. Thank you SO MUCH @Mark_Wonsil!
Iāve contacted support about this and the official response was it ever working was a bug and they donāt truly support it because itās a one to many relationship. I built a series of customization to fill the gap. Attached is a solution for those.
Moving to Expertās corner for posterity , since this is a really swanky solutionā¦ Donāt go getting a big head @jgiese.wci LoL
Also you forgot the disclaimer manā¦ get ready to support this for the next 100 years!
I thought I would piggy back on this issue with a further enhancement.
I have added a Pre-Processing Methods Directive to Part.GetPartXRefInfo.
I call it Job Number Lookup Feature:
In my case my production jobs have a āVā prefix, my manufactured parts donāt.
So the Methods Condition is "the PartNum argument begins with āVā.
I synchronously run ABL code.
Define Var sScCheck as Character no-Undo.
MyCheck = āNot Sureā.
find JobHead Where JobHead.Company = Cur-Comp
and JobHead.JobNum = PartNum no-lock.
if JobHead.Jobnum = PartNum then MyCheck = āJobNumberā.
IF MyCheck = āJobNumberā then PartNum = JobHead.PartNum.
OK so now what.
You can enter a production job number in the part number field and it will look up the manufactured part for you.
Solution file wouldnāt help you either still version mismatch with what Iām on. Open the CAB file up and see what is all in there. You might be able to rebuild what I did from that.
