SAP HCM/HR: Personnel Administration & Organizational Management

Employee master data structure (infotypes), organizational management, and the integration between PA and OM in SAP HCM.

HR/HCM interviews - whether for the classic on-premise SAP HCM or as a bridge topic before discussing SuccessFactors - almost always start with infotypes and organizational management, because these two pieces are the data foundation every other HR process (payroll, time management, recruiting) builds on, and a candidate who can't explain how they relate hasn't really worked in HCM.

Infotypes are like a patient's medical chart where every entry is dated and nothing is ever erased, only superseded by a newer dated entry, preserving the full history; Organizational Management is the hospital's org chart of departments and job titles that exists independently of which specific doctor currently holds which position, until you plug a real person into a specific seat.

Key Concepts

Personnel Administration (PA) stores employee master data in infotypes - structured data records with defined validity periods, each covering one aspect of an employee (Infotype 0001 Organizational Assignment, Infotype 0002 Personal Data, Infotype 0008 Basic Pay, Infotype 0006 Addresses, and so on). Because infotypes are time-sliced (each record has a start and end date), the same employee can have a full history of address changes, salary changes, or org assignment changes, each represented as a separate delimited record rather than an overwritten field - a design choice that surprises people used to simple CRUD systems and is worth explicitly calling out in an interview.

Organizational Management (OM) models the company's structure independently of individual employees, using objects like organizational units (departments), positions (a specific seat within an org unit), jobs (a generic role template a position is based on, e.g., "Financial Analyst"), and persons, connected through relationships (like "belongs to," "reports to," "is held by") stored in tables like HRP1000 (object) and HRP1001 (relationships). A position is filled by a specific person via Infotype 0001, which is the critical PA-OM integration point - it's what lets the system answer both "who is this person's manager" (via the position's reporting-line relationship) and "who currently holds this specific position" from a single connected model.

HRP1000HRP1001

A well-rounded answer mentions the difference between an org unit/position-based reporting structure and the actual employee's data, explains why history-preserving delimited infotype records matter for audits and retroactive processing (e.g., a retroactive salary change triggers payroll to recalculate the affected past periods), and, in modern contexts, notes how SuccessFactors Employee Central conceptually mirrors this same data model (position management, effective-dated records) even though the underlying technology is entirely different.