9.2 Running the Other Earnings Register Report

Purpose: Use this document as a reference for running the Other Earnings report in ctcLink.

Audience: Payroll Administrators.

Run the Other Earnings Register Report

Navigation:  NavBar > Navigator > Payroll for North America > Payroll Processing USA > Pay Period Reports > Other Earnings Register

  1. The Other Earnings Register page displays.
  2. Enter an existing Run Control ID or select the Add a New Value tab to create a new one.
  3. Enter the new Run Control ID.
  4. Select the Add button.
Other Earnings Register search add a new value
  1. The Other Earnings Register page displays.
  2. Enter the desired information into the Pay Run ID field.
    • You may use the look-up tool (magnifying glass icon) to select the correct ID.
  3. Select the On-Cycle radio button.
  4. Select the Run button.
Other Earnings Register page
  1. The Process Scheduler Request page displays.
  2. Select the OK button.
Process Scheduler Request
  1. The Other Earnings Register page displays.
  2. Make a note of the Process Instance number.
  3. Select the Process Monitor link.
Other Earnings Register page select process monitor link
  1. The Process Monitor page displays.
  2. Select the Refresh button until the Run Status is Success and the Distribution Status is Posted.
  3. Select the Details link.
Process Monitor page
  1. The Process Detail page displays.
  2. Most of the items on the Process Detail page are view only; however, you can use some tools to modify the process run, as needed.
  3. Select the View Log/Trace link.
Process Detail page view log/trace link
  1. The View Log/Trace page displays.
  2. To view the report, select the PDF link in the File List section.
View Log/Trace page
  1. The report opens in a separate window.
  2. View results of the report, and close the window when finished.
Other Earnings Register report
  1. You have successfully run the other earnings register report.
  2. End of procedure.

0 Comments

Add your comment

E-Mail me when someone replies to this comment