Sage 100

WO transaction batch hung / lost Customer went to post a batch that processed both a Completion and a Close Work Order transaction on 9 different work orders. When she went to print, an issue with Paperless Office caused the printing to fail. The batches subsequently disappeared. Now when they go to another workstation and try to re-create the transactions (because the batch is gone), the system gives a message that ""Quantity entered exceeds quantity remaining to be completed"". However, neither the Close nor the Completion transactions appear in the Transaction panel in WO Inquiry. Also, the Summary panel in WO Inquiry shows 0 Qty Completed and 2 Qty Planned. Something appears to be hung. Where do I go to clear this? Anyone? Bueller?

Any chance they know the batch number? I've had SO batches disappear but the entries are still out there in the batch. Once you recreate the batch, they appear. You might look in GL_CompanyActiveBatch.

Probably need to reinitialize the transaction data entry files.

+1 what Roberta said and my backup guess would be rebuild sorts

Try printing the WO transaction register for all batches and they may be on there.

I would bet there is an update flag set. Trick will be to find it.

@ThereseLogeais @RobertaFerguson good idea. They don't know the batch number because they have folks in the shop entering and processing batches all day long. I am going to DFDM the transaction entry table and look for orphaned entries. Also, I found an entry in the KB (ID:37200) regarding the need to clear ""Quantity Completed Today"" field (#13) in WO1*** for each item. I'm going to try that for one of the items and see where that gets me. I love Paperless Office. ;-p

You can fix the field manually but the reinit will also reset that field. If there are other batches then the manual fix is the only option unless you get them to update all other batches first and then reinit.

v2014, I attempted to reinit the 4 W/O Transaction Entry files and the W/O Batch file, but field 13 (11) didn't reset; I had to do it manually via DFDM.

------------------------------
- Brett
------------------------------

Original Message:
Sent: 09-10-2014 09:29
From: Roberta Ferguson
Subject: WO transaction batch hung / lostCustomer went to

You can fix the field manually but the reinit will also reset that field. If there are other batches then the manual fix is the only option unless you get them to update all other batches first and then reinit.