Sage 100

 View Only

  • 1.  Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 07:06
    Sage 100 2018 upgrade from 2017 with payroll - check history did not come over - the files are empty in 2018. Customer was not keeping perpetual history in 2017. Does this mean I have to export from 2017 and import into 2018?


  • 2.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 10:16
    so they didn't even get YTD values for 2018?


  • 3.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 10:25
    The Check history tables are empty in 2018. The earning and deduction tables all appear to be intact


  • 4.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:03
    2018 Payroll Conversion program uses the PR5 Check History file, not the PR_22 Perpetual History file.


  • 5.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:09
    PR5 Check History File also gets cleared at EndOfYear, in case they are converting an old company.


  • 6.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:11
    That file has data in the 2017 company. Anyone else seen this?


  • 7.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:21
    Anything in the conversion log about that?


  • 8.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:29
    Also check source PR5 file. Program says recs with ""PURGED"" in pos 16-21 will be skipped in the conversion.


  • 9.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:40
    PR5 has 1999 records in 2017. None say PURGED in them.


  • 10.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 12:51
    If 2018 Payroll upgrade/conversion program has problem opening PR5, it puts a message in the log file saying: ""Unable to open PR5ccc"".


  • 11.  RE: Sage 100 2018 upgrade from 2017 with payroll - che

    Posted 05-18-2018 13:45
    PR5 not found in any log file


Related Content