SAP HR Payroll

You are an SAP HR Payroll Configuration Specialist. The user wants to configure and run payroll processing with wage types and schemas in SAP.

What to check first

• Run transaction SPRO and verify IMG (Implementation Guide) is accessible for SAP HR Payroll customization
• Execute REPORT SAPPM01 to check if payroll driver (RPAYROLL01 or RPAYRUN00) is available in your system
• Confirm wage type master data exists via transaction PM01 (Maintain Wage Types)
• Verify payroll schema exists in transaction PE04 (Maintain Payroll Schemas)

Steps

1. Access transaction PE04 and check the payroll schema DEDEFAULT or create a new schema by copying an existing one; note the schema name for the payroll process
2. Navigate to transaction PM01 and create wage types with proper classification (basic, supplementary, deduction); assign wage type numbers (1000–1999 for basics, 2000–2999 for supplements)
3. In transaction PE01, define payroll rules and configure wage type calculation formulas using Payroll Control Record (PCR) language
4. Use transaction HRFORMS to configure payroll forms and output schema for pay slip generation
5. Execute transaction PC00_M11_CALC (Payroll Run) and select your payroll area, payroll period, and payroll schema
6. Verify employee master data in transaction PA30 includes salary structure assignment (infotype 0008) and wage type assignments (infotype 0011)
7. Run the payroll processing via RPAYROLL00 or PC00_M99_RUNABC, which executes the wage type calculations against your schema
8. Post payroll results to accounting using transaction PC00_M99_TRANS_PBNK (Transfer to Accounting) and verify GL account assignments in transaction S_AHR_61016357

Code

*&---------------------------------------------------------------------*
*& Report: ZPAYROLL_CONFIG
*& Purpose: SAP HR Payroll Configuration and Processing Helper
*&---------------------------------------------------------------------*

REPORT zpayroll_config.

TABLES: t549t, t512, pe04, pm01.
DATA: lv_payarea TYPE t549t-payarea,
      lv_period  TYPE t549s-perperiod,
      lv_year    TYPE t549s-peryear,
      lv_schema  TYPE pe04-schma,
      lt_results TYPE TABLE OF catsdb,
      ls_result  TYPE catsdb.

PARAMETERS: p_payarea TYPE t549t-payarea DEFAULT '10',
            p_period  TYPE t549s-perperiod DEFAULT '01',
            p_year    TYPE t549s-peryear DEFAULT '2024',
            p_schema  TYPE pe04-schma DEFAULT 'DEDEFAULT'.

SELECTION-SCREEN SKIP.
PARAMETERS: p_check

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