Sage 100

Just a momentary rant. I have one client in particular that heavily uses inventory and lots. Occasionally they get a batch to hang when posting Sales Order Invoices. This occurred in 4.4 and now in 2013. They call me. I find duplicate keys. Rebuild the files and post the batch. I then get to spend HOURS cleaning up files. Duplicate Inventory Transactions, AR Invoice History, Summary Totals, Warehouse Totals, Cost Totals and other. I would like to just restore them but... They have 15 to 20 people on the system everyday working hard.

Is there an easier way to fix this and more important, to prevent it from happening?

So far I have found 10 files all with duplicated or incorrect totals.

Are they on Advanced?

Do you check for duplicates before you rebuild the files? If an update is interrupted a placeholder record is written to the tables. Rebuilding the tables will remove the placeholder record. For example, 20 invoices are in a batch. An error occurs on the 15th invoice processed during the update. A placeholder record is written to all of the tables. If you rebuild the tables, the placeholder is removed. When you re-start the update the first 15 records get written again.. duplicated. The way to fix this without duplicates is to determine the invoice and/or line that is corrupt, then use DFDM to either correct or delete then restart the update.

The corruption probably occurs during sales order entry and then is copied when the order is invoiced. Rebuilding SO Header and Detail regularly may prevent errors during the sales journal update.

@JohnHoyt , They are on Standard. I need to address moving to advanced again. They are having disconnects from the terminal server. Not sure why that is happening when they sit next to each other and plenty of resources and nothing in the windows logs. @DougHiggs , Good to know. Thank you.

We have had many customers that have disconnects during invoice updates using Standard with a LAN connection. Using terminal server, this should not occur nor cause an issue, so that may be another issue. With the local connection, after upgrading to Advanced, these issues went away.

15-20 users on Standard, even with Terminal Services, I would recommend upgrading them to Advanced.

This architecture without commit rollback is embarrassing considering the massive maintenance customers have been paying...