Result Tables
Overview
Result tables store the calculated output of the engine by result type. They are the first place to look once you know a payee was identified and processed.
Common Result Tables
| Table | Content | Typical use in analysis |
|---|---|---|
GP_RSLT_ERN_DED | Earnings and deductions | Validate resolved pay values and supporting identifiers |
GP_RSLT_PIN | PIN-level values and resolution outcomes | Trace intermediate values and supporting elements |
GP_RSLT_ACUM | Accumulator balances | Check balance assignment and corrective versus forwarding impact |
GP_RSLT_ABS | Absence results | Review entitlement and take behavior |
GP_RSLT_DELTA | Retro deltas | Confirm forwarded retro output |
Reading Results Correctly
Result tables are easiest to interpret when joined back to:
- calendar context
- payee process status
- segment status
- PIN or element definition tables
A technically correct amount written to the wrong segment, wrong calendar, or wrong balance period is still an incorrect business result.
Recommended Analysis Order
- confirm the payee exists in
GP_PYE_PRC_STAT - confirm the right segment exists in
GP_PYE_SEG_STAT - review
GP_RSLT_PINif you need the calculation chain - confirm final values in the specialized result table
Key Takeaways
- Result tables show what happened, not necessarily why.
GP_RSLT_PINis often the bridge between status analysis and final-value analysis.- Always read results together with calendar and segment context.