Key Database Tables

Overview

The data model links setup objects to runtime status and results. Knowing the main tables helps isolate whether an issue started in configuration, processing status, or published output.

Table Relationships

Selected entity

GP_CALENDAR

Stores calendar definition headers, including run type, period, payment date, and status controls.

• GP_RUN_TYPE
• GP_CAL_PRD
• GP_PYE_PRC_STAT

High-Value Tables

Table	Role	Category
GP_CALENDAR	Calendar header and runtime control	Setup / runtime bridge
GP_CAL_PRD	Period definitions	Setup
GP_RUN_TYPE	Run type configuration	Setup
GP_PYE_PRC_STAT	Payee process status	Runtime status
GP_PYE_SEG_STAT	Segment process status	Runtime status
GP_PAYMENT	Payment output staging	Downstream output

How To Use This Model In Support

1. start with the setup table that defines the object
2. move to the status table that proves it was used
3. inspect the result table that shows the outcome
4. check the downstream table only after finalized output is confirmed

Key Takeaways

• Start with GP_CALENDAR and status tables to understand runtime state.
• Setup, runtime, result, and downstream tables each answer different support questions.
• Data model literacy shortens production triage time significantly.

Related Pages

• Result Tables
• Status Records
• Batch Programs