I have a client running 2013 SQL and we're finding hundreds of orders not recording all SO Entry Lines to SO History. Worse yet the SO History Line SO Line Index does not match the actual SO Line Index. So when an invoice update writes back to SO History the quantity shipped is wrong (because the active data is written to the wrong line in history). The real kicker is the write back sometimes goes to a Comment Line (due to mismatch sequence numbers)! When this happens the sales journal update throws an error 40 (missing UoM CF on a Comment Line) and halts the update. The resolution is to manually enter it for the Comment Line and restart the update. When this is done the update restarts, doubling the value of the original Invoice History Header Sequence 000000 (and Open Invoice), and it creates a duplicate Invoice History Header Sequence 000001. Loads of fun... :)