We have these kind of orders a lot as we run in a citrix environment and everytime a user is disconnected, the data gets stuck in mid-entry and we end up with a lot of data corruption.
When you enter an order, Great Plains does not enter any information into the SOP10100, other than the SOPNUMBE and SOPTYPE until the order is saved. Ie you can start an order, enter the customer, batch, po number, enter some line items, but only the Sopnumber and Soptype appear in the SOP10100. Once you save the transaction, GP updates that record in the SOP10100 table. If GP crashes etc., it does not roll back and you end up with bad data.
The worst thing about this is those items on this "corrupted" order, are still allocated and will not be removed until 1) Run checklinks to remove documents or delete via sql and 2) run reconcile in inventory.