PA0006 table — Addresses Infotype 0006 Table

PA0006 stores one address record per personnel number, address subtype, and validity period. Subtypes distinguish address purposes such as permanent residence, temporary residence, mailing address, or emergency contact, and the exact list of subtypes is country-dependent because address screens differ by country grouping (MOLGA). A single employee can hold several concurrent rows because several address types are usually allowed to coexist without one delimiting another, and because a single subtype can itself repeat, for example several emergency contacts stored under the same subtype with different sequence numbers. The row does not necessarily hold the full postal detail in every system: where central address management is active, PA0006 can carry a pointer to the address stored centrally rather than the street and city fields themselves.

Always restrict on MANDT, PERNR, and SUBTY before touching date logic; the table is not selective on its own and a scan across a large workforce without those keys is expensive. To find the address valid on a given day, filter BEGDA less than or equal to that date and ENDDA greater than or equal to it, then take the row with the highest SEQNR if more than one survives the filter, since some subtypes deliberately allow parallel entries. Prefer reading through the infotype framework (the standard read function modules or the logical database used by payroll and reporting) rather than a raw SELECT, because that layer respects authorization checks and time constraint rules that a direct query will silently ignore.

Symptom: a payslip or letter was sent to the wrong home address. Select PA0006 where PERNR equals the employee number and SUBTY equals the permanent residence subtype for that country grouping, with BEGDA less than or equal to the issue date and ENDDA greater than or equal to it. Order by SEQNR descending. Check STRAS, ORT01, PSTLZ directly; if all three are blank, the address is not stored on the infotype and must be traced through the central address pointer instead.

PA0006 continues to exist in S/4HANA on-premise HCM as the same infotype table; there is no compatibility view replacement specific to this object. In a SuccessFactors Employee Central landscape, address data is captured and owned in Employee Central personal information entities rather than on PA0006 directly. When Employee Central Payroll or an on-premise payroll system is in scope, address data is replicated from Employee Central into PA0006 through point-to-point replication or an integration center mapping, with Employee Central address types mapped onto local infotype subtypes.

In an Employee Central landscape, the address is owned and corrected in the source system by HR operations or the employee via self-service, not by editing PA0006 directly. Any discrepancy between what an employee sees in Employee Central and what payroll or on-premise HR shows on PA0006 is an integration and replication mapping question, owned jointly by the Employee Central configuration team and the payroll or HCM technical team who maintain the replication.

PA0002 (Personal Data) is read alongside PA0006 to present name and address together. PA0001 (Organizational Assignment) provides the employment context that determines which country grouping's subtype list applies to the address screen. PA0000 (Actions) confirms whether the employee was active on the date the address record claims to be valid. Both PA20 and PA30 write to PA0006 in an on-premise system; in an Employee Central landscape the writes originate from Employee Central and arrive through the replication process rather than direct PA30 maintenance.