Known Issues

Overview

This page captures issues that we are currently aware of, including current status. If you identify and issue not on this list, please contact effortreporting@uw.edu.

Work In Progress

  • System timeouts are moving users from the UW or UWM system instance into the APL instance without notification, requiring the user to logout and sign back into their original instance.
     
  • Workday payroll reports (e.g. R1269.1) will display different pay period dates for the same Retro Pay result lines depending on the user's security role. When the true "Earned Period End Date" and the obscured value (obscured as "Accounting Date" value) differ to dates that span across the boundaries of an ECC period, discrepancies will occur when attempting to reconcile ECC statements with Workday data.
     
  • Retro pay in Workday can cause salary over the cap to be calculated on workers whose salary/wages are not over the salary cap. This is a Workday global issue that needs to be fixed by Workday. There is no estimated date of resolution at this time. 
     
  • Awards with Purpose Code of "IPA/JPA/SA" are triggering effort and project statements to require certification, when these award types did not require certification in the legacy system and should be excluded from certification in ECC. PAFC is manually moving statements in this situation to "Auto Approved" while a solution to have them excluded automatically is being worked on.
     
  • ECC system generated emails sent from effortreporting@uw.edu are being flagged as 'unverified' or 'untrusted' when received by users.

Completed

  • A small number of non-faculty and all non-faculty PIs are having their payroll load to effort statements in ECC, rather than project statements. For all periods starting 01/01/2025, these workers will appear on project statements.

    For workers in this situation a note should be left on the statement indicating: "Due to the design of ECC’s business rules at the time of the FY24 reports being built and certified, *insert worker's name* had their payroll load to effort statements rather than project statements".
     
  • Stipends are appearing on Project Statements for individuals that were paid via that pay type. Stipends will be excluded from the Workday integration beginning in January 2025. PIs are not required to certify the reasonableness of stipends; if a Project Statement contains all stipend pay, contact PAFC and the statement can be marked as "Auto Approved" or "Certification Not Required." If a Project Statement contains both stipend and wages, only the wage portion must be reviewed for certification purposes.
     
  • Small number of instances where "Certified Effort" and "Computed Effort" columns differ on an effort statement. Users can fix this and bring the two columns back to alignment by clicking the "Reset Statement" button on the top left corner of the effort statement - screenshot

    Update: This is a result of current expected functionality in ECC. When a statement gets pre reviewed, it saves the values present in the "Certified" effort column, so if a change is made after the pre review is done, it will update the "Computed Effort" column only, until the "Reset Statement" button is clicked.

Post Award Fiscal Compliance email: gcafco@uw.edu

For questions and issues relating to Effort Reporting, email: effortreporting@uw.edu

Login to ECC