Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Sage 100 2018 upgrade with Payroll

  • 1.  Sage 100 2018 upgrade with Payroll

    Posted 05-10-2019 17:32

    Upgrading a customer form Sage 100 2014 Standard to Sage 100 2018 Standard.  They have 10 employees and are a Texas based company with only Texas resident employees so there is no state income tax.  The data rebuilds fine with no errors in 2014.  The migration goes without a hitch.  Once I start the conversion the Mappings from Tax Codes to Tax Groups works.  The mapping from Tax Group to Tax Profile goes well.  Originally, the Filing Status mapping shows 1 blank line with no statuses at all.  I could not proceed so I edited the FilingStatusPreConversion text file to include just the Federal married and single lines.  If I proceed then I get an error #11 Record not found while converting the PR1 file. 

    If I include ​any TX records in the filing status then I get an error #14 after it opens PR3.

    And remember, the system does not recognize ANY statuses if I don't edit the FilingStatusPreConversion text file.

    ​

    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------


  • 2.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-11-2019 18:54
    #Urgent #payroll #Sage100
    This is a vexing problem for us in the middle of this modest upgrade. Does anybody have any suggestions for us?

    ------------------------------
    Jerry Norman
    Smartbridge Partners
    Austin TX
    512.419.1444 x112
    ------------------------------



  • 3.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-11-2019 19:01
    Even though there is no state tax, there is probably a state tax record in PR3 (for workers' comp).  Not sure if that helps any.  Maybe something to look at.

    ------------------------------
    Chris St. Amand
    Arizona Accounting & Information Systems
    ------------------------------

    Original Message


  • 4.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-11-2019 19:09
    **In Sage 2017 **, Filing status for Fed record can be H, M, S, NRA, NRH, NRM.  Filing status for State (TX) record is Blank, but 7 digit workers' comp code is populated.

    ------------------------------
    Chris St. Amand
    Arizona Accounting & Information Systems
    ------------------------------

    Original Message


  • 5.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-11-2019 19:12
    Even though there isn't income tax in Texas, set up a Texas State profile for the employees.

    ------------------------------
    Michelle Taylor
    ERP Team Manager, CS3 Technology
    918-388-9772
    ------------------------------

    Original Message


  • 6.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-16-2019 19:40
    More interesting information on this one.  After an update and a patch I am getting the system to attempt the Payroll conversion.  The system breaks down with an Error #13 on file PRXDC2.SOA (DC2 is the company code).  This is a "Miscellaneous Tax Code" file and I can't find any company specific miscellaneous tax codes.  Any idea where I can tell the system to IGNORE miscellaneous tax codes?​

    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------

    Original Message


  • 7.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-16-2019 19:53
    @Chuck Peddy  This could be a permissions issue on the file, or the file could have corrupt data.  PRX is a Miscellaneous Tax Rate file.  It has the rates for the medicare surcharge and some other state miscellaneous taxes.  I would use DFDM and compare it to a known good file and or rebuild it using rebuild key files.  You might be able to replace it with a known good copy of the file.  Below is the definition of a pvx error 13:

    Error #13
    File access mode invalid 

    Possible Reasons: 

    • Cannot send output to serial file unless first locked. 
    • Cannot receive input from an output-only device (e.g. a printer). 
    • Cannot send output to an input only device.
    • Cannot write given output to file without a KEY= option or not before extracting a record. 
    • Cannot write to a non-externally keyed file using a KEY= option. 
    • Cannot drop the only active window on a terminal. 
    • OS returned an access mode violation or a permission denied status on an OPEN INPUT or OPEN PURGE directive for a file. 
    • Attempt to apply/remove a password when the file is in read-only mode, not locked, or not empty.

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------

    Original Message


  • 8.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-17-2019 00:12
    Edited by Nicole Ronchetti 05-17-2019 00:13
      |   view attached
    I've run into this  few times. Here's the KB article
    https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=92719&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=5687&cmd=displayKC&dialogID=219512&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true
    ------------------------------
    Nicole Ronchetti
    DSD Business Systems
    ------------------------------

    Note : Recently uploaded media files are still processing:

    • The following conversion record failed while converting XXX_ 02.17.00.00_DATA_PR_ConvertToFramework_000000_000 - Error #13_ File access mode invalid View the Activity Log to locate a specific conversion log_.pdf

    Original Message


  • 9.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-17-2019 10:40
    This company has PRU, PRV, PRW, and PRX.  No other Payroll installations that I have run across have utilized these files.  What's more, all four of these files contain no data.  They are TOTALLY blank.  If I eliminate them or restore from a backup, it doesn't help.  I am right now looking through other records to see if this company somehow USED to have some miscellaneous tax codes.  Any other ideas?

    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------

    Original Message


  • 10.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-17-2019 10:46
    @Chuck Peddy  Did you look in the mas90\PR folder of the Source installation for the PRX.soa file (not the PR_XXX folder)?   ​

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------

    Original Message


  • 11.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-17-2019 12:27
    @Nicole Ronchetti and @Doug Higgs, That fixed it.  The PRU.SOA and PRV.SOA ​​ had copied over to the PR program file but not the PRX.SOA.  This was actually two different problems with two distinct solutions.  I got wrapped around the axle after solving the first problem.  Thank you both very much for yoru hel!

    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------

    Original Message


  • 12.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-31-2019 22:59
    Those specific files are used for Local codes and should be living directly in the PR folder if being used.

    ------------------------------
    Carmen Cruz
    Senior Specialist, Technical Consultant
    SWK Technologies Inc.
    Carmen.Cruz@SWKTech.com CA
    973-437-3984
    ------------------------------

    Original Message


  • 13.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-31-2019 19:13
    What is the solution to this part of the issue?

    Running into this myself with an upgrade. 4 of the 5 companies convert fine, the last company gets this blank line with no statuses to select to continue.
    Once I start the conversion the Mappings from Tax Codes to Tax Groups works.  The mapping from Tax Group to Tax Profile goes well.  Originally, the Filing Status mapping shows 1 blank line with no statuses at all. 
    Chuck Peddy,  05-10-2019 17:31


    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------



  • 14.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-31-2019 20:01
    @Greg Stiles, there are files created in the Home/TextOut directory that help guide the conversion. The last one is named FilingStatusPreConversion. These text files don't go away if the conversion fails and you can edit the files. If you edit the FilingStatusPreConversion then the conversion will proceed. Let me know if you need the format of that CSV file. I am on my phone and don't have access to it right now.

    ---------------------------------
    Chuck Peddy
    Smartbridge Partners
    ---------------------------------



    Original Message


  • 15.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-31-2019 21:53
      |   view attached

    @Greg Stiles. the four files are as follows:

    ​XXXDepartmentPreConversion.TXT
    XXXTaxGroupPreConversion.TXT
    XXXTaxProfilePreConversion.TXT
    XXXFilingStatusPreConversion.TXT

    As I said, they are in the ..\Home\TextOut of the new installation.  The "FilingStatusPreConversion" is the last populated.  You can edit any and all of the files after a failed conversion and the new parameters that you give will be the new defaults in the next conversion.  The following is the the format that I used for the FilingStatusPreConversion.  As always the XXX is the company code.

    ,,M,*FEDERAL*,FEDERAL,M,
    ,,S,*FEDERAL*,FEDERAL,S,

    Let me know if you need any more help.



    ------------------------------
    Chuck Peddy
    Smartbridge Partners
    ------------------------------

    Attachment(s)

    TXT
    XXXFilingStatusPreConversion.TXT   52 B 1 version
    Original Message


  • 16.  RE: Sage 100 2018 upgrade with Payroll

    Posted 05-31-2019 23:06
    Edited by Carmen Cruz 05-31-2019 23:07

    The Tax Status Filing not giving you anything to select will happen for the following reasons:

    This happens if Sage 100 2018 was not installed in the correct order

    Sage 100 2018
    Sage PU2
    Sage 2.18.0 minimum PRIOR to Parallel Migration

    If this is not done in the correct order, hate to say this, you have to start the upgrade over from scratch,  uninstall, remove Sage folders the whole thing and start over.  This is what causes issues with the status.  The only way to avoid is to always backup the new MAS90 directory created during installations for the new versions prior to ever doing Parallel or any changes.  Always keep a vanilla image to avoid having to start from scratch in the future.  
    Now if it was done in the correct order go into the source Employee Maintenance and make sure on tab 2 i believe that when you go into Tax Status every employee is actually set up correctly.  I had a client who had NONE of that setup and it blew up on the Tax Status page just like what your getting



    ------------------------------
    Carmen Cruz
    Senior Specialist, Technical Consultant
    SWK Technologies Inc.
    Carmen.Cruz@SWKTech.com CA
    973-437-3984
    ------------------------------

    Original Message


  • 17.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-03-2019 11:37
    Thanks @Chuck Peddy & @Carmen Cruz​​ I will get back to this install today.

    @Carmen Cruz PU2 and 2.18.0​ are not current, are these required first for the initial conversion and then go to PU5 and 2.19.2?

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 18.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-03-2019 11:51
    its a minimum version level to be at prior to any migration.  You can take it all the way up though if you prefer.

    ------------------------------
    Carmen Cruz
    Senior Specialist, Technical Consultant
    SWK Technologies Inc.
    Carmen.Cruz@SWKTech.com CA
    973-437-3984
    ------------------------------

    Original Message


  • 19.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-03-2019 16:51
    SOP for me is always to create a backup of the new MAS90 folder once the DVD and PU's are installed but prior to any migration work.  Been burned too many times by having to go back to square one an reinstall everything.

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

    Original Message


  • 20.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-04-2019 12:39
    Edited by Greg Stiles 06-04-2019 12:39
    Thanks Everyone.

    Resolution was
    1. Remove offending company and data files from 2018 install
    2. Remigrate company from 2017 to 2018
    3. Edit ..\Home\TextOut\XXXFilingStatusPreConversion.TXT and change as follows. (Was 2 lines of 6 commas)

      ,,M,*FEDERAL*,FEDERAL,M,
      ,,S,*FEDERAL*,FEDERAL,S,

    4. Convert company in 2018.
    5. High five 90 Minds (virtual LOL)


    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 21.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-04-2019 21:33
    This is a neat trick Greg.  Didn't even know that was there.  Shame, I know...:)   Now in my bag of tricks.

    ------------------------------
    Carmen Cruz
    Senior Specialist, Technical Consultant
    SWK Technologies Inc.
    Carmen.Cruz@SWKTech.com CA
    973-437-3984
    ------------------------------

    Original Message


  • 22.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-05-2019 10:37
    Thanks goes to @Chuck Peddy, I didn't know those files were there either!​

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 23.  RE: Sage 100 2018 upgrade with Payroll

    Posted 06-05-2019 10:55
    Kudos to @ChuckPeddy, Very cool trick.  :)  Could have used that one a few times. ​

    ------------------------------
    Carmen Cruz
    Senior Specialist, Technical Consultant
    SWK Technologies Inc.
    Carmen.Cruz@SWKTech.com CA
    973-437-3984
    ------------------------------

    Original Message


Related Content