We currently are at the latest release 10.2.300.6 - we are a cloud dedicated tenant and are still in Unit Testing.
We have discovered an issue: When performing a Cost Rollup using the Costing Workbench the “Costing Lot size” do not load with the accurate “Costing Lot size” when performing Actions, Load Cost Details.
I have been in contact with Epicor support and after 2 months they gave me the following.
"To get the information expected, after Load Cost Details and ran the process to get the parts on the Costing Workbench, if the Cost Lot Size does not match with what is on the Part Entry (PartPlant.MfgLotSize field)
Go to Actions > Refresh Cost Details and check Purchase Parts, Labor Rate and Burden Rate to refresh the information and that will trigger the correction on the fields."
Note: This did bring in the correct lot sizes.
Does this happen with the standard On-Premise version also?
We’re on-prem on 10.2.300.4 and this is an issue for us as well. The workaround you mentioned worked to resolve our issue. Reviewing a BAQ against a costing group comparing the CostPart and PartPlant costing lot sizes there seems to be no consistent pattern I can detect. But indeed, running refresh with the options mentioned selected syncs them up.
Did they happen to mention if they were working on a fix for this?
They are NOT working on a fix.
The developer at one point said it was working as designed. “It is taking the lot size from the parent part and not itself.”
I do not like this work around, leaves room for error.
We had the same issue in 10.2.100.34 was raised in July 2019 as and it was fixed in 10.2.100.38 (Mid August 2019) we are now on 10.2.400.20 and the problem isn’t there. I assume the fix was applied to the latest patch release for each .xxx release but I may be wrong. Support requested a fix for us at the level we were currently at and it came out 4 patches later.