PA2002 table — PA2002 Attendances Infotype Table

Each row in PA2002 represents one attendance record for one employee for one continuous period, tied to a specific attendance type (subtype). Attendance types cover things like business trips, external training days, standby, or any presence-related event the client wants tracked separately from the standard work schedule. Unlike PA0007 which defines the planned schedule, PA2002 records actual reported deviations or additions to that schedule. The table is time-constraint driven like other infotypes, so overlapping records for the same subtype are normally blocked unless the attendance type is configured to allow parallel entries. Records here are consumed by time evaluation (which reads them alongside PA2001 absences and the work schedule) and, where the attendance type is wage-type relevant, they generate entries that eventually post to payroll via the time-to-payroll interface.

Always restrict by MANDT and PERNR first; this is a cluster of employee time records and a full scan across a live client is expensive. Narrow by BEGDA/ENDDA range and, where possible, SUBTY/AWART, since attendance type is usually the actual business question (is this a business trip type, is this standby). The table is not date-effective in the delimited-segment sense of PA0001; each row is its own period, so do not assume one active row per employee, there can be several attendance types active concurrently if the type permits overlap. Selectivity on AWART is high once the client has more than a handful of attendance types configured, so lead with it whenever the question is about a specific category of attendance.

Employee disputes a wage type for standby pay on the payslip. Select PA2002 where PERNR equals the employee and BEGDA/ENDDA cover the disputed period, check AWART matches the standby attendance type and STDAZ shows the hours claimed. If the row exists with correct hours but no wage type appeared on the payslip, the gap is downstream in the attendance-type-to-wage-type mapping or in time evaluation, not in PA2002 itself.

PA2002 continues to exist as a physical table on S/4HANA in the same shape it had on ECC, since infotype tables were not restructured by the HANA data model changes. Where a client has moved time and attendance tracking to SAP SuccessFactors Time Tracking or Time Off, PA2002 in the core HCM system may sit empty or replicated from the cloud side via the relevant integration, rather than being the true system of record. Standard time evaluation and payroll reporting still read PA2002 directly when core HCM remains the time management system.

Time management or HR administration owns the correctness of individual PA2002 entries, since they are entered or approved through time recording processes. Payroll owns the question of whether an attendance type correctly generates a wage type. Configuration questions about counting rules and attendance type behavior sit with the time management functional consultant, not with basis or the technical team.

PA0000 and PA0001 provide employment status and org context needed to interpret any PA2002 record. PA0007 holds the planned work schedule that attendances deviate from or add to. PA2001 is the equivalent table for absences and is checked alongside PA2002 in most time evaluation questions. T512W holds wage type valuation used when an attendance type generates payroll input, and TEVEN stores raw time events consumed during time evaluation runs that also touch attendance data.