Skip to main content

Process & Segment Status Records

Overview

Status records tell you where the engine is or where it stopped. They are often more useful than result tables when a process did not complete successfully.

Core Records

RecordScopeUse
GP_PYE_PRC_STATPayeeTracks overall payee processing state
GP_PYE_SEG_STATSegmentTracks segment-level state
Run control recordsProcessConnect batch invocation to calendar groups and restart behavior

Selection Status Examples

StatusMeaning
ActiveSelected because the payee is active in the calendar
InactiveSelected because of positive input, retro, or forwarding despite inactivity
Suspended by UserManually held out of processing
Suspended by SystemBlocked because of another open group or other control issue
CancelledExplicitly removed from processing

Calculation Status Examples

StatusMeaning
CalculatedSegment has been calculated
Calculated - CorrectedSegment was recalculated after changes
FrozenSegment is locked from calculation changes
FinalizedSegment is finalized
Finalized - With BankingFinalized and banking has already executed
Reversed / Recalculated combinationsIndicate more advanced correction paths in special cases

Process Indicators

Oracle also maintains process indicators such as:

  • Cancel
  • Calculate
  • Finalize
  • Freeze
  • Identify
  • Suspend
  • Uncancel
  • Unfreeze

These indicators are useful when diagnosing restart, suspension, and operator-action history.

How To Use Them

  1. confirm Identify created the expected payees
  2. verify whether the segment is open, frozen, suspended, or finalized
  3. compare process indicators with operator actions on run control
  4. only then move into result-table analysis

Key Takeaways

  • Status records are the fastest route to locating runtime failure points.
  • Restart decisions should be based on current status, not assumptions.
  • Segment status is especially important in retro, segmentation, and off-cycle analysis.