SAP SuccessFactors H1/H2 Release: What to Audit Before Each Update
SAP SuccessFactors releases H1 in May and H2 in November every year. Each release ships hundreds of changes across Employee Central, Performance & Goals, LMS, and the IAS/BTP integration layer. Here is the pre-release audit checklist that catches the regressions before they hit production.
1. The release cadence
Two major releases per year (H1, H2) plus monthly enhancement packs. The H1/H2 weekends are the highest-risk events; the monthly packs add up to the same regression surface over a year.
2. The four categories that break most often
- MDF object schema changes — custom MDF objects with inconsistent attributes that fail post-release.
- RBP rule deprecations — permission group filters that no longer evaluate as before.
- CPI integration mappings — connectors using deprecated SuccessFactors API fields.
- IAS trust drift — accumulated SSO config that breaks under new IAS releases.
3. Where to test
Use the Preview tenant. Run end-to-end transactions on every material BP type. Re-execute every CPI integration against a downstream sandbox. Validate IAS trust chain after every IAS-side update.
4. The Joule connection
Joule depends on the same MDF, RBP, and integration layers that releases change. A pre-release scan that misses a Joule-relevant config change becomes a Joule failure two weeks later.
Continue reading
Find out what's broken in your tenant
Free first scan. Read-only access. Results in under 2 hours.
Start Your Free Scan