Employee NOT Appearing on Successful Load to Job or Load to Job Error Report

If the employee you tried to Load to Job, does not appear on the Successful Load to Job Report or the Load to Job Error Report, confirm the following before submitting a ServiceNow Ticket:

1. The Action/Reason is correct.
2. The Eff Seq is not 1 or more without an Eff Seq of 0 being loaded at the same time. (Note: DO NOT change the Eff Seq to 0 unless the row that has Eff Seq 0 is changed first.)

Load to Job Error Message Meanings

When transaction appears on the Load to Job Error Report, and user is unable to resolve the reason the transaction appeared on the Load to Job Error Report, user can either:

1. Submit a ServiceNow Ticket
2. Follow the “~Manual Load to Job” process:
   • Manually enter the transaction into Job Data, based on the information on the My Approvals page.
   • Return to the My Approvals page, select “~Manual Load to Job” in the Other Action field, check the “Approve” box and click “Save & Submit”.
   • The transaction will no longer appear on the My Approval page.

1. Unexpectedly ended up with three appointments attached to one appointment number:
   1. Unfortunately, once multiple appointments are submitted with the same appointment number they cannot be separated. The only way to separate the appointments is to request CMS to delete the data from the TAE Staging, History, and Letter tables. A ServiceNow ticket will need to be submitted with the following information:
      • CHRS ID
      • Empl Record Number
      • Department ID
      • EE Group
      • Appointment Number
2. For EE Group 06- Substitutes, had two appointments attached to one appointment number, but only one appointment loaded to job successfully:
   1. When this occurs, user will be need follow the “~Manual Load to Job” process:
      • Manually enter the transaction into Job Data, based on the information on the My Approvals page.
      • Return to the My Approvals page, select “~Manual Load to Job” in the Other Action field, check the “Approve” box and click “Save & Submit”.
      • The transaction will no longer appear on the My Approval page.

1. When trying to cancel an appointment after the transaction has already loaded to job, the transaction disappears from the My Approval page without loading to Job:
   1. If certain fields (Term, Session, Appt Type, Eff Dt, End Dt, etc.) do not match exactly what was entered for the original transaction that was loaded to job, the Cancel After Loaded to Job process will not work. When certain fields do not match what was originally entered for the transaction, the module treats the cancelation as if it is a Mid-Process Cancel rather than a Cancel After Loaded to Job. Using the TAE Approval History page review the original transaction submitted and the transaction submitted as a Cancel.
      • If the certain fields (Term, Session, Appt Type, Eff Dt, End Dt, etc.) are different, the transaction will need to be submitted again with the fields matching.
      • If all the field are matching a ServiceNow ticket will need to be submitted with the following information:
        • CHRS ID
        • Empl Record Number
        • EE Group
        • Details of the Original Appointment from the TAE Approval History page review
        • Details of the Canceled Appointment from the TAE Approval History page review
2. When processing a “No Change” the transaction disappeared and did not load to job:
   1. When “No Change” is in the Other Action field, the transaction does not load to job and will fall off the My Approval page once the Appointment Notification has been sent.
3. When processing an appointment, the notification was NOT generated, the reports did not appear, the transaction did NOT load to job and has disappeared from the My Approval page:
   1. This could occur for various reasons.
      • Begin by confirming the following items below. If any of the reasons for the notification was NOT generating, the reports NOT appearing and the transaction NOT loading to Job and disappearing, are listed below, will need to submit the transaction again.
        1. On the WorkFlow Approvers page, confirm that the user who approved the transaction has access to the Final Load to Job step.
        2. On the Workflow Steps page, confirm that the workflow is set up correctly for the transaction being submitted. You will want to confirm that the workflow has the Load to Job and Send Appt Notif box checked at one of the steps.
        3. On the User Profile page, confirm the user has the CHR_PT_PeopleSoft_Advance role.
      • If after reviewing, it is found that the reason for the notification was NOT generating, the reports NOT appearing and the transaction NOT loading to Job and disappearing, is not listed above submit a ServiceNow ticket. The ServiceNow ticket will need to be submitted with the following information:
        1. Details of the Original Appointment (CHRS ID, Empl Record Number, EE Group)
        2. Details of Final Approver (CHRS ID, Campus ID, Approval Workflow access)
        3. Image of the Workflow Steps
        4. Details of the appointment from the TAE Approval History page review

