PA30: Maintain HR Master Data

Wann verwenden

Create and update personnel infotypes

Typischer Anfängerfehler

Editing wrong infotype period

Business context

Goal: consistent personnel records and controlled HR actions.

Typical stakeholders: HR specialist, HR admin, compliance officer.

KPIs to watch: master-data completeness, action processing time, authorization incidents.

Practical example

A business user runs PA30 during the normal HCM process cycle.

Consultant note: Use least privilege, validate master data, and keep reversals documented.

Case walkthrough: issue to resolution

Problem: HR master update entered in wrong infotype period causing downstream payroll issues.

Diagnosis: Verify personnel number, infotype validity dates, and action history before save.

Resolution: Correct date segment via proper change process and validate downstream integration outputs.

Vor Ausführung prüfen

• Benutzerrollen und Berechtigungen
• Organisationswerte (company code, plant, sales area)
• Konsistenz der Stammdaten

Verwandte T-Codes

• PA20
• PA40