Sage 100

Customer is on 2019 & 2.20 with patches.  In her v2019, she can access ACA Employer Maintenance use the pulldown for Year 2019, but when she clicks on the Monthly Detail, gets a 'The Year is Required' message.
  
The resolution refers to Corrupt Data Dictionaries and I would have to do a 'on my side' install of her complete environment to get new dictionaries. 
I had her try to create a UDF and update it to recompile the dictionaries, with no success.

For giggles tonight, in their test environment (which is on a separate old server) I DFDM'd changing the Key in the PR_ACAEmployer.m4t, for the year and I was now able to use the pulldown for the 2019 year and click on the Monthly Detail without receiving the message.

Anybody know if there is going to be any fallout from doing this?  
It would certainly be easier and quicker than trying to reinstall her environment.

Thanks

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

I ran into the same problem last week.  Sage had me replace their PR_ACAEmployer.m4t file with mine as long as it was on the same version and PU.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-14-2020 00:12
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I ran into the same problem last week.  Sage had me replace their PR_ACAEmployer.m4t file with mine as long as it was on the same version and PU.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

------Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]
------------------------------

Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Just a quick FYI here - my DFDM to create the record in PR_ACAEmployer looked like it worked from the user side, but in the PR_ACAEmployerMthlyDetail things weren't looking right (blank records) so in my case it didn't really work.  I also tried a fresh install on product/update on my system, to the PR_ACAEmployer over to client and as soon as I accessed the task, all the information shifted in DFDM - the encrypted value was not longer in the correct field along with everything below it. 
I did the reinstall last night and have to test yet today to confirm front and back door look ok.
N​

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

Original Message:
Sent: 01-15-2020 00:33
From: Michele Herzog
Subject: Year is Required in ACA Maintenance

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]
------------------------------


Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Just off the phone with client having that issue still.  I REALLY don't want to mess with the encryption key.

We were able to get past the employer detail month/date issue by copying the table from my install.  However, the Aatrix ACA forms are not populating properly (per client who has done this every year).


------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-15-2020 10:50
From: Nancy Hanson
Subject: Year is Required in ACA Maintenance

Just a quick FYI here - my DFDM to create the record in PR_ACAEmployer looked like it worked from the user side, but in the PR_ACAEmployerMthlyDetail things weren't looking right (blank records) so in my case it didn't really work.  I also tried a fresh install on product/update on my system, to the PR_ACAEmployer over to client and as soon as I accessed the task, all the information shifted in DFDM - the encrypted value was not longer in the correct field along with everything below it.
I did the reinstall last night and have to test yet today to confirm front and back door look ok.
N​

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------


Original Message:
Sent: 01-15-2020 00:33
From: Michele Herzog
Subject: Year is Required in ACA Maintenance

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]


Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

@Jeff Schwenk I had this the other day.

2019 is closed yes? Did they change the reporting period to 2019 from the 2020 default?

This was what the case was there.

​

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
https://www.firstmatellc.com/
------------------------------

Original Message:
Sent: 01-15-2020 11:15
From: Jeff Schwenk
Subject: Year is Required in ACA Maintenance

Just off the phone with client having that issue still.  I REALLY don't want to mess with the encryption key.

We were able to get past the employer detail month/date issue by copying the table from my install.  However, the Aatrix ACA forms are not populating properly (per client who has done this every year).

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 01-15-2020 10:50
From: Nancy Hanson
Subject: Year is Required in ACA Maintenance

Just a quick FYI here - my DFDM to create the record in PR_ACAEmployer looked like it worked from the user side, but in the PR_ACAEmployerMthlyDetail things weren't looking right (blank records) so in my case it didn't really work.  I also tried a fresh install on product/update on my system, to the PR_ACAEmployer over to client and as soon as I accessed the task, all the information shifted in DFDM - the encrypted value was not longer in the correct field along with everything below it.
I did the reinstall last night and have to test yet today to confirm front and back door look ok.
N​

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 01-15-2020 00:33
From: Michele Herzog
Subject: Year is Required in ACA Maintenance

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]


Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

I believe she did.  I was watching her.  But was I paying attention???  Will go back and check

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-15-2020 17:13
From: Eric Lunceford
Subject: Year is Required in ACA Maintenance

@Jeff Schwenk I had this the other day.

2019 is closed yes? Did they change the reporting period to 2019 from the 2020 default?

This was what the case was there.

​

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
https://www.firstmatellc.com/
------------------------------


