56
SAP S/4HANA | Extensibility for Customers and Partners | June 2015
7 / 31
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
b. Key user extensibility: Customers usually
apply many small changes and extensions,
since they want to increase user produc-
tivity or implement adaptations of the
application logic without changing the
major parameters of the respective business
processes. In other words, these extensions
add value to SAP applications and continue
to rely on the full context of the standard
implementations with respect to data,
process, and UI levels. Frequent examples
are “add custom fields and tables” or
“change/add business logic (rules, code
snippets, and so on).” With SAP S/4HANA,
you can implement in-app extensions sat-
isfying all extensibility qualities. In particular,
end-to-end tools enable business experts
to apply changes without risk, as the tech-
nical complexity is reduced to a level that
corresponds to the business purpose
and is stable and fault tolerant – similar
to standard office applications. Thanks
to a strict tool-based approach, these
extensions are loosely coupled with core
business processes and contribute to a
pace-layered IT. This scenario is applicable
for the on-premise and cloud deployment
options.
c. Managed extensibility: In addition to
using the key user and side-by-side exten-
sibility capabilities available in all cloud
edition deployment models, customers
and partners may have a strong need for
coded extensibility for SAP S/4HANA,
cloud enterprise edition, from within the
context of the application. These types of
managed extensions have a focus on tight
integration with the ABAP-based SAP
S/4HANA standard applications and thus
are written in ABAP. To fulfill this require-
ment, SAP will offer customers and part-
ners an additional service to use an SAP-
hosted development landscape to develop
ABAP add-ons that allow a very high level
of in-app extensibility, but with a restricted
scope so that the operation of the add-ons
do not break the cloud operations concept.
For example, modifications of SAP objects
are forbidden, and access to SAP objects
will be allowed only through released
“whitelisted” application program interfaces
(APIs) so that the custom and partner
code will be lifecycle stable.