Utilizing the Clean Core Strategy and Extensibility Tools

Objectives

After completing this lesson, you will be able to:

  • Explain the clean core concept
  • Define the different types of extensibility and the relevant tools

Clean Core Strategy

The SAP Clean Core Strategy

The core of ERP software consists of six fundamental dimensions: software stack, extensibility, integrations, processes, data, and operations. With a clean core, the performance of each ERP dimension improves.

Watch a video

Watch this video to learn about the clean core strategy from Paul Saunders, SAP Chief Evangelist for Cloud ERP.

Note

Learn more about the SAP Clean Core strategy.

Extensibility Types and Tools

Extensibility Tools

When extensions (customizations) to applications or processes are required, use the SAP Extensibility Explorer to identify which type of extensibility best addresses the requirement, and find learning resources on how to implement the extension.

Build extension within SAP S/4HANA Cloud (in-app)

There are a few types of in-app extensibility possible within SAP S/4HANA Cloud (public or private) directly:

  • Key User Extensibility uses the SAP Fiori apps on the launchpad designed to facilitate a user adding custom fields, logic, and other lifecycle-stable extensions to SAP S/4HANA Cloud without developer knowledge. These extensions are built in the customizing tenant of the development system and moved to other systems through transports. Most of the SAP Fiori extensibility apps are available for all deployments of SAP S/4HANA, however there are a few differences.
    Note
    To check if an SAP Fiori app is available for a certain deployment of SAP S/4HANA, look up the app in the SAP Fiori Apps Reference Library. If the app is available for more than one deployment, there will be a drop-down menu that lets you toggle between SAP S/4HANA Cloud (referring to just public cloud) and SAP S/4HANA (this includes both private cloud and on premise). For example, the Custom Fields app is available for all deployments.
  • Developer Extensibility uses the development tenant of the development system to make changes to released SAP objects with upgrade-stable ABAP code. This type of extensibility is only possible for SAP S/4HANA Cloud Public Edition (3-system landscape), because the development environment is controlled to only allow changes to specific SAP objects. Even though developer extensibility is possible, we recommend exhausting all key user extensibility options first, then moving to side-by-side extensibility for more complex extensions using the SAP Build licenses included in the GROW with SAP enablement package.
  • Classic Extensibility uses the development tenant of the development system to make changes to any SAP object with ABAP code. This type of extensibility is only possible for SAP S/4HANA Cloud Private Edition (and on premise), and is generally not recommended. The major concern is that customizations can become unstable since there are no restrictions on the ABAP code you can use, or the objects you can change. Just as with developer extensibility, we always recommend first exhausting all key user extensibility options, then moving to side-by-side extensibility for more complex extensions using the SAP Build licenses included in the RISE with SAP enablement package.

Build extension in SAP Business Technology Platform

The other type of extensibility separates the extension into a different platform. This ensures the extension is always stable and will not be affected by release upgrades in the SAP S/4HANA Cloud system.

Side-by-Side Extensibility uses the SAP Business Technology Platform to host custom extensions and integrate them to the SAP S/4HANA Cloud system. SAP Build enables business users with no development knowledge to create apps and automate processes in a low/no-code environment, while developers can use tools like the SAP Business Application Studio to build extensions and applications with classical coding languages (Java, JavaScript, Python, etc.).

Use existing application built by SAP Partner developers

When considering developing an entirely custom extension, check to see if an existing solution or application developed by our partner ecosystem meets your needs from the SAP Certified Solutions Directory, or the SAP Store. Industry cloud solutions can be found in the SAP Store too.

Note

To support a Clean Core Strategy, establish a Solution Standardization Board (SSB) to act as a body overseeing compliance with the strategy. The SSB is set up in the customer IT organization and reports to the steering committee during implementation. The SSB reviews proposed developments that deviate from the cloud mindset and clean core strategy and documents the logic behind why the development what approved. As new functionality becomes available through release upgrades in the software, the customer may be able to eventually remove the development and move to the standard functionality. The documentation helps customers remember why a certain development was done and makes it easier to remove it when a suitable alternative becomes available. Learn more about establishing an SSB for Public Edition or SSB for Private Edition.

Log in to track your progress & complete quizzes