Original Message:
Sent: 01-15-2020 11:15
From: Jeff Schwenk
Subject: Year is Required in ACA Maintenance

Just off the phone with client having that issue still.  I REALLY don't want to mess with the encryption key.

We were able to get past the employer detail month/date issue by copying the table from my install.  However, the Aatrix ACA forms are not populating properly (per client who has done this every year).

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444


Original Message:
Sent: 01-15-2020 10:50
From: Nancy Hanson
Subject: Year is Required in ACA Maintenance

Just a quick FYI here - my DFDM to create the record in PR_ACAEmployer looked like it worked from the user side, but in the PR_ACAEmployerMthlyDetail things weren't looking right (blank records) so in my case it didn't really work.  I also tried a fresh install on product/update on my system, to the PR_ACAEmployer over to client and as soon as I accessed the task, all the information shifted in DFDM - the encrypted value was not longer in the correct field along with everything below it.
I did the reinstall last night and have to test yet today to confirm front and back door look ok.
N​

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 01-15-2020 00:33
From: Michele Herzog
Subject: Year is Required in ACA Maintenance

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]


Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

FWIW, in SQL installs I just updated the PR_ACAEmployer YEAR field and verified the CALENDARYEAR field was populated and it pulled the reports as expected. Haven't run into this on any pvx installs yet, but the SQL fix was pretty easy.

------------------------------
Michelle Forsey
Eide Bailly, Inc.
801-456-5470
------------------------------

Original Message:
Sent: 01-15-2020 17:44
From: Jeff Schwenk
Subject: Year is Required in ACA Maintenance

I believe she did.  I was watching her.  But was I paying attention???  Will go back and check

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 01-15-2020 17:13
From: Eric Lunceford
Subject: Year is Required in ACA Maintenance

@Jeff Schwenk I had this the other day.

2019 is closed yes? Did they change the reporting period to 2019 from the 2020 default?

This was what the case was there.

​

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
https://www.firstmatellc.com/


Original Message:
Sent: 01-15-2020 11:15
From: Jeff Schwenk
Subject: Year is Required in ACA Maintenance

Just off the phone with client having that issue still.  I REALLY don't want to mess with the encryption key.

We were able to get past the employer detail month/date issue by copying the table from my install.  However, the Aatrix ACA forms are not populating properly (per client who has done this every year).

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444


Original Message:
Sent: 01-15-2020 10:50
From: Nancy Hanson
Subject: Year is Required in ACA Maintenance

Just a quick FYI here - my DFDM to create the record in PR_ACAEmployer looked like it worked from the user side, but in the PR_ACAEmployerMthlyDetail things weren't looking right (blank records) so in my case it didn't really work.  I also tried a fresh install on product/update on my system, to the PR_ACAEmployer over to client and as soon as I accessed the task, all the information shifted in DFDM - the encrypted value was not longer in the correct field along with everything below it.
I did the reinstall last night and have to test yet today to confirm front and back door look ok.
N​

------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 01-15-2020 00:33
From: Michele Herzog
Subject: Year is Required in ACA Maintenance

I have ran into this also.  Sage does have a KB that involves reinstalling Sage and all 3rd party enhancements.  I chose to correct thru DFDM.  Happy to hear there is another quick alternative.

------------------------------
[Michele] [Herzog] [CPA,CITP, CGMA]
[Overland Park] [KS]
[816-520-1365]


Original Message:
Sent: 01-14-2020 12:21
From: John Leonard
Subject: Year is Required in ACA Maintenance

I have run into this on two clients this morning.  I have been copying the PR_ACAEmployer.m4t from the ABC company on a clean install and that seems to be working.

 

John P. Leonard, CPA, CITP

JLA Consulting

(504) 835-9639

(504) 835-7850 (FAX)

www.jlaconsulting.net

 

Original Message------

Client of mine ran into this as well.  I fixed it as Nancy did, they called me a week later to say that it wasn't working.  I recommend they call Sage for a fix.  Will check to see what the resolution was. ​

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

I ran into these issues yesterday.  I created a new 2019 record in the PR_ACAEmployer (copied the data from the 2018 record) and 12 new records in PR_ACAEmployerMonthlyDtl (you just need to populte the year and month for each of the 12 records).  Seemed to work.  Note you cant create the encryption code but the system will create it for you after you access the table from within the Sage UI.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------

Original Message:
Sent: 01-28-2020 14:39
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

