UCPath Salary Cost Transfer Troubleshooting Guide


Overview


This article provides a troubleshooting guide for resolving errors encountered when entering Chartstring within Salary Cost Transfer (SCT). It offers step-by-step instructions to help users navigate and troubleshoot issues effectively.

Next Steps


If you receive SCT is balanced after you move all of the VAC and HOL earnings but it comes back unbalanced:


If you receive a warning message stating, ' This SCT has a Fund or Project ID with Salary Cap configured. Please verify the fund or project ID is appropriate. (32001,1851).


If you receive an error 'No rows changed - Please make a change':


Important: For sponsored projects ONLY, it may be necessary to do a direct retro in UCPath for May 2020 and June 2020 data, allowing it to align with UCPath data on the correct project.

Note: DRs for May 2020 & June 2020 will need an extra step of review/action, if the sponsored project ended before May 2020.

Instructions:

  1.  Confirm the Oracle sponsored project where the original May and June 2020 transactions posted to review the reports from FinLink and the Oracle IFIS conversion data in PPM
  2.  Process a PPM cost transfer in Oracle  - move the conversion payroll costs off of the original sponsored project and onto the default, in order to net against the credit resulting from the DR  - this step is necessary because the payroll costs for May and June 2020 were originally posted in IFIS and the balance came through the IFIS conversion costs
  3.  If the last step is not done, May 2020/June 2020 data will be accounted for on two projects in Oracle (the original sponsored project and the intended project)

Questions?


If you need any additional assistance, please submit a ticket here.