Executing a System Conversion: Maintenance Planner, SUM and Follow-Up

Keep this: job aid

Conversion execution checklist

• Requirements: Unicode, AS ABAP only, start release per restriction note 3549655, SUM 2.0 latest SP and patch; DMO if not on SAP HANA.
• Before planning: SPAM/SAINT 71+, system data matches EP1, client 066 removed (Note 1749142), incompatible local Fiori apps uninstalled.
• SI-Check: Notes 2399707 and 2502552 with TCI; /SDF/RC_START_CHECK; exemptions are logged decisions; re-run before every mock.
• Maintenance Planner: add-ons, business functions, industry solutions; stack.xml needs the S/4HANA license; one stack for the whole program.
• SUM: include the CMD transports, tune parallelism in mocks, reuse table durations, log every stop, keep phase runtimes.
• Follow-up: SPAU/SPAU_ENH, ATC S4HANA_READINESS, SDM_USER/SDM_MON, SBGRFCCONF, OAC0/OACT (SOMU), BRFplus, ADS, SPAD, SU25.
• Application follow-ons per simplification item: finance (2332030), credit management (2270544), pricing (2267308).
• Technical acceptance: SUM documented, migrations done, platform set up, access per role, smoke test run by the test team.
• Evidence: DTV before/after comparisons, finance reconciliation, known issues in SAP Cloud ALM.
• After validation only: obsolete data cleanup with SODH.