Tuesday, 12 October 2021 12:42

BTP – Make the core clean: session follow-up

Written by Alexander Korneev
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/10/13/btp-make-the-core-clean-session-follow-up/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

Introduction

In this blog post I would like to summarize the ideas, presented by Lukas Bretschneider at one of the sessions in terms of BTP – Rise program. The session was dedicated to clean core approach, and to this approach in context of BTP and SAP S/4HANA in particular.

This approach means, that the coding we create does not harm any upgrade in particular and we make code, which runs well with SAP S/4HANA Cloud in general.

Main principles

There are 4 main pillars of this approach:

  1. Avoidance: stay as close as possible to standard – without losing the flexibility to adapt the business processes to your needs at a fast rate.
  2. Decouple extensions for Upgrade-stability:
    • Custom extensions do not break an upgrade and upgrades do not break extension
    • Usage of released interfaces & technologies to standard objects
  3. Open to “location”: leverage the full of extension options (In-app-, side-by-side or hybrid) which fits best to your needs
  4. Be aware:
    • of your technical debts and evaluate them on a regular basis
    • of your custom code footprint and manage/monitor on a regular basis

Benefits

So, what benefits brings us the clean core approach?

  1. Reduce TCO by making upgrades eventually non-events from a custom code point of view:
    • Reduce test efforts for business users
    • Reduce adaption efforts for developers
    • IT service providers being able to offer upgrade projects at a fixed price
  2. Speed and Innovation:
    • Be able to absorb innovation delivered by SAP at a faster rate
    • React fast on changing business requirements
  3. Be cloud ready
    • If you run your SAP S/4HANA system on premise – already lay the foundation today to move to the cloud from a custom extension perspective

How to keep the core clean

Let´s discuss this question based on the example of SAP S/4HANA Cloud.

The following ways of extensibility are available for SAP S/4HANA Cloud:

  1. Key user extensibility:
    • Field extensibility
    • UI adaption
    • Custom business logic
    • Custom business objects
    • Custom CDS views
    • Custom analytical queries
  2. Side-by-side extensibility (this type of extensions are developed on BTP side and connected with SAP S/4HANA cloud via Events and APIs):
    • Custom code
    • Partner extension

So what are the general rules:

  1. Utilize Key User Extensibility to create custom fields and custom logic (“cloud BAdI”)
  2. Create de-coupled extensions in Side-by-Side approach
  3. Access standard objects via released APIs/Objects (e.g. I_Product instead of MARA)
  4. Consider abstraction layer in case of missing APIs/released objects to minimize technical debts

Typical Extension in SAP ECC/ S/4HANA on-premise vs Clean Core extension with SAP S/4HANA Cloud

Let´s shortly take a look, how the stated rules work from technical point of view.

Here it is graphical overview of

Continue reading here
Read 28 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.