dreamwork_

SAP S/4HANA MDL Developer

Role Summary
Experienced SAP S/4HANA MDL Developer responsible for designing, developing, and executing data migration solutions using Migration Cockpit, LTMOM, and LSMW to support S/4HANA transformation programs.

Key Responsibilities

  • Develop and execute master and transactional data migration loads into SAP S/4HANA.
  • Configure and manage SAP Migration Cockpit (File, Staging, and Direct Transfer approaches).
  • Extend and customize migration objects using LTMOM.
  • Develop and maintain LSMW objects for legacy data migration.
  • Perform data mapping, transformation, validation, reconciliation, and defect resolution.
  • Support mock loads, UAT, cutover, and hypercare activities.
  • Collaborate with functional teams and business stakeholders to ensure data quality and successful migration.

Required Skills

  • 5+ years of SAP Data Migration experience.
  • Hands-on expertise in SAP S/4HANA Migration Cockpit, LTMOM, and LSMW.
  • Strong understanding of SAP master data objects: G/L master data, Cost Centres, Profit Centres, WBS / Project-related master data, Bank-related master data, Exchange rates, Fixed Assets
  • Experience with transactional data migration and reconciliation.
  • Experience in at least 2 SAP S/4HANA implementation/migration projects.

Preferred

  • Experience with SAP Data Services (BODS).
  • Exposure to SuccessFactors and Ariba.
  • Experience supporting migration cutover and dress rehearsals.

The candidate does not necessarily need to be an FI solution architect, but they should understand the difference between a technically successful load and a financially correct migration.

Reconciliation & Controls good to have experience with:

  • Source-to-target reconciliation
  • Record-count reconciliation
  • Financial/control-total reconciliation
  • Pre-load and post-load validation
  • Duplicate/missing-record analysis
  • Migration error analysis
  • Data-quality checks
  • Migration evidence and sign-off support

This is especially important for Compass because migration is being managed as a controlled ETL process rather than simply an SAP upload exercise.