PA2006 table — Absence Quota Infotype Table (2006)

One row in PA2006 represents a single absence quota entitlement granted to one employee for one quota type, effective for a defined validity or deduction period. Quota types are customer-configured, one per leave or compensation category (vacation, comp time, sick leave entitlement, and so on) and are represented by the subtype field. A quota record can be generated automatically by time evaluation based on accrual rules, or entered manually through infotype maintenance for corrections, carry-forward adjustments or manual grants. Each record carries the entitled quantity for that period; the amount actually remaining is not a stored column but is computed by subtracting deductions posted from absences and compensation payouts within the same deduction period. Multiple quota records can coexist for the same employee and quota type when periods overlap or when a correction record has been added alongside an original one, which is why the sequence number exists as part of the key.

Always restrict on MANDT and PERNR first; the table is not huge per employee but is read constantly by time evaluation across the whole workforce, so an unrestricted scan is expensive. Restrict SUBTY to the specific quota type being investigated rather than pulling every quota type for the employee. BEGDA/ENDDA selection needs to account for overlapping periods deliberately, since a correction record and an original grant can both be valid on the same date; do not assume one row per employee per quota type per year. Never treat ANZHL alone as the current balance; it is the entitlement for that record, not entitlement minus consumption.

Symptom: an employee reports their vacation balance is wrong in the portal. Select PA2006 for that PERNR, SUBTY equal to the vacation quota type, ordered by BEGDA. Check for more than one row with overlapping validity dates and compare AEDTM/UNAME to see if a manual correction was posted after the original time-evaluation-generated record. Then pull PA2001 for the same PERNR and quota-relevant absence types in the same period to see what has actually been deducted; the discrepancy is almost always between what PA2006 grants and what PA2001 has consumed, not a fault in either table alone.

PA2006 exists unchanged in S/4HANA on-premise for customers running classical time management; it is a standard infotype table and has not been replaced by a compatibility view in the way some finance tables have. Where absence and quota management has been moved to a cloud time solution such as SAP SuccessFactors Time Tracking or Time Off, PA2006 in the core system may no longer be the system of record and instead reflects data replicated or integrated from the cloud side, which changes where a consultant should actually go to investigate a quota discrepancy.

Time management configuration and quota generation rules are owned by the HCM time consultant. Absence quota corrections requested by employees or managers are typically a payroll or time administration operational task, escalated to the time consultant when the correction requires touching accrual schema logic rather than a single infotype record.

PA2001 holds the absences that deduct against quotas stored in PA2006. PA0007 carries the time management status controlling whether an employee is processed by time evaluation at all. PA0001 supplies the organizational assignment accrual rules key off. TEVEN holds the time evaluation results, including the cluster entries that show exactly when and how a quota record was generated or adjusted by a time evaluation run.