As Chief Enterprise Architect, you want to select an extension option that follows SAP's clean- core strategy. What are your recommendations to implement the clean-core strategy best?

Question

Options

• ATo follow the clean-core strategy, the so-called "Developer Extensibility" of S/4HANA isn't
• BFollow SAP's Tier 1 to Tier 2 extension model, which enables different extension options: Cloud
• CUse "Key User Extensibility" functions of S/4HANA for simple extensions. "Developer Extensibility
• DUse of public local APIs or public remote APIs for "Developer Extensibility.

• A
  66% (21)
• B
  9% (3)
• C
  19% (6)
• D
  6% (2)

Explanation

The clean-core strategy is a SAP initiative to keep the core of SAP S/4HANA as clean as possible by moving customizations and extensions to the side-by-side layer. This allows SAP to more easily deliver new releases of S/4HANA without having to worry about breaking custom code. There are two main ways to extend SAP S/4HANA: Developer Extensibility: This allows developers to extend the core of SAP S/4HANA by modifying the source code. This is not allowed under the clean-core strategy. Side-by-Side Extensibility: This allows developers to extend SAP S/4HANA by creating new applications that run alongside the core system. These applications can communicate with the core system using public APIs. The following are the benefits of using Side-by-Side Extensibility: Flexibility: Side-by-Side Extensibility allows developers to extend SAP S/4HANA in any way they Scalability: Side-by-Side Extensibility can be scaled to meet the needs of any organization. Maintainability: Side-by-Side Extensibility is easier to maintain than Developer Extensibility, because custom code is not embedded in the core system. Therefore, the best way to implement the clean-core strategy is to use Side-by-Side Extensibility. This will allow you to extend SAP S/4HANA in a flexible, scalable, and maintainable way.

No community discussion yet for this question.