Diving Deep into the SAP S/4HANA Cloud Extensibility Model Following Clean Core Principles

Question 1

What is the main issue with classic extensibility in the context of SAP S/4HANA Cloud?

Answer 1

Classic extensibility techniques are inconsistent with cloud-native principles, which creates problems for SAP S/4HANA Cloud because updates are pushed simultaneously to all customers. This can lead to disruptions if classical extensions are in use.

Question 2

Why is extensibility important in SAP S/4HANA Cloud?

Answer 2

Extensibility is important because it allows customers to customize their business processes and partners to create tailor-made solutions, enabling competitive advantages.

Question 3

How does SAP S/4HANA Cloud handle extensibility to maintain a clean core?

Answer 3

SAP S/4HANA Cloud uses an evolved extensibility framework that supports extensions while ensuring smooth, disruption-free software updates. This framework is designed to be consistent with cloud-native principles.

Question 4

What is the clean core approach mentioned in the context of SAP S/4HANA Cloud?

Answer 4

The clean core approach involves using upgrade-stable interfaces and avoiding classic extensibility techniques to ensure that the core system remains stable and can receive updates without issues. This approach is essential for maintaining consistency with cloud-native principles.

Question 5

What are the key principles of the SAP S/4HANA Cloud extensibility model?

Answer 5

The key principles are:

1. Extensions can be implemented either internally (on-stack) or externally (side-by-side on SAP BTP).
2. Extensions must use released local or remote public APIs, BAdIs, and ABAP RESTful Application Programming Model Business Object extension points.
3. Extensions must be implemented using cloud-enabled and released technologies.

Question 6

What are the three types of extensions available in SAP S/4HANA Cloud?

Answer 6

The three types of extensions are:

Key User Extensions (Type 1)
Developer Extensions (Type 2)
Side-By-Side Extensions (Type 3)

Question 7

What are on-stack extensions in SAP S/4HANA Cloud?

Answer 7

On-stack extensions are internal extensions within SAP S/4HANA Cloud and include Key User Extensions (Type 1) and Developer Extensions (Type 2).

Question 8

What are side-by-side extensions in SAP S/4HANA Cloud?

Answer 8

Side-by-side extensions (Type 3) are external extensions that run on SAP Business Technology Platform (BTP).

Question 9

Why does SAP S/4HANA Cloud enforce the use of released APIs and BAdIs for extensions?

Answer 9

SAP S/4HANA Cloud enforces the use of released APIs and BAdIs to ensure stability and compatibility with future updates, maintaining a clean core and allowing seamless software updates without disruption.

Question 10

What is key user extensibility in SAP S/4HANA Cloud?

Answer 10

Key user extensibility allows for the quick realization of extensions using low-code/no-code tools, enabling business experts, key users, and citizen developers to customize SAP applications without needing to understand the underlying technical details.

Question 11

Who are the primary users of key user extensibility tools?

Answer 11

The primary users are citizen developers, business experts, and key users who utilize low-code/no-code tools to create extensions.

Question 12

What are some of the tools available for key user extensibility in SAP S/4HANA Cloud?

Answer 12

Tools for key user extensibility include:

User Interface (UI) Adaptation at Runtime
Custom Fields
Custom Business Logic
Custom Business Object (BO)
Custom CDS View
Custom Analytical Queries
KPIs
Forms

Question 13

What can a key user do with the Custom Fields tool?

Answer 13

A key user can create and edit custom fields for SAP tables, CDS views, or OData services.

Question 14

How does the Custom Business Logic tool benefit key users?

Answer 14

The Custom Business Logic tool allows key users to enhance SAP S/4HANA Cloud functionality by adding additional business logic through a Web-based ABAP editor that includes code completion, syntax checking, and testing capabilities.

Question 15

What is the purpose of the Custom Business Object (BO) tool?

Answer 15

The Custom Business Object (BO) tool enables key users to create entirely new business objects along with their associated database tables, and APIs for creating, reading, updating, and deleting data.

Question 16

How can key users utilize the Custom CDS View tool?

Answer 16

Key users can use the Custom CDS View tool to model access to data in ways that existing CDS views do not support.

Question 17

What functionality does the Custom Analytical Queries tool provide?

Answer 17

The Custom Analytical Queries tool allows key users to create queries for reporting based on SAP or customer-created data sources.

Question 18

What can key users achieve with the KPI toolset?

Answer 18

The KPI toolset enables key users to design new KPIs, which are visualized as tiles in the SAP Fiori launchpad with drill-down capabilities.

Question 19

What is the role of the Custom Forms tool?

Answer 19

The Custom Forms tool allows key users to create form and email templates based on SAP data sources such as CDS views and OData services, supporting form and email-based process implementations.

Question 20

