Describing Application Development

This lesson introduces the learner to application development and automation in the context of SAP BTP. It begins with a discussion of extensibility in general and some basic terms used. Next we cover the concepts of clean core and the SAP S/4HANA Cloud extensibility model. Finally we look at some of the specific SAP BTP services used for application development and automation.

This lesson contains the following topics:

This unit provides an overview of SAP S/4HANA extensibility options, including on-stack options such as key user, developer, and classic extensions as well as side-by-side options on the SAP Business Technology Platform (SAP BTP.) Each option is explained in detail and how each of them can be applied depending on business requirements and implementation scenarios.

The following is an overview of the SAP S/4HANA Cloud Extensibility Model. The various components are explained briefly here and in subsequent lessons..

Taking the specifics of the SAP S/4HANA Cloud Extensibility Model into account ABAP code can therefore be placed in the following locations:

• SAP S/4HANA Cloud public edition (ABAP Cloud only)
• SAP S/4HANA Cloud private edition (ABAP Cloud recommended; Classic ABAP permitted)
• SAP S/4HANA (on-premise) (ABAP Cloud recommended; Classic ABAP permitted)
• SAP BTP, ABAP environment (ABAP Cloud only)

ABAP Development Tools In Eclipse is used for ABAP Cloud development. For classic ABAP development traditional transaction codes (i.e., transaction /SE80 can be used).

This architecture diagram shows the various possibilities for extension, depending on the currently available ABAP installations.

Key user extensibility along with developer extensibility is available in all SAP S/4HANA deployment models (i.e., public edition, private edition,on-premise).

Traditional ABAP programming (classic ABAP) along with classical extensibility, both of which have been used for many years with various approaches and frameworks, is only available on certain SAP S/4HANA deployments (private edition | on-premise). While ABAP Cloud is the preferred approach irregardless of the deployment option chosen for SAP S/4HANA, in certain (and hopefully rare) situations (i.e., mission critical legacy code not currently able to be refactored in ABAP Cloud) classical ABAP and classical extensibility techniques may still temporarily need to be used. In this case SAP recommends for customers to monitor these situations and as soon as ABAP Cloud becomes feasible for usage to refactor legacy code based on ABAP Cloud and retire the classic ABAP accordingly.

It is important to understand these differences to choose the right implementation and extension technology for your organization's specific needs and goals.

• Custom Extensions in SAP S/4HANA Implementations - A Practical Guide for Senior IT Leadership
• Extend SAP S/4HANA in the cloud and On Premise with ABAP based extensions

SAP BTP has various platforms that can be utilized for software development including both low-code/no-code (LCNC) and pro-code (PC) approaches. LCNC platforms allow users without in-depth programming knowledge to create applications, while PC platforms are used for more complex and extensive IT projects.

Software development has changed dramatically over the last 20 years due to technologies such as cloud, mobile, IoT, and Artificial Intelligence/Machine Learning. In light of this development, the importance of agile methods has increased. In this context, you will learn about the rise of low-code/no-code and pro-code development platforms.

LCNC provides tools and functions that simplify development and make it more efficient. Graphical editors for visualizing data models and application components facilitate the configuration of specific elements and promote reusability. These approaches are central to the Rapid Application Development (RAD) methodology.

In the IT-centered business world, advanced programming skills and flexibility are often required, which falls into the area of pro-code development. At SAP BTP, for example, various programming languages are used in different environments.

The choice between LCNC and PC depends on the complexity of the application. LCNC can save time and money and allows less technical users to create efficient solutions. However, PC development is often required for sophisticated functions and performance optimization. Both approaches can coexist if a governance framework defines when which approach is appropriate.

The following are some examples of the application of LCNC and PC on SAP BTP:

Low-code application development and automation with SAP Build

Clean Core is a philosophy and an approach which aims to maximize the ability for customers to innovate with SAP S/4HANA by utilizing a best practices methodology in regards to areas such as business process design, extensibility and integrations. Regarding clean core extensibility for example some principles are that extensions should be avoided if possible and extensions should be strictly separated from the standard software and only use released APIs.

Clean Core is one of the most frequently mentioned terms in the context of the SAP S/4HANA. Depending on the perspective (i.e., business processes, extensibility, integration), various factors are emphasized.

Custom Extensions in SAP S/4HANA Implementations - A Practical Guide for Senior IT Leadership.