SAP HCM/HR: Personnel Administration & Organizational Management

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

SAP HR stores employee data in a way that surprises people used to ordinary applications: nothing is overwritten.

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

An infotype is one aspect of an employee, with dates. Each record has a start and end date, so a change does not replace the old value — it ends it and starts a new one.

    infotype 0008 (Basic Pay), employee 4711
    01.01.2024 - 31.03.2026   salary 60,000
    01.04.2026 - 31.12.9999   salary 66,000

The old row stays. 31.12.9999 is SAP's way of saying "until further notice", and it appears everywhere in HR data.

31.12.9999

Why the design is like this. Payroll must be able to answer "what was this person paid in February", not just "what are they paid now". Without history there is no audit trail and no retroactive processing.

Retroactive processing is the concrete consequence: approve a pay rise in June backdated to April, and payroll recalculates April and May and pays the difference. That is only possible because the system knows what was true then.

The infotypes to know by number.

    0001  Organizational Assignment    position, cost centre, org unit
    0002  Personal Data                name, date of birth
    0006  Addresses
    0008  Basic Pay
    0007  Planned Working Time

Organizational Management models the company, not the people. It is a separate structure made of objects and the relationships between them:

    org unit    a department
    position    one seat in a department -- "Financial Analyst, Mumbai"
    job         a generic template a position is based on
    person      the employee

Objects live in HRP1000, relationships in HRP1001, with relationships like "belongs to", "reports to" and "is held by".

HRP1000HRP1001

The distinction between job and position matters. A job is "Financial Analyst" — one description, one grade. A position is a specific seat: Financial Analyst in Mumbai, reporting to that manager. Forty positions can share one job.

So changing the job description changes forty positions at once, and each position keeps its own reporting line.

Where the two halves join. Infotype 0001 assigns the employee to a position. That single link is what lets the system answer both questions:

    who is this person's manager?     person -> position -> reports-to -> position -> holder
    who holds this position now?      position -> is-held-by -> person

The structure exists whether or not anyone is in the seat — which is how a vacancy is represented, and how recruiting can advertise a position before anybody holds it.

Worth adding in a modern interview. SuccessFactors Employee Central is a completely different technology and keeps the same two ideas: effective-dated records and position management. Someone who understands infotypes and OM understands its data model.

What the interviewer is probing.1. "What is an infotype?" Probing: the data model. Stalls: "A table." Moves up: a logical grouping of employee data with validity dates, so history is kept rather than overwritten.

2. "Why is time-dependency central in HR?" Probing: the model. Stalls: "Nothing." *Moves up:* almost every record has a validity period, so a retroactive change must re-trigger payroll for the affected periods.

3. "How does Organizational Management relate to PA?" Probing: the structure. Stalls: "The same thing." Moves up: OM holds positions, jobs and reporting relationships; PA holds the person — the link is the position assignment.

4. "What is the authorization concern specific to HR?" Probing: the sensitivity. Stalls: "The usual." Moves up: structural authorizations restricting by org unit, on top of infotype-level checks, because salary data needs much narrower access.