Error Explanations

Error #01 – Approver(s) security problem

Reason: The approver has HRMS security access but it is not set up correctly.

Solution:

  • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • Contact the HRMS Security Administrator at HRMS.Security@ubc.ca.
  • Re-submit your transaction after the problem has been fixed.

Error #02 – Approver(s) no longer active

Reason: The primary approver is not currently an active employee.

Solution:

  • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • If you get this error on a Financial Signing Authority approval step contact your departmental FMS Web Security Administrator to have this problem fixed:
  • For any other type of approval step you must fix your departmental approval rules stored in the Workflow Central Rules Repository.  To see your rules, please click on the hyperlink in the Review and Confirm Approvers page or run the HRMS Query400_HRMS_WORKFLOW_RULES“.
  • This problem is most likely caused by a position (referred to in the rules for your department) that is vacant or that the person in the position is on leave.  If this is the case, fill out a Workflow Rules Authorization Form, provide the updated information, and email it to the HRMS Workflow Administrator at HRMS.Workflow@ubc.ca.
  • Re-submit your transaction after the problem has been fixed.

Error #03 – Approver(s) security problem

Reason:  You can receive this error for one of 2 reasons:

  • Workflow could not find a Faculty/Staff CWL account for the approver.
  • There is no ‘Primary Financial Officer’ identified in the FMS Signing Authority system for the P/G associated with the speedchart used on your transaction.

Solution:

  • If this is a CWL problem:
    • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
    • If the approver does not have CWL, have them create a Faculty/Staff CWL account.
    • If they have a student CWL account, have them convert it to a Faculty/Staff CWL account.
    • If they have a guest CWL account, have them contact the HRMS Security Administrator at HRMS.Security@ubc.ca.
    • Have them complete an HRMS Access Request Form and request access to the appropriate department.
  • If this is a Signing Authority problem:
  • Re-submit your transaction after the problem has been fixed.

Error #04 – Approver(s) security problem

Reason: The approver previously had an HRMS account but it is currently inactive.

Solution:

  • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • Have the approver complete an HRMS Access Request Form and request access to the appropriate department.
  • Re-submit your transaction after the problem has been fixed.

Error #05 – No Primary Approver Found

Reason: There is no valid primary approver defined in the central rules repository for this transaction.

Solution:

  • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • Complete a Workflow Change Request Form, provide the updated information, and email it to the HRMS Workflow Administrator at HRMS.Workflow@ubc.ca.
  • Re-submit your transaction after the problem has been fixed.

Error #06 – Approver(s) security problem

Reason: The approver has HRMS security access but it is not set up correctly.

Solution:

  • Do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • Contact the HRMS Security Administrator at HRMS.Security@ubc.ca.
  • Re-submit your transaction after the problem has been fixed.

Unable to select ‘Yes’ in Approvers List

Reason: There are no Financial Approvers found for the Speed Charts used.

Solution:

  • Click Return and do a Save for Later or Save as Draft for your transaction so you don’t lose your work.
  • Check the FMIS Signing Authority setup for your department.
  • It is possible that the PG being used does not exist or is no longer active.
  • If you need more assistance, contact your departmental FMS Web Security Administrator to have this problem fixed:

Comments are closed, but trackbacks and pingbacks are open.