Sage 100

Client just hosed up their Item transaction history table (among others) by entering a data of 201230216. Items were posted to history with a fiscal year of 2013 and period one. Inventory is set to calendar. Anyone have any thoughts of a less painful way of fixing it? Luckily, there were only 76 transactions and most of them are the same item number.

Disassembly Entry and then Production Entry with correct datae?

Hey! Welcome to the club! This was my issue a few weeks back with the sales journal posting to 2020. I manually changed the dates in the transaction history file through DFDM. It took me about an hour. (I of course created a Crystal report to export what I needed in order to enter it more efficiently.) Then, about a week later, I discovered there were TWO more journals that posted to 2020 and had to do those all manually as well. Since I was well-versed in it now, those only took me about an hour as well. HAVE FUN!!

Myron, testing your thought in the test company. The date that posted in the transaction history was 6/21/2014 in addition to the other two fields so I doubt if that will be the fix. Starting to wonder whether I should start a MAS 200 upgrade discussion. Bad dates are becoming more frequent and there doesn't seem to be any particular workstation causing the issue. Of course, IT doesn't have an issue. @ThereseLogeais - Did you rebuild the transaction history table?

Funny - Well I have a situation where the sales order posting locked up in 4.5 and most of the big files were hosed. When I rebuilt the IM_Itemtransactionhistory table it did not say there were any issues - but it ended up removing ALL records - we did not realize it for 2 weeks. I got it properly rebuilt with *UFAR but the challene has been getting those 2 weeks in. And when I saw this I had just finished trying to import these transactions back into that file. Well VI does not allow to import certain fields as they are read only. Now I get a message the record is not in an editable state. Back to support.

@JeffSchwenk I did not rebuild the transaction table as my transactions weren't so hosed as yours - I mean, what kind of date is 201230216?? Mine just posted to the wrong year. So it posted to period 1, 2013 but the transaction date is 6/21/14?? You could certainly try rebuilding the trans. hist. table - in the test company!

This is where SQL will make our lives SO much easier....and always check file/table sizes before/after using the rebuilds.