Are these reports run every day? (doesn't seem so, seeing as how there are no totals for a 3 week stretch). The most likely reason is that the reports hadn't been run and there's no menu item posting procedure in the autosequences.
On June 25, was the system date accidentally changed to August 13, however briefly?
When was it discovered that these totals were missing? If it was any time before August 27 there's something weird going on.
You have to have an understandign of how Micros posts totals for this to make sense.
[ol 1]
[li]The 3700 holds check details for 14 days, these details are used to post reporting totals which are then usually held for about a year.
[li]When posting, Micros looks at each of the Menu Item totals sets in the hist_ttl_def table. Among other things this table holds the last transaction sequence number that was posted for each total set and the date & time at which it was posted. The posting procedure stores that info and the most recent transaction number.[/li]
[li]All menu item transactions between the two stored numbers are posted to the menu item totals tables.[/li]
[li]The hist_ttl_def table is updated, setting the last posted seq to the end of the range that was stored. This is how it keeps track of what's been saved and what's outstanding.[/li]
[/ol]
So, if a menu item report was run on August 15 it should have posted everything from 8/1 forward.
End of night posting procedures should have made sure everything was posting, even if no reports were run.
If the system date had been changed and the Menu Item Posting procedure ran during that time, it would have written the current, incorrect date and time as the last posted datetime. After the date was changed back, totals wouldn't post until after the last posted datetime had been cleared.
I have seen cases where the hist_ttl_def table was altered manually through SQL. Usually by mistake, but it really banged things up.