What is developer extensibility in SAP S/4HANA Cloud?

Answer 20

Developer extensibility allows traditional ABAP developers to implement more complex extensions using released extension points, maintaining a clear separation between SAP solutions and custom extensions.

Question 21

What types of extensions can developers implement with developer extensibility?

Answer 21

Developers can implement extensions that require complex SQL access, run in the same logical unit of work (LUW) as SAP applications, or serve as remote APIs for side-by-side applications.

Question 22

Where are developer extensions implemented in SAP S/4HANA Cloud?

Answer 22

Developer extensions are implemented within the SAP S/4HANA Cloud, ABAP environment, using the ABAP Cloud development model.

Question 23

What are the two main possibilities provided for developer extensibility?

Answer 23

The two main possibilities are:

ABAP RESTful application programming model extensibility options
Business Add-Ins (BAdIs)

Question 24

How does SAP ensure stability for developer extensions?

Answer 24

SAP provides released extension points and guarantees stability through upgrade-stable interfaces and systematic extensibility enablement.

Question 25

What can developers do with ABAP RESTful application programming model extensibility?

Answer 25

Developers can create data model extensions, field behavior extensions, node and service definition extensions, and more, enabling the addition of new fields, actions, determinations, and validations.

Question 26

How are Business Add-Ins (BAdIs) used in developer extensibility?

Answer 26

BAdIs allow developers to enhance SAP S/4HANA Cloud functionality in an object-oriented manner, separate from the underlying SAP object, ensuring that updates to SAP objects do not affect the BAdI implementations.

Question 27

What changes are made to the system landscape to support developer extensibility?

Answer 27

The system landscape includes separate tenants for development, testing, and production to support ABAP-based tools and code, allowing for comprehensive testing and transport of extensions.

Question 28

Can you provide an example of a developer extension using the ABAP RESTful application programming model?

Answer 28

An example would be extending an ABAP RESTful application programming model Business Object by adding a new field, action, validation, or node, which involves modifying the data model and behavior layers to incorporate the new extension.

Question 29

What does “extensibility enablement” mean in the context of SAP S/4HANA Cloud?

Answer 29

“Extensibility enablement” refers to SAP determining and allowing which parts of the system can be extended. This involves providing specific extension points and ensuring that extensions are upgrade-stable and maintain a clean core.

Question 30

What is meant by “extensibility provisioning”?

Answer 30

“Extensibility provisioning” refers to the actual process of creating and implementing extensions by the customer. This involves using the enabled extension points to customize or extend the functionality as needed.

Question 31

What are side-by-side extensions in SAP S/4HANA Cloud?

Answer 31

Side-by-side extensions are custom applications built on SAP Business Technology Platform (BTP) that interact with SAP S/4HANA Cloud using remote APIs. These extensions run on SAP BTP instead of SAP S/4HANA Cloud.

Question 32

Who typically develops side-by-side extensions?

Answer 32

Traditional developers, often with experience in SAP BTP and various programming environments like Java, Node.js, or the SAP BTP, ABAP environment.

Question 33

What is the primary consideration for choosing a side-by-side extension approach?

Answer 33

The primary consideration is whether the application needs SAP S/4HANA Cloud data but does not require the SAP S/4HANA Cloud runtime environment. This allows leveraging SAP BTP’s services and integrating with various systems.

Question 34

How do side-by-side extensions access SAP S/4HANA Cloud data?

Answer 34

Side-by-side extensions access SAP S/4HANA Cloud data using remote APIs. These APIs enable data manipulation and interaction with SAP S/4HANA Cloud from the SAP BTP environment.

Question 35

What are some use cases for side-by-side extensions?

Answer 35

Some use cases include:

Custom applications needing access to SAP BTP services like machine learning and AI.

Custom applications integrating multiple systems, both on-premise and cloud-based.

SaaS solutions developed by partners.

Question 36

What benefits do side-by-side extensions offer in terms of system integration?

Answer 36

Side-by-side extensions allow for seamless integration with various systems and services, both on-premise and cloud-based. They enable combining SAP S/4HANA Cloud data with other data sources.

Question 37

What are public released interfaces in SAP S/4HANA Cloud?

Answer 37

They are stable, curated artifacts like local and remote APIs and extension points, ensuring future-proof extensions.

Question 38

What is the difference between local APIs and remote APIs in SAP S/4HANA Cloud?

Answer 38

Local APIs are used within the SAP S/4HANA Cloud environment for on-stack extensions, while remote APIs are used by SAP BTP for side-by-side extensions.

Question 39

How do local APIs support on-stack extensions?

Answer 39

Local APIs allow key users and developers to create extensions within SAP S/4HANA Cloud, facilitating complex SQL operations and core system integration.

Question 40

