PA0008 table — PA0008 Basic Pay Infotype Table

One row is a single validity-delimited version of an employee's basic pay as held in infotype 0008. A personnel number can have several rows in this table simultaneously, each covering a non-overlapping BEGDA to ENDDA period, plus a SEQNR for same-day changes. A row carries the pay scale type, area, group and level (TRFAR, TRFGB, TRFGR, TRFST), the capacity utilization level (BSGRD), annual salary (ANSAL) and currency (WAERS), and up to twenty pairs of wage type and amount fields (LGA01 through LGA20 with BET01 through BET20, and corresponding number fields) that represent the fixed and recurring pay components valid for that period. It does not store one-time payments, that belongs to other infotypes; PA0008 is specifically the recurring, structurally-driven pay elements.

MANDT is the client field, always restrict on it first in any direct table access. PERNR plus the date range is the real key for selectivity; never select PA0008 without at least one of PERNR, a personnel number range, or a payroll area join, because the table carries one row per employee per pay change and grows continuously across the org. When checking pay 'as of' a date, filter BEGDA less than or equal to the key date and ENDDA greater than or equal to it, do not assume the most recent row by AEDTM is the currently valid one; changed-on date and validity date are unrelated. SPRPS marks a locked row awaiting approval, exclude it unless the check is specifically about pending changes.

Symptom: an employee reports the wrong salary on a remuneration statement for a given month. Select PA0008 for that PERNR with BEGDA less than or equal to the pay period end date and ENDDA greater than or equal to the pay period start date, order by BEGDA descending. Compare TRFGR/TRFST and the LGAnn/BETnn pairs on the row that actually covers that period against what was expected. If two rows overlap or there is a gap between ENDDA of one row and BEGDA of the next, the payroll driver will have picked up the wrong or no record for part of the period.

PA0008 remains a live transparent table in S/4HANA on-premise for employees managed through classic or concurrent employment personnel administration; it has not been dropped. Reporting and CDS-based extraction increasingly go through compatibility views and HCM-specific CDS layers rather than direct table access, but the underlying storage and infotype logic are unchanged. Where an organization has migrated payroll and core HR to SuccessFactors Employee Central, basic pay is maintained in the cloud system and only replicated into PA0008 for on-premise payroll processing, so the table becomes a downstream replica rather than the system of entry.

Payroll configuration consultants own the wage type structure and valuation logic feeding this table; PA/OM consultants own the infotype maintenance and authorization side. When SuccessFactors Employee Central is in scope, a data discrepancy is first a replication/integration question for the EC-to-payroll integration team, not a table-level fix.

PA0000 (Actions) and PA0001 (Organizational Assignment) are maintained alongside PA0008 during hiring and organizational change actions and share the same PERNR and date-slicing pattern. T512W supplies wage type valuation used to interpret the LGAnn/BETnn pairs. PA0007 (Planned Working Time) is checked against BSGRD for consistency. Infotype 0008 is typically written through the standard personnel actions transactions or maintained directly via infotype maintenance transactions rather than edited in the table itself.