Preventing Duplicate lot#'s on Scan receive

Hi ​@JWS539 

For customising the WMS in Acumatica, it is a bit different, I recommend reading the knowledge base articles:

How to customize the new Automated Warehouse Operations Engine in Acumatica ERP 2021 R1 and later: Barcode Driven State Machine architecture | Community

It is a lot of trial and error but, you want something like this for tour graph extension

using RecBase = PX.Objects.IN.WMS.INScanRegisterBase<INScanReceive, INScanReceive.Host, INDocType.receipt>;
using WMSBase = WarehouseManagementSystem<INScanReceive, INScanReceive.Host>;
using qtySupport = PX.BarcodeProcessing.BarcodeQtySupport<INScanReceive, INScanReceive.Host>;
using Mode = PX.Objects.IN.WMS.INScanReceive.ReceiptMode;

public class YourExtensionName = YourScanGraphName.ScanExtension //Graph Extension Declaration

{

 //Override the ScanState
 [PXOverride]
 public ScanState<INScanReceive> DecorateScanState(
 ScanState<INScanReceive> original,
 Func<ScanState<INScanReceive>, ScanState<INScanReceive>> originalMethod)
 {
 var state = originalMethod(original); //Get the current state of the barcode engine
 if(state is RecBase.LocationState loc)//You might need a different state
  {
    loc.Intercept
       .GetByBarcode
       .ByOverride((rawBarcode /*Parameter for the input of the barcode*/, defaultParser /*Parameter for the DAC entry*/) =>
    {
     //Your Logic Here
    });
  }
 }

}

Hope this helps!

Hi ​@aiwan 

Thanks for taking the time to review this problem and for setting me on the right track.  After a bit of trial and error have come up with the below which is closer,

One issue though, the PXSetPropertyException is causing issues.  After entring 3 different lo#’s the form is in the state shown below:

Then if the next entry is a duplicate (1234y), an error message get’s correctly displayed, however, problem is all of the lines disappear,

The behaviour we are needing to achieve is that duplicate lot number gets rejected (with the error message) and the details grid stays the same.  So I’m guessing we need to do something other than throw the exception.

Any ideas,

Thanks,

JOhn.

Hi @aiwin,

Thanks for the additional info. Really appreciate the “in-parallell” learning

Had a good read of the Barcode-Driven Engine Guide very interesting.  

Have taken your code snippet and come up with the below which is closer to the answer:

Next issue, which I’m still working on is that the Messaging from Line 36 above(highlighted) isn’t being displayed.  The screen shot below shows what happens on  a rescan of a duplicate lot#

  The message I was attempting to display was “Lot Number 1234z” is a duplicate”.  The barcode not found message appears to be coming from the implementation of InventoryItemState:

My current theory is that when the custom validation.Fail is being called on the LotSerial# in INScanReceiveExt,  the standard logic is automatically resubmitting the lot # as an inventoryID, and this is then failing as there is no InventoryID with the same lot#.

To further substantiate this theory, if you enter in the InventoryID as the Lot#, the standard logic seems to get past the Lot#/InventoryID issue above and displays the correct messaging

Still working on it but I think that some how we need to back up the state, or somehow Stop the Lot# being passed back as an InventoryID

Thoughts?

Thanks,

John.

​@JWS539 

Parallel learning is always fun, sometimes AI can be helpful with this stuff as a start but as soon as you get to the more complex stuff it starts to hallucinate.

It is quite confusing for me too, but I am starting to wonder whether the input between these two stages (Inv. Item & Lot/Serial) dictates what state the barcode engine goes to.

Might be worth trying to push the validation in Inv Item state too.

If you would like, shoot me a private message and I’ll share my email. Happy to take this off-piste!

Aleks