Urgent: Financial Year-end on version 7.5 with sp#2 1

[Luvsql]

Has anyone run this yet? Please take a look at the LASTUSER and USWHPSTD fields in the GL30000 after you run the year-end. Did anyone else's data (ALL the data) get updated to the user who ran the year-end (ie it overrode every single record)?

It did this for every company we ran the year-end on now. They are saying restore. Sorry, we've been working for 2 entire days now.

 

[klewis10367]

Will that cause a problem?

 

[Luvsql]

For auditing purposes, our controllers look at these fields to see who did what and when. I'm getting emails asking why I posted entry x and entry y. We now have no idea who did it.

 

[VictoriaYudin]

yeah - ouch - it looks like version 7.0 did the same thing...I only have 1 year (2000) where that is not the case, which is back when we were on 6.0 - GOOD CATCH - have you asked GP support about this?

 

[Luvsql]

Yes, I found out it's a problem report since version 3 that they have never fixed (PR 5197). They said they can add it as a product suggestion ie suggest that product not corrupt my data during a year-end.

They said that they've never fixed it becuase it would require them changing the table structure. Ahhh, what exactly are our enhancements paying for if not to fix things???!!!

 

[lpd64]

You could restore to a new database then use an sql script to update the "corrupt" field in your production database with the data from the restored database. Since Great Plains is at fault they should write the script for you

 

[Luvsql]

Irestored test databases with date prior to closing. Microsoft is writing the scripts for me next week. I'll post them for anyone that may need them.

 

[VictoriaYudin]

Awesome - thanks!

 

[Luvsql]

Here is the script that they wrote for me. It's required to have a test company or another database that contains the data prior to running the year-end.

/* LIVE = Database after year end close ( this is the live company database)

TEST = Database before year end close ( this will be the backup database that is restored) */



Select * from LIVE..GL30000 a
INNER JOIN TEST..GL20000 b ON
a.HSTYEAR=b.OPENYEAR
and a.JRNENTRY=b.JRNENTRY
and a.TRXDATE=b.TRXDATE
and a.ACTINDX=b.ACTINDX
and a.DEBITAMT=b.DEBITAMT
and a.CRDTAMNT=b.CRDTAMNT
and a.SEQNUMBR=b.SEQNUMBR
and a.RCTRXSEQ=b.RCTRXSEQ
and a.TRXSORCE=b.TRXSORCE
and a.CURNCYID=b.CURNCYID
and a.USWHPSTD <> b.USWHPSTD



update a set a.USWHPSTD = b.USWHPSTD from LIVE..GL30000 a
INNER JOIN TEST..GL20000 b ON
a.HSTYEAR=b.OPENYEAR
and a.JRNENTRY=b.JRNENTRY
and a.TRXDATE=b.TRXDATE
and a.ACTINDX=b.ACTINDX
and a.DEBITAMT=b.DEBITAMT
and a.CRDTAMNT=b.CRDTAMNT
and a.SEQNUMBR=b.SEQNUMBR
and a.RCTRXSEQ=b.RCTRXSEQ
and a.TRXSORCE=b.TRXSORCE
and a.CURNCYID=b.CURNCYID
and a.USWHPSTD <> b.USWHPSTD