SAP HR Personnel Administration

You are an SAP HR specialist managing personnel master data. The user wants to create, read, and modify employee infotypes using transaction PA30 (Create) and PA20 (Display) in SAP HCM.

What to check first

• Verify your SAP user has authorization object P_PERNR (Personnel number) and P_ORGIN (Organizational assignment)
• Check that the personnel number exists in table PA0001 with SELECT * FROM PA0001 WHERE PERNR = <personnel_number>
• Confirm your client allows HR master data changes (check customizing in SPRO → Personnel Management → Maintain HR Master Data)

Steps

1. Launch transaction PA30 by entering it in the command field; you'll see the "Create Personnel Data" screen
2. Enter the personnel number (PERNR) in the field and specify the effective date (default is today); click Enter
3. SAP displays the infotype selection screen—choose the infotype you need (e.g., 0001 for Organizational Assignment, 0002 for Personal Data, 0006 for Address)
4. Complete all required fields marked with * in the infotype dialog; leave optional fields blank if not needed
5. Set the validity period using "From Date" and "To Date" (leave "To Date" blank for ongoing validity or use 31.12.9999)
6. Click Save (Ctrl+S) to write the record to the corresponding infotype table (e.g., PA0001, PA0002, PA0006)
7. For reviewing existing data, use PA20 (Display Personnel Data) with the same personnel number and infotype selection
8. Use PA40 (Change Personnel Data) to modify existing infotype records by entering the personnel number and selecting the infotype to edit

Code

*& Report: Bulk Load Employee Master Data
REPORT zhr_personnel_load.

TABLES: pa0001, pa0002, pa0006.

DATA: lt_pa0001 TYPE TABLE OF pa0001,
      lt_pa0002 TYPE TABLE OF pa0002,
      lt_pa0006 TYPE TABLE OF pa0006,
      ls_pa0001 LIKE pa0001,
      ls_pa0002 LIKE pa0002,
      ls_pa0006 LIKE pa0006,
      lv_pernr TYPE pernr_d VALUE '00000001',
      lv_begda TYPE begda VALUE '20240101',
      lv_endda TYPE endda VALUE '99991231'.

START-OF-SELECTION.

  "Create Organizational Assignment (Infotype 0001)
  CLEAR ls_pa0001.
  ls_pa0001-pernr = lv_pernr.
  ls_pa0001-begda = lv_begda.
  ls_pa0001-endda = lv_endda.
  ls_pa0001-werks = '1000'.      "Plant

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change