So we are doing some final testing and one of the users found that the expiry date process was not firing on a part. We checked the data load information and we has the part set as Expiry Date required on the Part (LotExpDt set to 1) and checking the DB this has been set. Now when i check Kinetic on the Lots menu, the Expiry Date field seems to be in a different format. It comes under the attributes section and is either N = Not Tracked, T = Tracked or M = Mandatory and the field is AttExpDt. Looking at this further all the system processes for using LotExpDt have gone as when i try and book something in or adjust a quantity where that is set to 1 on the part it doesnt ask for export details?
Am i missing something here or has this fundamental process changed?
When we set expiration dates it is done at the lot level. Look in PartLot.ExpirationDate. You do have to set the lot to require expiration dates in Company Configuration > Modules > Materials > Inventory > Lot. You can also set the Lot Attributes that are required by part, in Part Entry > Lots > Attributes.
Once you set that up, and create the lot, you can define the expiration date, and it gets saved in that field.
I made a BAQ to investigate the expired lots. ExpiringLots.baq (53.3 KB)
At the same time though the old DB fields have been left in the Kinetic DB so when we have loaded parts with Lot Attributes attached to them from E9 into Kinetic via DMT, no errors have been thrown and therefore we were non the wiser of any issues. Unfortunately the data that has been loaded is now useless as it seems the 'Expiry Date processes work off the new fields!
You should still be able to extract that lot data and setup the lot records for import with DMT. Not saying it will be easy, but I believe it is doable. Or you can try your luck with Epicor support.
If you can get a BAQ to show you the expiry data from your old fields, then you can use that data to create a DMT import file. Use the Inventory > Part > PartLot DMT template.
Someone else jump in here If I am sending Dan down the wrong path. This is what I would try before dealing with support.
Even more so when the data you are dealing with is that bad and include loads of issues that you cannot use the Sirus tool and have to do everything via manual DB extracts and DMT