What are the use cases for remote APIs in side-by-side extensions?

Answer 40

Remote APIs are used for custom apps on SAP BTP, integrating with multiple systems, and utilizing services like machine learning and AI.

Question 41

Why is it important to use only public released interfaces for extensions?

Answer 41

They ensure compatibility with future SAP updates, minimizing disruptions and maintaining system integrity.

Question 42

Can you give examples of artifacts and objects included in public released interfaces?

Answer 42

Examples include released CDS views, OData and SOAP services, BAdIs, and ABAP RESTful Application Programming Model Business Objects.

Question 43

How do public released interfaces contribute to the clean core approach in SAP S/4HANA Cloud?

Answer 43

They prevent custom code from modifying the core system, maintaining integrity and facilitating smooth updates.

Question 44

What factors should be considered when choosing the right extensibility option?

Answer 44

Consider the extension use case, architecture, scope, and size.

Question 45

What does the “extension use case” refer to?

Answer 45

It refers to whether the extension is a new application or an enhancement to an existing SAP app.

Question 46

How does “extension architecture” impact the choice of extensibility option?

Answer 46

It determines whether the extension should be loosely or tightly coupled to SAP S/4HANA Cloud and whether it uses only SAP data or integrates data from multiple products.

Question 47

What does “extension scope and size” encompass?

Answer 47

It involves who provides the extension and for what purpose, such as key users for small extensions, development teams for custom projects, or partners for SaaS applications.

Question 48

Are the three extensibility options mutually exclusive?

Answer 48

No, many extension use cases may require a combination of key user, developer, and side-by-side extensibility approaches.

Question 49

Which of the following are key user extensibility tools?

A
Custom Fields

B
Custom Database Tables

C
Custom Business Objects

D
Custom CDS Views

Answer 49

A
Custom Fields

C
Custom Business Objects

D
Custom CDS Views

Correct. The following are key user extensibility tools: Custom Fields, Custom Business Objects, and Custom CDS Views.

Question 50

BAdIs are classified under which of the following extension types in SAP S/4HANA Cloud?

A
Side-By-Side Extension

B
Classical user exit

C
Key User Extension

D
Developer Extension

Answer 50

D
Developer Extension

Question 51

Which of the following are use cases for side-by-side extensions?

A
A custom solution needing to be developed by a partner

B
Creating custom applications integrating data from SAP S/4HANA Cloud and SAP Ariba

C
Adding additional business logic to an SAP S/4HANA Cloud Business Object

D
Creating custom fields in an SAP S/4HANA Cloud table

Answer 51

A
A custom solution needing to be developed by a partner

B
Creating custom applications integrating data from SAP S/4HANA Cloud and SAP Ariba

Correct. Use cases for side-by-side extensions include a custom solution needing to be developed by a partner and creating custom applications integrating data from SAP S/4HANA Cloud and SAP Ariba.

Question 52

Which of the following are essential rules of the SAP S/4HANA Cloud extensibility model?

A
Customer upgrade projects are to be done once per year

B
Usage of released objects only

C
Clear separation of extensions and SAP code

D
No modifications of SAP objects

Answer 52

B
Usage of released objects only

C
Clear separation of extensions and SAP code

D
No modifications of SAP objects

Correct. The essential rules of the SAP S/4HANA Cloud extensibility model are as follows: No modifications of SAP objects, a clear separation of extensions and SAP code, and usage of released objects only.

Question 53

Which of the following are factors to consider in deciding what extensibility option to use?

A
Extension use case

B
Extension uniqueness

C
Extension architecture

D
Extension scope and size

Answer 53

A
Extension use case

C
Extension architecture

D
Extension scope and size

Correct. The following are factors to consider in deciding what extensibility option to use: Extension use case, extension architecture, and extension scope and size.

Question 54

Which of the following are ABAP RESTful application programming model extensibility options?

A
Field

B
Data Model

C
Behavior

D
Domain

Answer 54

A
Field

B
Data Model

C
Behavior

Correct. Data Model, Field, and Behavior are ABAP RESTful application programming model extensibility options.

Question 55

Which of the following are challenges with trying to use classical extensibility in SAP S/4HANA Cloud?

A
Classical extensibility does not enable customers to have flexible processes

B
Classical extensibility does not enable customers to have competitive advantage

C
In SAP S/4HANA Cloud, all software updates run simultaneously

D
In SAP S/4HANA Cloud, there are no customer-specific customer update projects

Answer 55

C
In SAP S/4HANA Cloud, all software updates run simultaneously

D
In SAP S/4HANA Cloud, there are no customer-specific customer update projects

Correct. In SAP S/4HANA Cloud, there are no customer-specific customer update projects, and in SAP S/4HANA Cloud, all software updates run simultaneously.