Job Effective Dated Row Insert (JEDI Process)

Purpose:  Use this document as a reference for creating a new effective dated data row in Job Data for a group of employees, such as full-time faculty, in situations where employees must be placed in short work break status and returned back from it. Additionally, the JEDI process can be run to update compensation for employees such as classified enrolled in Salary Plan data setup. JEDI can also perform a mass change of employees from one salary administration plan into another one if required to do so by OFM. Lastly, the JEDI update can be reversed if needed to, due to incorrectly used parameter(s), through the use of the Reverse Job Effective Dated Row process.

This QRG covers the following JEDI processes:

  • Place Full Time Faculty on Short Work Break
  • Return Full Time Faculty from Short Work Break
  • Compensation Update
  • Update Salary Admin Plan for OFM
  • Reverse Job Effective Dated Row

Audience:  Human Resource Specialists and/or Human Resource Administrators.

You must have at least one of these local college managed security roles:

  • ZC HR Employee Maintenance
  • ZZ HR Employee Maintenance

If you need assistance with the above security roles, please contact your local college supervisor or IT Admin to request role access.

Job Effective Dated Row Insert

Expand or collapse content Place Full Time Faculty on Short Work Break

IMPORTANT:  Do not run this process to place full-time faculty in short work break status until Balloon Payments have been processed. Please work with your payroll department to coordinate the processes.

Navigation:  Menu  > Workforce Administration > CTC Custom > CTC Processes > Create New Job Eff. Dated Row 

  1. The Create New Job Eff. Dated Row search page displays.
  2. Select the Add New Value tab and create a Run Control ID. (This step is strictly for the first run; after that you may use this new run control.)
  3. Select the Add button.
  4. The Create New Job Effective Dated Row page displays.
  5. Select the appropriate Company.
  6. Enter/Select the Effective Date for the Job Data Insert.
    NOTE:  The effective date in this instance will be the first day of payroll processing cycle when the employee is scheduled to be on Short Work Break (for example:  6/16/25 for employees going on short work break as of the 6B payroll processing or 7/1/25 for employees going on short work break as of the 7A payroll processing cycle.)
  7. In the Action field, select SWB action. This action will be populated in the employee’s full-time job data record upon process completion.
  8. Leave the Reason field blank for the SWB action.
  9. Select the appropriate PayGroup. When running this process for full-time faculty use FXX pay group where XX stands for two digit company code.
  10. Entry of the Contract Begin and Contract End Dates is not necessary when running this process to place faculty on short work break status. If an employee has contract begin and contract end dates populated on the most recent data row, these dates will auto populate on the newly created SWB inserted data row.
Create New Job Effective Dated Row page - Process Request Parameters section for SWB action.

In the majority of cases, users will be running this process for all full-time faculty set up with the FXX pay group. However, some users may opt to run this process for FXX pay group and specific department. If/when running the JEDI process to place full-time faculty on SWB status for a specific Department, please do the following:  

  1. Select the appropriate Department (if /when applicable).
  2. Entry of the Contract Begin and Contract End Dates is not necessary when running this process to place faculty on short work break status for FXX pay group and specific department
Create New Job Effective Dated Row page - Process Request Parameters section for SWB action, including Department..

WARNING:  The system WILL NOT create/insert a new row for an employee with an effective dated row that is greater than the date entered in step #6; or if the employee has an Expected Job End Date less than the effective date in step #6.

Should an employee have a future dated row greater than the effective date entered in step #6; a manual entry will need to be created Job Data. Additionally, if an employee has an Expected Job End Date that is less than the date entered in step #6; a manual entry will need to be created in Job Data.

Be sure to check your report results for validation.

This process WILL create an effective dated sequence for multiple actions with the same effective date.

  1. Select the Run button to activate the process request.
  2. The Process Scheduler Request page displays.
  3. Select the OK button.
  4. The Create New Job Effective Dated Row page displays.
  5. Make note of the Process Instance number.
  6. Select the Process Monitor link to view the progress of the request.
  7. The Process Monitor page displays.
  8. When the Run Status changes to Success and the Distribution Status changes to Posted, access the process log file to view and validate results. Pay close attention to populated errors. These will need to be resolved manually.

