In Part Tracker i have a part when it is entered launches the part cross reference selection pop-up window.
Fine we have plenty of parts with various cross references.
But for this one there is only one record in the results window of the pop-up and it is of the Part Master type.
Any ideas?
I have dug into:
PartXRefInt - nothing
PartXRefMfg - nothing
PartXRefVend - there are two records but not returned
What about it being a Customer’s P/N? I think that’s in table CustXPrt
There was a reference there that was not needed. I deleted it so I am still getting the pop-up.
It is just strange that the only record returned is a type Part Master.
Is it strange that in the window the record doesn’t have a value for ID or Name? or is that because the type is Part Master.
Eric, what are you asking here… is there a problem?
What is the problem? Is it that you are seeing this pop up and you aren’t for other parts?
Or is the problem that you aren’t seeing all of the cross references you are expecting to see?
In short, what is the problem you are facing?
The problem is the fact the pop up is happening and the only record is the same value as what is entered into the PartNum field. So you have to then select the record with the same partnum value. So it is 2 more clicks.
This seems to be an isolated issue at this point. The business hasn’t come forward with any other instances of superfluous cross reference selection pop ups.
Alright, thanks for clarifying.
I have seen this happen if the original part in the Part table has a SPACE at the end of the part number… it LOOKS like it is the same, but it is actually different. The only way to figure this out is if you check the actual database, and / or do an extract of both the Part table and the cross reference table and check the field’s string length.
@timshuwy thanks for the idea.
I then looked at the field len of the PartNum fields in all of the usual places and they all came back with a LEN of 9 (as expected). So epicor support suggested I run conversion 1420. I did. And looked at SQL again and nothing changed. And the pop up is still happening.
Good morning @Eric_Howell. Check out the following, perhaps you are seeing the same issue.
KB0109825 - Customer Cross Part Reference changes when used in Job Entry
Hey Scott.
I see what you are thinking, but this is happening when I enter a part master partnum into Part Entry.
It isn’t a part on the fly situation as far as I can tell.
ok so I have had some back and forth with Epicor Support. After running a trace log and turning on all of the options there, here is what I get back:
<tracePacket>
<businessObject>Erp.Proxy.BO.PartImpl</businessObject>
<methodName>GetPartXRefInfo</methodName>
<appServerUri>xxxxxxxxxxxxxxxxxxxxxxxxx</appServerUri>
<returnType>System.Void</returnType>
<localTime>11/30/2021 10:22:07:3366436 AM</localTime>
<threadID>1</threadID>
<correlationId>044d79c5-1924-4865-bd4f-81ca6df7d386</correlationId>
<executionTime total="14" roundTrip="11" channel="0" bpm="0" bpmDataForm="0" other="3" />
<retries>0</retries>
<parameters>
<parameter name="partNum" type="System.String"><![CDATA[224-01222]]></parameter>
<parameter name="SysRowID" type="System.Guid"><![CDATA[00000000-0000-0000-0000-000000000000]]></parameter>
<parameter name="rowType" type="System.String"><![CDATA[]]></parameter>
<parameter name="serialWarning" type="System.String"><![CDATA[]]></parameter>
<parameter name="questionString" type="System.String"><![CDATA[]]></parameter>
<parameter name="multipleMatch" type="System.Boolean"><![CDATA[False]]></parameter>
<parameter name="CallContext" type="Ice.Bpm.Context.ContextDataSet">
<ContextDataSet xmlns="http://www.epicor.com/Ice/300/Bpm/Context">
<BpmData>
<SysRowID>00000000-0000-0000-0000-000000000000</SysRowID>
</BpmData>
</ContextDataSet>
</parameter>
</parameters>
<returnValues>
<returnParameter name="serialWarning" type="System.String"><![CDATA[]]></returnParameter>
<returnParameter name="questionString" type="System.String"><![CDATA[]]></returnParameter>
<returnParameter name="multipleMatch" type="System.Boolean"><![CDATA[True]]></returnParameter>
</returnValues>
</tracePacket>
The line of interest is
<returnParameter name="multipleMatch" type="System.Boolean"><![CDATA[True]]>
Now if we could figure out why for my part this is returning a TRUE value…
Did you find a solution to stop the box from popping up?
I have the exact same issue in 2023.2.9 that just started. It does not do it in our test environment from August but does happen in production.
I also have checked all the tables, and the part is not referenced, but my trace log looks the same as yours where it is seeing a multiple match.
I have an open ticket with Epicor, but they are recommending a consultant to fix this. Hoping you found a different solution.
did you check internal part cross reference as well as customer part cross reference?