By using this website, you agree to our Terms of Use (click here)
On our Sales Order screen, we're Allocating serial numbers using the Allocations button and pop-up, just like is done on the Shipment. We can then create a shipment and/or an Invoice and the serial number Allocations are copied to these documents and stored in their respective DAC, SOLineSplit.LotSerialNbr, ARTran.LotSerialNbr, and SOShipLine.LotSerialNbr, respectively. On the Sales Order and Shipment screens we can click the Allocations button and see the serial number that's been allocated.
However I just discovered that when the Shipment is confirmed, the Allocations on the Sales Order disappear! They continue to appear on both the Invoice and Shipment and if we create a Invoice after they have disappeared from the Sales Order (after we've confirmed the Shipment) they are copied over to the Invoice.
Now, I think we'll be able to work around this, but first I'd like to know if this is proper behavior we need to work around or if this is indeed a bug. Our printed Sales Order form currently contains the serial/lot number, but now only works if we print it before we confirm the shipment. Anyone have any insight or know where else the Lot/Serial Number might be stored wrt the Sales Order? I know I can pull in the Shipment table, but that seems like it's not the most elegant solution.
So I'm 95% sure this is proper behavior and I was wrong...SOLineSplit.LotSerialNbr does still contain the serial/lot number, it just doesn't show up on the Sales Order's Allocation tab anymore. Just wanted to update in case someone stumbles upon this in the future with the same query.
I've noticed it disappearing on the front-end before and wondered if it also disappeared on the back-end. Glad to hear that it's still stored on the back-end. What Acumatica build are you using?
I had an issue this as well. For us it was the Shipment Plan Type under the Order Type codes, Template tab. We had it set for Sales Order and it needs to be SO Allocation to handle the allocations correctly.
Just recently noticed this as well but thought it was due to a recent change. Based on the age of this post it looks like it's always been that way.