NOTE:  You should ALWAYS VALIDATE your data at the end of this process. Select a few individuals from the results list to validate in Job Data.
(Navigation: Main Menu > Workforce Administration > Job Information > Job Data)

Remember to look for those employees with a future dated row greater than the date selected for this process. Those employees will need to be updated manually.

Expand or collapse content Return Full Time Faculty from Short Work Break

Navigation: Menu > Workforce Administration > CTC Custom > CTC Processes > Create New Job Eff. Dated Row

WARNING:  The system WILL NOT generate a new effective dated row for the Return from Workbreak Action IF the Short Work Break Action is NOT the most recent previous action of record.

It may be best to run this process for both actions simultaneously (1st Run = SWB; 2nd Run = RWB)

  1. The Create New Job Effective Dated Row search page displays.
  2. Select an existing Run Control ID (or add a new Run Control Id value)
  3. The Create New Job Effective Dated Row page displays.
  4. Select the appropriate Company.
  5. Enter/Select the Effective Date for the Job Data Insert.
    NOTE: The effective date in this instance will be the first day of payroll processing cycle when the employee returns from Short Work Break.
    For example, 9/1/25 would be used for employees coming back from Short Work Break as of the 09A payroll processing or 9/16/25 for employees coming back from Short Work Break as of the 09B payroll processing cycle.)
  6. In the Action field, select the RWB action. This action will be populated in employee’s full-time job data record upon process completion.
  7. Leave the Reason field blank for RWB action.
  8. Select the appropriate Pay Group. When running this process for full-time faculty use FXX pay group where XX stands for two digit company code.
  9. Add Contract Begin and Contract End Dates when running this process to reflect employee’s contract begin and end dates for new academic year. These dates will populate for employee under the CTC_JOB_DATA tab in Job Data on newly inserted RWB data row.
Create New Job Effective Dated Row page - Process Request Parameters section for RWB action.

In the majority of cases, users will be running this process for all full-time faculty set up with the FXX pay group. However, some users may opt to run this process for FXX pay group and specific department. If/when running the JEDI process to place full-time faculty on SWB status for a specific Department, please do the following:  

  1. Select the appropriate Department (if applicable).
  2. Enter the Contract Begin Date (if applicable).
  3. Enter the Contract End Date (if applicable).
Create New Job Effective Dated Row page - Process Request Parameters section for RWB action, including Department.

WARNING:  The system WILL NOT create/insert a new row for an employee with an effective dated row that is greater than the date entered in step #5; or if the employee has an Expected Job End Date less than the effective date in step #5.

Should an employee have a future dated row greater than the effective date entered in step #5; a manual entry will need to be created in Job Data.
Additionally, if an employee has an Expected Job End Date that is less than the date entered in step #5; a manual entry will need to be created in Job Data.

  1. Select the Run button to activate the process request.
  2. When Run Status changes to Success and the Distribution Status changes to Posted, access process log file to view and validate results.  Pay close attention to populated errors.  These will need to be resolved manually.

NOTE:  You should ALWAYS VALIDATE your data at the end of this process. Select a few individuals from the results list to validate in Job Data.  (Navigation: Main Menu >  Workforce Administration > Job Information > Job Data)

Remember to look for those employees with a future dated row greater than the date selected for this process. Those employees will need to be updated manually.

Expand or collapse content Compensation Update

The JEDI process can be used to update the Compensation tab for employees, for example, Classified enrolled in Salary Plan data setup.

Navigation: Menu > Workforce Administration > CTC Custom > CTC Processes > Create New Job Eff. Dated Row

  1. The Create New Job Eff. Dated Row search page displays.
  2. Select the Add New Value tab and create a Run Control Id. (Colleges might consider using a separate Run Control ID when running compensation updates).
  3. Select the Add button.
  4. The Create New Job Effective Dated Row page displays.
  5. Select the appropriate Company.
  6. Enter/Select the Effective Date for the Job Data Insert. When updating an employee’s Compensation data to account for pay rate changes effective 7/1/25, be sure to use 7/1/2025 Effective Date.  
  7. In the Action field, select PAY (Pay Rate Change) action.  This action will be populated in employee’s full-time job data record upon process completion.
  8. In the Reason field, select COL (Cost of Living Adjustment).  (Select the look up tool to view other available reason choices for selection.)    
  9. Select the appropriate Pay Group such as for example C22.  When running JEDI process for compensation updates, our recommendation is that users do so for one pay group at a time.  
  10. Check the Calculate Compensation box.
  11. Lastly select correct Salary Plan, such as for example CS and/or ST in Salary Admin Plan area at the bottom of the run control page. In addition to running the JEDI process for compensation updates one pay group at time, we also recommend that users run such update one Salary Plan at a time.  
  12. Entry of the Contract Begin and Contract End Dates is not necessary when running this process to update compensation.
