Underscore not recognized on serial lot after update to 2024 R2

Our first day on 2024R2 and we also encountered this. We cannot issue material from lots with underscores, whether subsequent fields are touched or not - the transformation is immediate upon selection of the lot from the picker. I have tried to avoid the picker as well (typing or pasting the lot id in) with no success.

Hi ​@PBSA ,

This has been confirmed by Acumatica support as an issue in 2024 R2.  I would suggest reaching out to support for help with resolving it in your instance.

Laura

​@lauraj46 I did report it to our resellers. Are you still waiting for a solution from Acumatica? Have you found any workarounds to get these transactions entered?

Hi ​@PBSA ,

I am a reseller - one of our customers is experiencing the issue.  Support is actively testing a fix to update the existing serial numbers with a different character such as a dash or a space.  Your reseller should be able to help you with creating a support case to do similar for your instance.

In the meantime, the only workaround that we found is to issue all of the quantity for an inventory item location (in which case no lot has to be specified), and then receive it back in with the corrected lot numbers.  Be sure to receive with the same qty, cost, expiration date, etc.

Laura

​@lauraj46 does your customer feel comfortable updating records via the database?👀
I have a very dangerous SQL script that I use to fix duplicate serial values since Acumatica allows duplicate serial numbers as long as the InventoryID is unique, but we don’t. 

It would require some modification to work in your case, but it collects tables that contain the LotSerial column, constructs an update statement for each one, then runs all the dynamically generated scripts to update the values.

I have this note at the top of the SQL script.
--WARNING: USING THIS FUNCTION WITHOUT UNDERSTANDING WHAT IT IS DOING MAY POSSIBLY END YOUR CAREER!
--MAKE SURE YOU UNDERSTAND THE OBJECTIVE OF WHICH TABLES ARE BEING UPDATED AND WHICH SERIAL YOU'RE UPDATING TO!

Direct Message me if you need it, because I don’t want to release it to the public, and be held liable for what people do with it!

​@lauraj46 Thank you for your answer. Unfortunately for us, changing our lot numbers would be very difficult as we have a warehouse full of barcoded inventory and a hundreds of files attached to the existing numbers. Hopefully Acumatica will be able to (quickly) restore the ability to use underscores in lot numbers…

​@MichaelShirk Terrifying!

​@PBSA yeah it’s very stressful to run!

Hi ​@MichaelShirk ,

Our customer is SaaS, and support is working on a script to correct this issue for them so we are going to stay with that approach for the time being.  Appreciate the offer though!

Laura

Although the Lot/serial is not a segmented key, the INVENTORY segmented key allows the overriding of the Prompt Characters _ underscore is the default.

Hi ​@dgodsill97 ,

I appreciate the input regarding the default separator for the INVENTORY segmented key.  I tested by specifying a different character as the separator, but still could not put through an inventory adjustment for an existing serial lot that contains an underscore.  

Thanks for the suggestion, though.

Laura

This has been identified by Acumatica as a product issue.  Development is working on a hot fix.

Hi ​@lauraj46,

This is a known issue in 2024 R2; as a workaround, use a dash instead of an underscore for new receipts and update existing lot numbers via an inventory adjustment or database script.

Hope this helps.

​

Hi ​@Ankita Tayana ,

Thanks, I am aware that it's a known issue.  For new lots the dash is a workaround.  An inventory adjustment generates an error unless the whole location is issued.  Client is SaaS.  Support is working on a fix.

Thanks for the suggestions!

Laura 

Thank you ​@hananeoufdir34 !  We applied the hotfix and it resolved the issue.

Laura