​​Thanks for passing along the utilities.  My client was able to get past the issues, manually fix the large employer report and put the forms into the mail yesterday.  Sometimes you just have to demand that Sage think outside their little cubby!

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-28-2020 14:46
From: Doug Higgs
Subject: Year is Required in ACA Maintenance

I ran into these issues yesterday.  I created a new 2019 record in the PR_ACAEmployer (copied the data from the 2018 record) and 12 new records in PR_ACAEmployerMonthlyDtl (you just need to populte the year and month for each of the 12 records).  Seemed to work.  Note you cant create the encryption code but the system will create it for you after you access the table from within the Sage UI.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Assistant to the Traveling Secretary
------------------------------


Original Message:
Sent: 01-28-2020 14:39
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176

Thank you @Mary Jo Krueger for posting these.  The 'resolution' that Sage has on their KB is ridiculous.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------

Original Message:
Sent: 01-28-2020 14:39
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

My client sent her data in.  Below is Linda Raby's response. 

The problem was your data.  In your legacy version there were no Earnings Types in the PR_23SEI.soa table after 9/9/2011.  I don't know how that happened as that was 8 years ago.  The new Payroll ACA uses that field and after conversion it converted the blank field to the wrong earnings type because it had no reference.  I got a utility yesterday to fix the records in the new payroll version.  I am glad you were able to get those records fixed.  There should not be a problem next year because you are entering the 2020 year data in the new version so there will be no migration/conversion of the bad records in 2020.  That is true unless you have done some of 2020 payroll in the legacy version before the upgrade.  If so, then we need to fix that data.

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 01-29-2020 08:22
From: Jane Scanlan
Subject: Year is Required in ACA Maintenance

Thank you @Mary Jo Krueger for posting these.  The 'resolution' that Sage has on their KB is ridiculous.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758
------------------------------


Original Message:
Sent: 01-28-2020 14:39
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176

Thanks for posting this, Jeff.  I hope you don't mind, but I'm going to copy and paste it into the thread that was started regarding hours being wrong on the ACA Applicable Large Employer report since the utility that you reference actually fixes that issue - finally.  It doesn't do anything to resolve "The Year is Required".  I've been waiting for the resolution on the Applicable Large Employer report for over 2 months so I really appreciate the heads up that they finally figured out the problem.  Lord only knows when they might have gotten around to telling me they resolved it.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176
------------------------------

Original Message:
Sent: 01-30-2020 11:35
From: Jeff Schwenk
Subject: Year is Required in ACA Maintenance

My client sent her data in.  Below is Linda Raby's response.

The problem was your data.  In your legacy version there were no Earnings Types in the PR_23SEI.soa table after 9/9/2011.  I don't know how that happened as that was 8 years ago.  The new Payroll ACA uses that field and after conversion it converted the blank field to the wrong earnings type because it had no reference.  I got a utility yesterday to fix the records in the new payroll version.  I am glad you were able to get those records fixed.  There should not be a problem next year because you are entering the 2020 year data in the new version so there will be no migration/conversion of the bad records in 2020.  That is true unless you have done some of 2020 payroll in the legacy version before the upgrade.  If so, then we need to fix that data.

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 01-29-2020 08:22
From: Jane Scanlan
Subject: Year is Required in ACA Maintenance

Thank you @Mary Jo Krueger for posting these.  The 'resolution' that Sage has on their KB is ridiculous.​

------------------------------
Jane Scanlan
Partner, Next Level Manufacturing Consulting Group
Next Level Manufacturing Consulting Group
Chanhassen MN
952-210-7758


Original Message:
Sent: 01-28-2020 14:39
From: Mary Jo Krueger
Subject: Year is Required in ACA Maintenance

I didn't have a compatible version of an ACA_Employer file that I could swap in so I contacted Sage support again.  I got Jeri and was told that I had to follow the instructions to rename data dictionary files and reinstall everything.  I told her there was no way every single ACA filer we work with has problems with their data dictionaries and the problem had to be on Sage's end somewhere.  I said I was refusing to reinstall everything and she had to get me the file I needed.  She went back to talk with Scott Brady and lo and behold found they created a utility to fix the problem.  She said it should work both on Providex and SQL installations but make sure you have a backup before running it.  I ran it at one site and it resolved the issue.

------------------------------
Mary Jo Krueger
Senior Software Consultant
CLA (CliftonLarsonAllen LLP)
Appleton WI
920-996-1176

Link to the Sage KB with the utility to fix their issue - https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=95595&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=2286&cmd=displayKC&dialogID=111664&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------