Distribution, Manufacturing, and Internet Modules

[thebottomline]

Client upgraded from v4.3 to v4.4 last week.  Fairly smooth migration.  However, they are noticing that SOME balances per the Turnover report do not tie to the balances per the Inventory valuation report.  The inventory valuation report has the correct numbers.

How does one fix this?  Recalculate Item History?  Where is the inventory turnover report pull its numbers from?

Thanks in advance.

[kvpierce]

If you are talking about the Quantity On Hand YTD, it is calculated based on the ‘Year’ and ‘Period/Month’ selected and uses the following: IM_PeriodPostingHistory: BeginningBalQty + PeriodChangeQty

[thebottomline]

So if I want to tweak the beginning balance, do I just change the current year or do I go back to the beginning to change the BB and then recalculate the item history utility?

[kvpierce]

Which Valuation report are you comparing the Turnover report to, as there are two?

I would compare the Valuation by Period to the Turnover report and set the year and period/month to be the same for both reports and see what you get.

[thebottomline]

The inventory valuation report is the master report.  All reports should agree with this one.  Client migrated three companies, two companies agree to a T.  The third company has about 15 items that do not agree between the turnover report and the inventory valuation report.

[kvpierce]

My suggestion would be to make a backup of that company and run the Recalculate Item History in the backup company to see if that fixes it. I believe you said something about this utility earlier, so try that.

[thebottomline]

Tried that but it throws a somewhat cryptic error

"A record with an invalid posting date was encountered in an item transaction table.  The recalculation cannot continue."

I rebuilt the key files for inventory and common items.  Rebuilt the sort files for inventory.  I downloaded the IM_Transaction history records into Excel and scanned for bad transaction date (none noted).

Any thoughts on what the real issue is?  No error number, program name or line # provided.

Thanks in advance.

[kvpierce]

The program not only reads the IM_ItemTransactionHistory table, but also the following tables when it's processing: 

IM_PeriodPostingHistory

IM_ItemCustomerHistoryByPeriod

IM_ItemVendorHistoryByPeriod

IM_ItemWhseHistoryByPeriod

CI_ItemTransactionHistory

CI_ItemHistoryByPeriod

The only table from the list above that has a 'Posting Date' is CI_ItemTransactionHistory. The rest all have Year and Period/Month fields so I don't think it's one of them because of the message you're receiving.

Try doing the same thing that you did on the Item Transaction table to the CI_ItemTransactionHistory and see if the corrupted date is in there.

[thebottomline]

Really starting to hate these generic error messages.

I downloaded both files into Excel.  Sorted both by transaction date.  Neither yielded a bad data record.  I created a pivot table on both of them and summarized by transaction date.  Same result.

Unless you have another thought, I guess I'll turn the files over to tech support and let them diagnose.

[kvpierce]

There's another date field in those tables called 'Reference Date' which may be the 'Posting Date' the program is referring to. If you do another search on that field with no results, then contacting support sounds like your next step.