In the PartPlant table, there is a field SLTVendorNum. I wolud like to find out what this is for, and how it is used.
In both of the Classic and Kinetic UI’s, on the “Part Maintenance” form, under “Part > Plant > Detail” there are fields for Purchasing Supplier (which relates to database field ERP.PartPlant.VendorNum) and Urgent Planning Supplier (which relates to database field ERP.PartPlant.UrgentVendorNum).
What, then, is STLVendorNum used for?
Best Regards,
Tom
I second your legitamousness
Except I think there was a transposition… STL vs SLT
Here’s the description from Data Dictionary:
So… not sure it has anything to do with stock transfers.
And the OP question is a good one. When would this (short lead time) SLTVendorNum be used over the UrgentVendorNum?
Perhaps @timshuwy knows?
STOP IT DAVID. I’M TRYING TO VIBE CODE OVER HERE. 
I was never here…
@ThomasR , forgot to welcome you. Welcome!
I am thinking that this might be fields that were intended for functionality they never implemented. Can’t say for sure, but looking at the part, there is Short Horizon planning but no place to put a Supplier. I also looked at the overflow menus and other cards to see if the field showed up anywhere, and I could not find it being used. And as @dcamlin said, there is already the UrgentVendorNum.
Since we just enhanced the urgent planning options, i know that the urgent supplier is used… but not sure what that SLT version is for. I have asked development if they have some history.
ok… just got feedback from the dev team. This field was added to the schema, but never used. we did a code check and there is no-code that references this field. SO… it will be obsoleted in a future release. Thank you for pointing it out to us. please do not use it for anything.
What service! Excellent, thank you very much. I had hoped it wasn’t used, it simplifies my BAQ design not to have to include it.
I’ve never trusted AI to be overly accurate when it comes to ERP systems. I just don’t think they’ve been trained on the right datasets. Maybe if we fed CoPilot studio the entire content of the Epicor LMS, EpicWeb, EpicCare manuals, data dictionary, and this forum, we’d create a resource capable of answering technical questions with more certainty, (as well as surfacing geese when it was unsure).
