Run Types
Overview
Run types define what kind of calculation a calendar will perform and which process list the engine should use. They are the contract between the calendar, the batch engine, and the processing rules that should be active for that run.
Run Type Configuration
Page And Purpose
| Purpose | Component |
|---|---|
| Define processing parameters | GP_RUN_TYPE |
| Typical navigation | Set Up HRMS > Product Related > Global Payroll & Absence Mgmt > Framework > Processing > Run Types |
Key Options
| Option | Impact |
|---|---|
| Calculation Type | Determines payroll versus absence processing behavior |
| Process List | Controls section and element resolution order |
| Retro Trigger Processing | Decides whether retro triggers are consumed in the run |
| Allow Duplicates | Controls duplicate segment behavior |
| Retro Adjustment Sources | Allows deltas from other run types to forward into the current run |
| Time Reporting Codes | Supports Time and Labor integration |
| Variable Compensation Awards | Links run types to award-driven earnings processing |
Effective-Dated Behavior
One of the more important Oracle design notes is that run types are effective-dated so the system can reproduce retro calculations using the settings that were in force at the time of the original run. That matters when process lists or retro handling rules change over time.
Duplicate And Retro Considerations
- Duplicate handling affects how segment status records are reused or newly created.
- Retro triggers can be enabled at run type level and then further controlled at calendar or calendar-group level.
- Additional retro adjustment sources are useful when an infrequent run type, such as bonus, needs to forward deltas into a more regular payroll run.
Operational Rule
After processing begins, do not edit the Run Types page unless you cancel the pay run. Changing run type behavior mid-cycle undermines reproducibility and supportability.
Key Takeaways
- Run type is the execution identity of the calendar.
- Process list selection is the most consequential run type dependency.
- Effective dating and retro adjustment sources are essential for repeatable payroll behavior.