x Want to participate? Join the group to interact
Options
  • Replies 19 replies
  • Subscribers 73 subscribers
  • Views 6298 views
  • Users 0 members are here
Browse Forums
Announcements
152
topics
130
replies
General Discussion
370
topics
732
replies
Sage HRMS Training
139
topics
97
replies
Troia

Sage HRMS and Sage Abra Suite: Announcing Sage HRMS and Sage Abra Suite Q2 2020 product update

Posted By

***Note*** The Sage HRMS Q2 2020 product update is currently unavailable as we investigate an issue with the Crystal Reports runtime. If you have already installed the update and are experiencing issues please refer to KB 105549.”

 What's new

  • Payroll tax updates
  • Payroll product updates
  • HR product updates
  • Sage Payroll and Tax Forms and eFiling by Aatrix

For detailed information about these releases, see:

Download and install this update

Important:　If you use third-party products that integrate with Sage HRMS or Sage Abra Suite, check with the vendor of your third-party product to ensure these product is fully compatible with these releases. If you integrate with other Sage products, check with your business partner or Sage to ensure that these components are compatible.

Note: There is no update for the Employee Self Service (ESS) for Abra Suite.

Click applicable link below  to download and install the update:

If you are prompted to log on, enter your Customer Portal Username and Password, and then click Log on.

Questions?

Visit the Sage City Customer Resources page at www.SageCity.com/Resources page for additional resources, including links to Sage Knowledgebase, Sage City and Sage University, as well as Live Chat and Online Case submission.

Parents

  • This update is very flawed.  I installed the current HOTFIX but now no one can run an earning and hours report.  Are there any current fixes to this?  Thanks for any help.

  • in reply to MelanieL

    On June 23, we applied the quarterly update and ran into issues running reports on Thursday. I originally made a post on here Thursday but removed it later in the day. The issue I ran into on the reports were with date fields and number type parameters.

    In the UPCHKH, UPCHKD, and UPEMPL views (probably others too) in SageHRMS_Live, some of the fields changed from datetime to a decimal(9,0). According to Sage Support, the fields were listed as a decimal(9,0) in the payroll databases. I verified and agree with their statement that the payroll databases were decimal(9,0); however, many of the reports provided use the SageHRMS_Live views where the data type was a datetime.

    Specific fields I had issues with on Delphia and our own custom reports were:

    1. UPCHKD.EARDEDDATE
    2. UPCHKD.PEREND
    3. UPCHKH.TRANSDATE
    4. UPCHKH.PERSTART
    5. UPCHKH.PEREND
    6. UPEMPL.HIREDATE
    7. UPEMPL.FIREDATE

    For some reason, the crystal reports window form viewer did not want to run a report with a number type parameter - it kept coming up with UNSPECIFIED ERROR. I had to change the parameter to a string type and then in the record select statement change to a number.

    Reports from Delphia Consulting that contained one or more of these fields include:

    1. dc_payrolldepreq-AHDA.rpt
    2. dc_cddrdetail_daterang-AHDA.rpt
    3. dc_cddrsum_daterange-AHDA.rpt
    4. dc_tax summary by Employee-AHDA.rpt
    5. dc_deduction summary by Employee.rpt
    6. dc_earnings summary by EMployee.rpt

    "Troy will be the analyst assisting you through the technical review and guidance/recommendations to address your questions on running custom reports after applying Q2."  I have not heard from Troy but moved forward with modifying the reports we needed for this week. Sage Ticket Number: 8008252485

Reply
  • in reply to MelanieL

    On June 23, we applied the quarterly update and ran into issues running reports on Thursday. I originally made a post on here Thursday but removed it later in the day. The issue I ran into on the reports were with date fields and number type parameters.

    In the UPCHKH, UPCHKD, and UPEMPL views (probably others too) in SageHRMS_Live, some of the fields changed from datetime to a decimal(9,0). According to Sage Support, the fields were listed as a decimal(9,0) in the payroll databases. I verified and agree with their statement that the payroll databases were decimal(9,0); however, many of the reports provided use the SageHRMS_Live views where the data type was a datetime.

    Specific fields I had issues with on Delphia and our own custom reports were:

    1. UPCHKD.EARDEDDATE
    2. UPCHKD.PEREND
    3. UPCHKH.TRANSDATE
    4. UPCHKH.PERSTART
    5. UPCHKH.PEREND
    6. UPEMPL.HIREDATE
    7. UPEMPL.FIREDATE

    For some reason, the crystal reports window form viewer did not want to run a report with a number type parameter - it kept coming up with UNSPECIFIED ERROR. I had to change the parameter to a string type and then in the record select statement change to a number.

    Reports from Delphia Consulting that contained one or more of these fields include:

    1. dc_payrolldepreq-AHDA.rpt
    2. dc_cddrdetail_daterang-AHDA.rpt
    3. dc_cddrsum_daterange-AHDA.rpt
    4. dc_tax summary by Employee-AHDA.rpt
    5. dc_deduction summary by Employee.rpt
    6. dc_earnings summary by EMployee.rpt

    "Troy will be the analyst assisting you through the technical review and guidance/recommendations to address your questions on running custom reports after applying Q2."  I have not heard from Troy but moved forward with modifying the reports we needed for this week. Sage Ticket Number: 8008252485

Children

*Community Hub is the new name for Sage City