Upgrade to Kinetic - left Journal Group Open

Kinetic ERP
1

I helped a client upgrade last weekend from Vantage 6 to Kinetic 2023.1.10 cloud. It appears that a General Ledger Journal group was mistakenly left unposted. This is causing all kinds of problems.

  • When we pull up the group in Journal Entry, it’s showing the headers with the correct debits/credits, but the detail lines are all missing. So, we can see journal 1234 there with $25000 in debits/credits, but the account details are missing.
  • I can run a BAQ against GLJrnDtl and I see the unposted journal lines there. But I don’t believe the process writes to this table until it’s posted. I created a test journal in Kinetic, and the lines from that don’t appear in GLJrnDtl until they’re posted. So, even though GLJrnDtl has the Vantage 6 lines in the table and marked as unposted, I don’t think they should be there.
  • When we run the Trial Balance, it is not matching our Vantage Trial Balance as it’s including all the unposted lines.

So, it appears that there are places the group appears to be posted, and other places where it doesn’t. I’d prefer if we could simply blow away the journal groups and we can reenter in Kinetic.

Has anyone else had this happen? How did you resolve? I have been working with Tech Support for a few days, but so far the solutions proposed don’t really have anything to do with the problem. I can’t believe in all the upgrades they’ve had that leaving a Journal Entry unposted hasn’t happened. It would seem like there should be a fix to remove these offending records and start over. If anyone has had this and had a case number, that would be great.

Thanks.

2

They explicitly warn on the upgrade guides to post all financial groups they have for years. I suspect if they make modifications to tables related the records get corrupted

That’s a bummer, hopefully it hey can come up with a solution

1 Like
3

Yep, complete oversight on our part. That was a task, someone thought they posted.

4

In one of my test builds I did this, and the DB conversion simply failed. I assumed at the time this was intentional given all the warnings as mentioned above.

I didn’t realize there’d be a direct upgrade path from V6 to K

Hope you find a solution!

5

It wasn’t quite a direct upgrade path. There was what Epicor considered a manual upgrade from V6 to V8, which I suspect means they just didn’t have it all scripted. Then it went through a series of automated upgrades, like from 8 to 8.03, 8.03 to 9.05, etc. To add to it, we took two different Vantage databases for two single-companies and merged them into one Kinetic database. All in all, from the time we uploaded the DB to Epicor to getting it back in the cloud was almost 3 full days.

If I don’t end up with a solution, I’ll probably test out the brute force method on a PILOT system - write some code to remove the unposted entries from tables, clear out the group, and test like the dickens. I assumed they’d have a fix that would do the same, but maybe we’re the only ones who’ve pulled that move!