Report Quantity - End Activity - Too Many complete serial numbers specified

Kinetic ERP
1

Hi,

We are using ‘Report Quantity’ to report pallets of units into stock, but stays logged into the activity, as the packing operation is ongoing.

The ‘Report Quantity’ button is working as expected in MES, however, when I come to eventually end the activity via the ‘End Activity’ button I get the following error:

image

This is the details:

Form Name: MES Menu
Customization Name: 
Menu ID: Erp.Menu.Mes
Software Version: 11.2.200.33

============

Business Layer Exception

Too many complete serial numbers specified.

Exception caught in: Epicor.ServiceModel

## Error Detail ##
============

##!Correlation ID:##!  38aa2b19-bb7d-4c3e-b1bf-bbe46aa84c38
##!Description:##!  Too many complete serial numbers specified.
##!Program:##!  Erp.Services.BO.Labor.dll
##!Method:##!  validateSerial
##!Line Number:##!  15399
##!Column Number:##!  13
##!Table:##!  LbrScrapSerialNumbers

Client Stack Trace ##
==================
   at Ice.Cloud.ProxyBase`1.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
   at Ice.Cloud.ProxyBase`1.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Ice.Cloud.ProxyBase`1.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Erp.Proxy.BO.LaborImpl.Update(LaborDataSet ds)
   at Erp.Adapters.LaborAdapter.OnUpdate()
   at Ice.Lib.Framework.EpiBaseAdapter.Update()
   at Erp.UI.App.EndActivityEntry.EndActTransaction.Update()

The only way I can end activity is via process in the Conversion Workbench, which is not a workable solution on the shop floor.

The impact of this means that ‘Report Quantity’ cannot be used for serialized products.

I have spoken to Epicor and they have recognized this as an issue and linked it to PRB0250265.

The bad news is that this has been a PRB for over three years and is still a problem in 2024.2.

I just wondered whether anyone had come up with a BPM that can resolve this issue, whilst we wait for a fix.

Thanks,

Andrew.

1 Like
3

Slight development - the problem has been moved to ‘general sustaining backlog’.

I’m not sure what that means in terms of delivery time for the fix.

image

1 Like
4

Good news - there is a ETA for the fix

image

1 Like