Create New Job Effective Dated Row page -- Process Request Parameters section for action PAY - Pay Rate Change, including pay group, salary admin plan and Calculate Compensation check box enabled.

In majority of cases, users will be running this process to update compensation for all employees in a specific Pay Group and Salary Plan. However, users may run this process for employees employed within specific Department, Pay Group, and Salary Plan.  If/when running the JEDI process to update compensation for employees employed within a specific department, please set up the parameters as shown below:

Create New Job Effective Dated Row page -- Process Request Parameters section for action PAY - Pay Rate Change, including pay group, department, salary admin plan and Calculate Compensation check box enabled.

WARNING:  The system WILL NOT create/insert a new row for an employee with an effective dated row that is greater than the date entered in step #6; or if the employee has an Expected Job End Date less than the effective date in step #6.

Compensation updates can be completed through the JEDI process for any employee group that utilizes Salary Plan data (classified, hourly, faculty).   Appropriate Salary Plan table must be updated first to reflect new rates prior to completing compensation updates in job data.

  1. Select the Run button to activate the process request.
  2. When Run Status changes to Success and the Distribution Status changes to Posted, access the process log file to view and validate results. Pay close attention to populated errors. These will need to be resolved manually.  

NOTE:  You should ALWAYS VALIDATE your data at the end of this process. Select a few individuals from the results list to validate in Job Data.  (Navigation: Main Menu >  Workforce Administration > Job Information > Job Data)

WARNING:  Employees employed with FTE value of <1 will need to have their compensation data manually updated in Job Data to ensure their semi-monthly rate of pay is calculated at the reduced percentage.

Expand or collapse content Update Salary Admin Plan for OFM

Salary Administration Plans can also be updated in mass through the JEDI process for any employee group, or groups, that are currently in one Salary Plan, for example, and have to be placed into another new or revised plan. Appropriate Salary Plan table entries must be updated first to reflect the new Salary Administration Plan identifiers prior to completing salary plan changes in job data, perhaps to meet new OFM requirements for example.

Prior to running the process to update the Salary Administration Plan, confirm with HCM Customer Support the following system configuration changes are in place:

  1. The new Salary Administration Plan exists.
  2. Salary Grades for the respective new plan are defined correctly per OFM requirements.
  3. Job codes and position numbers using the old plan are updated to the new Salary Administration Plan.

NOTE: The Colleges will need to identify Job Codes and Position Numbers that are set up with the old OFM plans: CS, ST, or SP.
Then, submit a request to HCM Customer Support to switch to the respective new OFM salary plans.

Use the query:  QHC_HR_OFM_JOBCODE_POSITION to identify the data:

-  Run this query; sort by Salary Plan (CS-Column H);
-  Insert new columns for the New Salary Plan for BOTH Job Code and Position.
-  Return this information by using the ticketing system with the subject of OFM Job Code and Position.
-  DO NOT ATTEMPT THE JEDI PROCESS UNTIL THE DATA PROVIDED HAS BEEN CHANGED AND THE TICKET IS CLOSED!

Prior to running the JEDI process:

  1. Run the QHC_HR_JOB_DATA_OFM query to get a current data snapshot for comparison purposes.
    NOTE: You are to run this same query after completing the JEDI process (Step 18) as the comparison/validation of the updates.

Run the JEDI process to update the Salary Administration Plan for OFM:

