Follow-up

When SUM finishes, the system runs SAP S/4HANA, but it is not ready for users. SAP's guide lists custom code adaptation, cross-application follow-on activities and application-specific follow-on activities, with the full list coming from the Simplification Item Catalog and the checks for your system. In the first conversion these take days; by the production conversion most are transports or scripted steps on the runbook.

Cross-application follow-on activities

Silent data migration deserves a note for testers. By default SUM leaves some data migrations to run after the conversion, in uptime. SUM can force them into downtime instead, at the cost of a longer outage. Either way, SAP warns that every silent migration must finish successfully in every client, or new functions may not work. Add a check of SDM_MON to the technical acceptance.

Application-specific follow-on activities

The application list depends on the simplification items relevant to your system. For Contoso the main ones are the finance data migration (SAP Note 2332030; the finance conversion course covers it), the SAP Credit Management migration (SAP Note 2270544), and the sales items flagged in Readiness Check, such as the pricing data model change (SAP Note 2267308). Each has an SAP Note with its steps. Map each to an owner and a runbook line.

Expect differences that are by design. A simplification item may replace a transaction, change a field length or move a function into a new app. Testers who compare against ECC need to know which differences are intended, or they will log them as defects. Sam's team collects these items from Readiness Check and the SI-Check results into a short list of expected changes, which goes to Priya with the converted system (lesson 5).

Technical housekeeping

• Background jobs: check the job schedule against the new release; obsolete jobs removed, new standard jobs scheduled.
• RFC destinations and interfaces: connections to the bank, the tax engine, EDI and the plant systems tested from the converted system.
• Printers and output: spool devices and forms printed from the new output control.
• Logs: SUM evaluation reviewed; every ignored error explained in writing.
• Old data: after testing and validation, the Obsolete Data Handling Monitor (transaction SODH) deletes data left behind by data model simplifications. Plan it for after go-live sign-off, not during the weekend.

Step by step: Contoso's post-SUM runbook

1. Modifications. SPAU and SPAU_ENH, imported from the transports collected in CMD (SPDD already ran inside SUM).
2. Custom code. ATC run with check variant S4HANA_READINESS in the converted system; fixes in ABAP Development Tools, because SE80 does not support every object type, such as CDS views.
3. Finance. The finance data migration and its reconciliation, owned by Dan's team (SAP Note 2332030).
4. Silent data migrations. Technical users maintained in SDM_USER before the run; status checked in SDM_MON for every client.
5. Output control. bgRFC supervisor destination in SBGRFCCONF; storage system in OAC0 assigned to category SOMU in OACT; BRFplus applications imported from SAP Note 2248229; Adobe Document Services; printers by short name in SPAD.
6. Authorizations and UI. SU25 exchange report for obsolete transactions in role menus (SAP Note 2465353); Fiori catalogs and business roles; launchpad checked per test role.
7. Technical. Job schedule, RFC destinations, interfaces to Process Orchestration (XQ1 in test), printers.