PA2001 table — PA2001 Absences Infotype Table

A row in PA2001 represents one absence record for one employee: a single continuous period, of one absence type, recorded under infotype 2001. Typical absence types stored here are illness, planned vacation, unpaid leave, maternity leave, jury duty, and any other customer-defined absence subtype. Each record carries a start and end date, the number of calendar days and payroll-relevant days the absence spans, and administrative fields such as who last changed it and when. Because infotype 2001 supports multiple records per day in some configurations (partial-day absences, different absence types on the same date), a single calendar day for one employee can appear across more than one row, distinguished by a sequence number. The table feeds time evaluation, payroll absence valuation, quota deduction, and absence reporting used by HR and line managers.

Always restrict by MANDT and PERNR first; the table grows across the entire absence history of every employee, so an unrestricted select on a productive system is expensive and usually unnecessary. Add a date range filter on BEGDA/ENDDA rather than pulling full history when the question is about a specific period. SUBTY narrows to a single absence type when the question is scoped to, for example, sickness only. Do not assume one row equals one calendar day off; a record can span weeks, and partial-day or split records show up as separate rows with the same BEGDA. Check HISTO before trusting a record as current - a historicized row remains in the table for audit purposes.

Symptom: an employee disputes the number of vacation days payroll or a report shows as taken. Select PA2001 for that PERNR with SUBTY restricted to the vacation absence type and a wide BEGDA/ENDDA window covering the disputed year, sum ABWTG across the returned rows, and compare against the quota consumption shown in PA2006 for the same period. A mismatch between the two points to a quota transfer, correction, or an absence posted but not yet processed by time evaluation, rather than a data entry error in PA2001 itself.

In S/4HANA on-premise with classic time management, PA2001 continues to exist and behaves the same way, including the underlying redundant-storage relationship with the time cluster. Where employee master data has moved to the newer HR data model or where SuccessFactors Employee Central owns absence data with replication into ECP or on-premise payroll, PA2001 may be populated by inbound replication rather than direct PA30 entry, and its role shifts from primary entry table to a landing/reporting table for replicated absence data. Consultants should verify which system is the system of record for absences before treating PA2001 content as authoritative.

Time management or HR administration owns absence master data quality; the payroll or time evaluation team owns disputes about how an absence was valuated once posted. When SuccessFactors Employee Central is in scope, the integration or replication team owns discrepancies between EC absence records and the PA2001 copy on the receiving system.

PA0000 and PA0001 give employment status and organizational assignment context needed to interpret an absence correctly. PA0007 supplies the planned working time used to calculate SOLL days against which absences are measured. PA2002 is the structurally identical attendances table, and PA2006 tracks the quota consequences of absences recorded here. TEVEN holds raw time events from clocking systems that can conflict with or corroborate an absence record. Records are maintained through the standard infotype maintenance transactions for personnel administration and time management.