Navigation: Menu > Workforce Administration > CTC Custom > CTC Processes > Create New Job Eff. Dated Row

  1. The Create New Job Eff. Dated Row search criteria page displays.
  2. Select the Add New Value button and enter a Run Control Id. (Colleges might consider using a separate Run Control ID when running salary plan updates.)
  3. Select the Add button.
  4. The Create New Job Effective Dated Row Process Request Parameters page displays.
  5. Enter or select the appropriate Company.
  6. Enter/Select the Effective Date for the Job Data Insert. For example, when updating employees from one Salary Administration Plan to another plan that has to be processed on a certain payroll, such as 09B, use the Effective Date for the start of that payroll period. For this example, be sure to use the Effective Date: 09/16/2025.  
  7. In the Action field, select DTA (Data Change) action.  This action will be populated in employee’s full-time job data record upon process completion.
  8. In the Reason field, select OFM (OFM Correction).  (Select the look up tool to view other available reason choices for selection.)    
  9. Be sure the Calculate Compensation check box is turned OFF.
  10. Turn ON the Modify Salary Admin Plan check box.
  11. Select the appropriate Pay Group such as C09, for example. When running JEDI process for salary admin plan updates, our recommendation is that users do so for one pay group at a time. For example: Classified - Cxx) or NRA Classified - xxC.
  12. Departments field:  This is not required, however, if a value is entered, processing is limited to the specific department.
  13. Union Code field:  If left blank, the JEDI will process WFSE, WPEA and Non-represented. Selecting one of the values from the lookup will limit to job records that are set up with the respective union code.
  14. Lastly, select the correct Salary Administration Plan that employees are currently set up, for example:  CS, SP or ST. To accommodate multiple plans on the same run, use the Add a New Row icon [+] at the end of the row. The JEDI process determines the new plan for the employee based on the old plan:
    • 00CS - (Non-Represented)
    • 00SP - (Non-Represented SP)
    • 00ST - (Non-Represented ST)
    • 01CS - (WFSE)
    • 01SP - (WFSE SP)
    • 01ST - (WFSE ST)
    • 02CS - (WPEA)
    • 02SP - (WPEA SP)
    • 02ST - (WPEA ST)

 

Create New Effective Dated Row page - Process Request Parameters section.
  1. Select the Run button to activate the process request.
  2. When the Run Status changes to Success and the Distribution Status changes to Posted, access the process log file to view and validate results. Pay close attention to any populated errors. These will need to be resolved manually.
  3. Run the query QHC_HR_JOB_DATA_OFM after the JEDI process to validate/confirm the updates, as well as confirm that data that was not part of the update process is unchanged/stayed the same.
Expand or collapse content Reverse Job Effective Dated Row

Should a situation arise where the JEDI process was completed (for short work break, return from work break, or compensation update) with an error due to a wrong parameter selection, HCM users have an ability to reverse JEDI process results by running Reverse Job Effective Dated Data Row process.

Navigation: Menu > Workforce Administration > CTC Custom > CTC Processes > Reverse Job Eff. Dated Row

  1. The Create New Job Eff. Dated Row search page displays.
  2. Select the Add New Value tab and create a Run Control ID.
  3. Select the Add button.
  4. The Create New Job Effective Dated Row page displays.
  5. Select the Company code for which the JEDI process was completed.
  6. Enter/Select the Effective Date that was in JEDI process update.  
  7. In the Action, Reason, Pay Group fields, select the values used in JEDI process update.  
  8. If the Department field was used in JEDI process update, additionally list it in this process reversal.
Reverse Job Effective Dated Row page -- Process Request Parameter section, including pay group.

NOTE:  While the Reverse Job Effective Dated Data Row parameters page does not show Compensation Calculation box nor Salary Admin Plan fields, it will complete successfully for reversal of compensation updates.

  1. Select the Run button to activate the process request.
  2. When Run Status changes to Success and the Distribution Status changes to Posted, access the process log file to view and validate results.

NOTE:  You shouldALWAYS VALIDATEyour data at the end of this process. Select a few individuals from the results list to validate in Job Data. (Navigation: Main Menu > Workforce Administration > Job Information > Job Data)

End of procedure.

Video Tutorial

The video below demonstrates the process actions described in steps listed above. There is no audio included with this video. Select the play button to start the video.

Video Tutorial via Panopto

View the external link to Job Effective Dated Row Insert (Short Work Break). This link will open in a new tab/window.

Compensation updates can be completed through the JEDI process for any employee group that utilizes salary plan data (classified, hourly, faculty). Appropriate Salary Plan table must be updated first to reflect new rates prior to completing compensation updates in job data.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.