Which type of legacy code does SAP recommend you eliminate when reviewing modifications as part of an SAP S/4HANA system conversion?

The recommendation to eliminate code that can be redesigned as a key user extension is based on SAP's shift towards utilizing the capabilities of key user extensibility for ensuring that customizations remain manageable and in line with the latest upgrades. Key user extensions allow for changes and adaptations to be made in a way that is more aligned with standard SAP functionality and can be easily maintained during system upgrades. By eliminating legacy code that could instead be managed as a key user extension, organizations can streamline their systems and make future migrations to newer versions of SAP S/4HANA less complex and costly.

In addition, this approach promotes the best practices of system simplification and innovation, ensuring that the solution remains agile and responsive to business needs. It also helps in reducing technical debt and dependencies that could inhibit the use of new system features or functionalities that come with updates and enhancements in the SAP ecosystem.

Legacy code, particularly when it is possible to achieve the same objectives through safer, more flexible customization approaches, should be phased out to take full advantage of the new functionalities provided by SAP S/4HANA.