Week 5 of 12
Simplification items and custom code
Some S/4HANA changes affect almost everyone: customers and vendors become Business Partners, finance postings land in the Universal Journal, the material ledger becomes mandatory, credit management moves to SAP Credit Management, output may move to the new framework, and many users move to Fiori.
Customizations were the second-biggest barrier in the ASUG research, at 44%. Each one is code that must be found, fixed and regression tested.
This week: convert the Readiness Check into test scope
- Export the relevant simplification items from your SAP Readiness Check and give each one an owner and at least one test scenario.
- Run custom code analysis (ABAP Test Cockpit with the S/4HANA checks) and use usage data to retire code nobody runs.
- Record each extension’s clean core level (A to D). C and D extensions go into every regression cycle, now and after go-live.
- Add Business Partner conversion, Universal Journal reconciliation and credit block-and-release to your critical scenarios.
Number of the week
44%
of SAP customers named customizations as a top S/4HANA barrier.
Source: ASUG and Precisely (2025)Use this week
- Simplification Item Test Impact Tracker →
22 common simplification items with what changes and how to test each one.
- Guide: phase-by-phase migration test plan →
Where each test activity sits across SAP Activate, and the S/4HANA changes to test.
Next week: most broken SAP tests are broken by data. We set up test data and environments that hold.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.