Demand Entry - Multiple Cross Reference

Hello fellow EDI people…

Does anyone know how this gets flagged? I see one entry in customer part cross reference… what is this going off of?

This got rejected by the system, but I’m having a hard time understanding why… anyone have a “cheat sheet” for things to check?

image

Just guessing that you have customer part number cross-reference entries pointing to more than one Kinetic part.

Thanks Mark, I thought that too, but we don’t for this part, which is why I am confused… was hoping someone had decompiled this or traced it out and would be able to let me know the logic behind this… Cause it’s not adding up or making sense.

Take a look in Demand Contract Entry.

When you import a PO this list of parts gets appended or updated based on the Customer/Epicor Part numbers on each PO line. It’s possible you wind up with multiple customer part numbers pointing to the same Epicor part number, etc.

@hackaphreaka , when you say “this list” do you mean demand contract detail table? or the CustXPrt table?

When you go into a demand contract, there is a grid called ‘Contract Lines’

This also contains a list of cross references. The data lives in DemandContractDtl.PartNum, DemandContractDtl.XPartNum.

Check this list for possible multiple cross references.

I’ll check it, but I swear I did

More specifically check the PO you are trying to import and see if it would create a multiple cross reference issue.

Is that the logic? There is no part cross ref for the part, anywhere- in the contract lines nor in custxref

The PO you are trying to import contains both your Epicor Part # and the Customer Part #?

There is no entry for this Epicor part # in Customer Part Cross Reference?

Neither the Epicor Part # nor the Customer Part # exist anywhere in the Contract Lines in Demand Contract Entry?

The EDI document only contains the customer part number, not both. I’ve been meaning to reference the EDI documentation because I find that weird. There is nothing custxpart table and there is no xpartnum in the contract lines.

If you are only getting the customer part, I believe you NEED an entry in Customer Part Cross Reference. How on earth does Epicor figure out the Epicor part number otherwise. Depending on some other settings it will either stop with an error or do something like create a make direct line on the SO with the customer part # in the part # field.

For sure on that, I’m just saying I don’t get why it says multiple part reference- is it because nothing exists and this is technically a new reference so you can either reference it by nothing or by this new way and there’s two reference’s now- hence the “Multiple Part reference”? In any case, thank you for your time.