1. The Session Code is not auto-populating to Session 1 for certain Terms entered on the TAE Appointment Data Entry page:
   1. There are two reasons that this could be occurring:
      • First review the Session Code table and confirm that a Session Code has not created starting with a zero. If a Session Code has been created, you will need to update this on both the Session Code table and the Term table.
      • Second review the Term table to confirm that the Description and Short Description field only have numbers, letters, and spaces. If the Description and Short Description field have other characters beyond that, you will need to update.
2. The Session Code is not generating values when clicking on the magnify glass on the TAE Appointment Data Entry page:
   1. This could be occurring because the Term table has not been setup correctly. The Description and Short Description field on the Term table should only have numbers, letters, and spaces. If the Description and Short Description field have other characters beyond that, you will need to update.
3. The Session Code is not generating the correct dates:
   1. There are two reasons that this could be occurring:
      • First review the Session Code table and confirm that a Session Code has not created starting with a zero. If a Session Code has been created, you will need to update this on both the Session Code table and the Term table.
      • Second review the Term table to confirm that the Description and Short Description field only have numbers, letters, and spaces. If the Description and Short Description field have other characters beyond that, you will need to update.

1. Workflow Approver page is not allowing for me to insert a new step in the middle of the workflow process:
   1. Users are not able to insert a step in the middle of the workflow as the module does not have that functionality. To add a step to the workflow, users will need to add the step at the end of the workflow and relabel the prior steps. This process is explained through the Update TAE Approval Workflows Job Aid located in the CHRS Library under Training.
2. Not all workflow steps are appearing on the WorkFlow Approvers page:
   1. If you set up your workflow by EE Group and job code, you need to search by EE Group and job code on the Workflow Approvers page.
   2. If you set up your workflow by EE Group, job code and department, you need to search by EE Group, job code and department on the Workflow Approvers page.
   3. If you setup your workflow by EE Group and department, you need to search by EE Group and department on the Workflow Approvers page.
   4. If you recently inactivated a workflow and did not create a new Workflow with a higher month than the recently inactivated, then the new workflow step will not appear on the WorkFlow Approvers page.
3. Fields that should be hidden from approvers are still visible:
4. If you setup your workflow by EE Group and job code, you need to setup the hidden fields by the same EE Groups and job codes. Otherwise, the fields will remain visible to the approver.
   1. If you setup your workflow by EE Group, job code and department, you need to setup the hidden fields by the same EE Group, job code and department. Otherwise, the fields will remain visible to the approver.
   2. If you setup your workflow by EE Group and department, you need to setup the hidden fields by the same EE Group and department. Otherwise, the fields will remain visible to the approver.
5. When adding an approver to the Approver Workflow page and checking the "Auto-Change by Position Nbr", the correct person is not being pulled:
   1. When "Auto-Change by Position Nbr" is selected if more than one incumbent shares the position number the most recently added incumbent will pull. You will need to uncheck the "Auto-Change by Position Nbr" field so that the approver does not update.
6. Values on the TAE Appointment Type table still appearing after requested to be removed:
   1. Values on the table are never removed, only inactivated due to the standardization of the table. Although the table is standardized each campus has their own version under their campus business unit which allows them to request different values to be inactivated. Values that have been inactivated will no longer appear as a drop down option on the TAE Appointment Data Entry Page.

Certain TAE pages have the ability for data to be updated based on Position Number or Empl ID changing. The scheduled job process TAE Update Approvers/Authority (TAEAUTO) will target those pages and make the updates. When updates cannot be made, an error message will produce and restrict updates from occurring. The errors will appear on the CSU Update Appr/Auth Error Log for review.

A ServiceNow ticket should be opened if

• You are unable to resolve the error.
• Need to request for the TAEAUTO process to be ran off-schedule for your campus.

Job Aid: Pending