Key Pages & Components Reference
Overview
This page summarizes the purpose of the most important setup and processing pages used in the calendar framework.
Reference Table
| Page / Component | Primary use | Notes |
|---|---|---|
GP_RUN_TYPE | Define calculation type, process list, retro, and duplicate handling | Effective-dated for reproducible retro behavior |
GP_CALENDAR_PERIOD | Define single period IDs | Use GP_AUTO_PRD for mass generation |
GP_CALENDAR1 to GP_CALENDAR4 | Define calendar header, payees, overrides, and exclusions | Review target calendar and holiday pay date handling |
GP_AUTO_CAL1 | Create sets of calendars automatically | Generated calendars can still be reviewed and edited |
GP_CALENDAR_RUN | Sequence calendars into a run-control group | Controls open-group behavior and dependencies |
GP_RUNCTL | Launch Identify, Calculate, Finalize, and control options | Reuse for restart after abort |
GP_RUNCTL_SEC | Review prior processing action after abort | Helps with restart decisions |
GP_RUNCTL_DBUG_SEC | Produce element chain and performance statistics | Use only for targeted troubleshooting |
How To Use This Reference
- use component names when reading Oracle documentation
- use page purpose to decide whether an issue is setup, processing, or publishing related
- keep local screenshots aligned to the same component names for training material
Key Takeaways
- A small set of components controls most operational behavior.
- Component names are often more stable than menu wording across documentation sets.
- Internal runbooks should refer to both the navigation path and the component name.