Sap Hcm

1. Environment Detection (Critical — Ask First)

□ Scenario A — ECC HCM (classic on-premise, pre-S/4HANA)
□ Scenario B — HCM Compatibility Pack on S/4HANA (2020 / 2021)
□ Scenario C — HCM for S/4HANA / H4S4 (S/4HANA 2022+, BF H4S4_1 active)
□ Payroll country? (country-specific PC00_M[XX] where XX = country code)
□ SuccessFactors integrated? (hybrid or standalone HCM?)

⚠️ Strategic Context — Always Share with User

• ECC HCM mainstream support ends 2027 (extended maintenance to 2030 with additional fee)
• HCM Compatibility Pack usage rights expired end of 2025
• H4S4_1 business function activation is IRREVERSIBLE — warn before recommending activation
• H4S4 is a bridge — no major new functionality planned by SAP; SuccessFactors is strategic direction
• For SuccessFactors-specific topics, refer to the sap-sfsf skill

2. Personnel Administration (PA)

Core concept: infotype-based data model — all employee data stored in versioned, date-effective records

Key T-codes:

• PA20: display HR master data
• PA30: maintain HR master data (create / change / delete infotypes)
• PA40: personnel actions (hire / transfer / terminate)

Key Infotypes

Common Errors

3. Organizational Management (OM)

Object Types

Key T-codes:

• PP01: general object maintenance
• PPOCE: org structure editor (hierarchical view)
• PPOME: org management for managers (MSS)

Relationships

Common Issues

4. Payroll (PY)

Payroll Flow

1. Release payroll    PA03 → status: "Released for payroll"
2. Run payroll        PC00_M[XX]_CALC (XX = country code)
3. Check log          Display log → identify error employees
4. Corrections        PA03 → "Release for correction" → fix master data → re-run
5. Exit payroll       PA03 → "Exited"
6. Post to FI/CO      PC00_M[XX]_CIPE → SIMULATE first → then actual run
7. Bank transfer      PC00_M[XX]_CDTA → generate DME file

Country-Specific Payroll T-codes (PC00_M[XX]_CALC)

Key Concepts

• Wage types: dialog (Mxxx — customer-defined) / technical (/1xx — system-generated)
  • V_T512W: wage type configuration table
  • V_T512W_B: wage type permissibility per infotype
• Schemas: country-specific payroll logic (X000 DE / U000 US / etc.)
  • PE01: schema editor — edit payroll calculation logic
• PCRs (Personnel Calculation Rules): PE02 — individual calculation rules within schema
• Payroll periods: T549Q → period parameters per payroll area
• Retro accounting: triggered automatically when backdated IT0008/IT0014/IT0015 changes

Payroll Calculation Failure — Evidence-First Diagnostic Path

Do not jump from a generic "payroll error" to a schema change. First identify the failed stage, reproduce it in simulation, and collect the first error in the log.

Minimum intake

• ECC EhP or H4S4 release and deployment; distinguish classic HCM from Employee Central Payroll and an EC-to-ECP replication incident.
• Country payroll, payroll area, regular versus off-cycle, for-period and in-period.
• Exact message class/number, first failing payroll-log node, first failure time, last successful run, and whether all employees or a masked subset are affected.
• Recent transport, schema/PCR/wage-type, master-data, or time-close change.

Never request names, national IDs, bank details, or raw salary values. Mask employee numbers and retain only the smallest diagnostic sample.

Read-only triage sequence

1. PC00_M99 — menu path: Human Resources > Payroll > International > Payroll. Select the applicable country driver and reproduce the same payroll area and periods in Simulation. Never retry a productive run as the first diagnostic step.
2. In the payroll log, capture the first error node and its surrounding schema function, PCR, and wage-type context. A later summary error is not root cause.
3. Payroll Control Record — menu path: Human Resources > Payroll > <Country> > Tools > Control Record. Compare payroll area, current period, and Released/Correction/Exit state with the run selection. Do not change status or clear a lock during evidence collection.
4. PA20 — menu path: Human Resources > Personnel Management > Administration > HR Master Data > Display. At the failing date, compare IT0000/0001/0007/0008 and relevant IT0014/0015 and IT2001/2002 validity with a masked normal peer.
5. If calculation completed and only FI/CO posting failed, split it into a posting incident. Inspect the posting-run log and symbolic-account/account-assignment chain; do not rewrite payroll calculation results or clusters.

Ranked hypotheses and falsification evidence

Each live diagnosis must state at least two observations that would falsify its leading hypothesis. If the evidence does not distinguish the hypotheses, issue a read-only follow-up request instead of proposing a configuration change.

Fix, rollback, and verification contract

• Correct master/time validity only from an approved source document and preserve the prior dates/values for rollback. Re-run one masked employee in simulation before the affected population.
• Change schema/PCR/wage-type customizing only in DEV with a Transport Request and QA regression cohort. Rollback is the prior transported version plus re-simulation of both affected and normal cohorts.
• Change the control record only with the payroll process owner's approval. Record its previous state and period as rollback data. Never improvise a reversal after Exit or FI posting; design the standard reversal/reposting flow separately.
• Verify the same failing sample, the affected population, and a normal control group. Compare employee count, error count, totals, retro results, and the first log node with the last successful run before any productive execution.

Product boundary

• ECC HCM and H4S4 retain the classic control-record, schema/PCR, and infotype axes, but confirm release-specific support and whether the entry point is GUI or Fiori.
• Employee Central Payroll incidents may originate in EC-to-ECP replication. Prove that replication completed before treating the symptom as a classic payroll calculation error.
• In managed or public-cloud environments, use the exposed payroll apps and monitors when classic GUI transactions are unavailable.

Common Errors

5. Time Management (TM)

Configuration Hierarchy

Holiday Calendar (SCAL)
  → Factory Calendar (SCAL)
    → Daily Work Schedule (PT01 view)
      → Period Work Schedule
        → Work Schedule Rule
          → IT0007 (Planned Working Time)

Key T-codes

Common Issues

6. FI/CO Integration (Payroll Posting)

Posting Flow

PC00_Mxx_CIPE (simulation) → Preview FI document
  → PC00_Mxx_CIPE (actual) → HCM cluster posting document
    → PCRV / PUOC_xx → FI document in target company code

Mapping Chain

Wage type → Symbolic account (V_T52EL) → G/L account (SPRO assignment)

Cost Assignment

• IT0027 (Cost Distribution): split payroll costs across cost centers / internal orders / WBS
• Without IT0027: cost posted to cost center from IT0001 (Org Assignment)

7. H4S4 Guidance (S/4HANA 2022+)

Before Recommending H4S4_1 Activation

• Run impact assessment: SAP Note 3091160 — check which functionalities are deprecated
• Activation is IRREVERSIBLE — no rollback possible after activating H4S4_1 via SFW5
• Some PA / TM / PY functionalities deprecated — must have replacement plan

What Changes with H4S4_1

• Fiori apps added: My Paystub, Leave Request, Team Calendar, Manager Self-Service apps
• Learning Solution: NOT available in Private Cloud → must use SuccessFactors Learning
• Some classic PA/TM reports replaced by Fiori equivalents

What Stays the Same

• Core payroll engine — schemas, PCRs, wage types unchanged
• Infotype data model — PA30 still works
• Time management configuration — work schedules, PT60 unchanged
• FI/CO posting logic — PC00_Mxx_CIPE unchanged

8. References

• references/payroll-guide.md — country-specific payroll T-codes, schema structure overview, PCR logic