Technology Fundamentals for SAP - S4HANA and SAP Business Suite

SAP Business One: for small companies with up to 100 employees

SAP Business ByDesign: for small and midsize companies with between 100 and 150 employees

SAP Business Suite for SAP HANA (SAP S/4HANA)

SAP S/4HANA is the abbreviation for SAP Business Suite for SAP HANA

Launched in 2015

Cloud or on-premise

Business Technology Platform (BTP): an open platform-as-a-service (PAAS) that delivers in-memory
capabilities, core platform services, and unique microservices for building and extending intelligent,
mobile-enabled cloud applications.

SAP Ariba

SAP SuccessFactors: a global provider of cloud-based human resource software and fully integrated
human capital management (HCM) systems. It covers everything from core HR, payroll, and people
analytics to the four pillars of talent management: recruiting, learning and development, compensation,
and performance management.

SAP Fieldglass: a cloud-based, open external workforce management and services procurement platform
that helps organizations find, engage, and manage all types of flexible resources – from temporary staff
to Statement of Work-based consultants, to freelance workers and more.

SAP Concur: provides travel and expense management services to businesses

Cloud Terminology: Market Sectors

Infrastructure as a service (IAAS): subscribing hardware resources based on your needs right on
demand. This includes networking, storage, server, and virtualization.

Platform as a service (PAAS): subscribing middleware functionalities on top of your virtual

infrastructure.

Software as a service (SAAS): subscribing applications based on your needs right on demand.

Cloud Terminology: Deployment Models – cloud services differ in different types of deployment.
Depending on who offers the services and to which target group they are targeted.
 Public Clouds: a cloud system assigned to many customers. The resources are shared but
operative data is separated on application level. The public cloud is an offer of a freely accessible
provider, which its services openly accessible to everyone via the internet.

Private Clouds: a cloud system assigned to on customer. The resources of a private cloud are not
shared. Not accessible for others.

Hybrid Clouds: a mixture of combining private and public cloud solutions to one integrated
landscape. It’s also possible to integrate on-premise scenarios into cloud scenarios of your choice.

Community clouds: cloud infrastructures that are used and deployed by multiple organizations,
such as in the context of a project, to share access to specific services. However, these are not publicly
available, but are limited to a defined user group.

SAP HANA

• Database tables are based on:

1. Row storage

2. Column storage

• Applications:

• On-Line Transactional Processing (OLTP) Application: requires fast, record-level updates where
all columns in the record are usually needed for processing.

• On-Line Analytical Processing (OLAP) Application: typically work with high-volumes that need to
be quickly aggregated by ad-hoc queries.

Storage Design:

1. Row storage: the optimal storage design for OLTP application.

2. Column storage: the optimal storage design for OLAP application.

• SAP HANA fully supports OLTP applications using row storage but also supports columns based
storage.

• The database of SAP HANA supports both row tables and column tables in the same database.

o Column tables are efficient for analytical applications where requests for selections of data are
not predictable (Queries from analytical applications that are sent to the database often require only a
subset of the overall data in the table. Usually only a few columns are required from the table and also
only a limited number of entries from the columns are needed. With column tables, only the required
columns are loaded to memory, so you avoid filling up memory with columns that will never be used.
Also, the data is arranged efficiently with all values of a column appearing one after another. This
continuous sequencing of the column values is preferred by the CPU, which is able to scan the values
efficiently without having to skip over unwanted values).
o Although it is possible to build transactional applications on column tables, you might see better
performance if you were to use row-based tables where all the columns in a record are always held
together and can be read in one step.

o More often these days, applications combine transactional and analytical elements. In this case,
you must decide which is the best storage method to use. You cannot have a table that is both row-
based and column-based.

SAP NetWeaver AS for ABAP: Complete infrastructure in which ABAP-based applications can be
developed and used.

SAP NetWeaver AS Java: Complete infrastructure in which JEE-compliant applications can be developed
and used.

Note: If you use an SAP S/4HANA system, you must use the SAP HANA database, and a Linux operating
system is required for the SAP HANA database.

ABAP

• ABAP is a programming language developed by SAP.

• Many business applications of an SAP system are written in ABAP.

• ABAP has been optimized for developing highly scalable business applications.

• Customers can use the ABAP Workbench for developing completely new applications as well as
enhancing and modifying SAP standard applications.

• The Application Server ABAP provides the runtime environment for programs written in ABAP.

• SAP not only provides a runtime environment for ABAP programs but also a runtime
environment for Java programs. AS Java is an application server according to the Java Enterprise Edition
(JEE) standard.

o Java Platform Enterprise Edition (Java EE, previously J2EE) is a vendor standard for a whole range
of software components that are primarily created in the Java programming language.

Client/Server-Based Architecture: Two ways of defining the concepts client and server.
• In the hardware-oriented view, the term server means the central server in a network that
provides data, memory, and resources for the workstations (clients).

• In the software-oriented view, client and server are both defined at the process level (service). A
service in this context is a service provided by a software component. This software component can
consist of a process or a group of processes (such as an Application Server ABAP) and is then called a
server for that service. Software components that use a service are called clients. At the same time,
clients can also be servers for other specific services.

In the context of SAP systems, the terms client and server are generally used as defined in the software-
oriented view.

The following processes are often used for operating business application software:

• Presentation processes (for example, for displaying screens)

• Application processes (for example, for executing application programs)

• Database processes (for example, for managing and organizing database data)

The following list describes the various ways to distribute the required processes among the available
hardware:

• In single-tier configurations, all processing tasks (database, application, and presentation

processes) are performed by one computer. This is classic mainframe processing. Single-tier
configurations are generally used for tests and demonstrations (for example, an SAP system on a
laptop). If many users want to work on a system configured in this way, then the extra hardware costs
for each additional user become greater than the costs associated with implementing additional
hardware levels (for example, moving the presentation processes to other hosts).

• Two-tier configurations are usually implemented using special presentation computers that are
responsible solely for formatting the graphical interface. The two-tier configuration with distributed
presentation processes can maintain good performance for a significantly higher number of users,
without substantially increasing the hardware costs. The load resulting from the presentation processes
is distributed to the various front-end computers and so does not influence the performance of the
database host.

If the number of users exceeds a certain upper limit, the central host, on which both application and
database processes run, risks becoming a bottleneck. To prevent this, you can improve the performance
of the SAP system by distributing the application-layer processes to several hosts. Another advantage of
adding a hardware layer specifically for application processes is that it facilitates scalability. If the
number of SAP users in an SAP system increases over time, negatively affecting SAP system
performance, then this problem can, in most cases, be solved simply by adding another host for
application processes.

An alternative two-tier configuration is to install powerful desktop systems and to use these for
presentation and applications (two-tier client/server). These configurations are especially suited to
applications with high processor demands (for example, simulations or for software developers), but are
not implemented in the SAP environment, other than for test purposes, due to the additional
administration required.

• In a three-tier configuration, each layer runs on its own host. Many different application servers
can simultaneously work with the data of a database server.

In the SAP S/4HANA and SAP Business Suite environment, more complex client/server configurations
consisting of more than three tiers are both theoretically possible and used in practice. An additional
level could be a Web server, for example.

SAP NetWeaver

• The foundation for running business applications like SAP S/4HANA and SAP Business Suite.

• Layers and uses of SAP NetWeaver:

o SAP Enterprise Portal

o Web Dynpro (WD): a technology for creating web-based applications for SAP systems. There are
Java and ABAP versions of Web Dynpro. Web Dynpro for ABAP is particularly important for new
developments.

o The SAP UI Development Toolkit for HTML5 (SAPUI5): a user interface technology that enables
you to set up and modify client applications.

o SAP Process Orchestration

o SAP Business Warehouse

o AS ABAP

o AS Java: support for Java Platform, Enterprise Edition for the development of Java-based
enterprise applications.

o SAP Application Lifecycle Management

o SAP Gateway:

 SAP Gateway located between SAP systems and the outside world, thus making data from the
SAP systems available externally. SAP Gateway uses the Open Data (OData) protocol for
communications between applications and the SAP system. OData is developed by Microsoft and is an
extension of the Atom Publishing and Atom Syndication Standards, which in turn are based on XML
(Extensible Markup Language) and HTTP(S) (Hypertext Transfer Protocol (Secure)). With this extension,
OData provides database like access to server-side resources.

o SAP Fiori:

 SAP Fiori runs on a wide variety of devices, to get work done quickly and efficiently. As a key
component of the SAP user experience (UX) strategy, the new version of SAP Fiori has been enhanced to
offer additional business areas and a wider spectrum of roles, to capture the full benefits of a simple,
modern user experience.

o SAP HANA or AnyDB

 SAP NetWeaver Application Server supports a number of different databases and operating
systems, particularly the SAP HANA database for fast, real-time access to large datasets.

SAP Fiori

• SAP Fiori Launchpad (FLP): serves as the central entry point for all of the apps of a user.

• The three dimensions in which SAP Fiori is defined:

o Design

o Concept

The five design principles of SAP Fiori:

 Role Based

 Adaptive: adapts to multiple use cases and devices

 Coherent: provides one fluid, intuitive experience

 Simple: includes only what is necessary

 Delightful: makes and emotional connection

o Technology

• SAP Fiori Apps

o All SAP Fiori apps utilizes the technologies SAPUI5 and SAP Gateway. The three types of SAP Fiori
apps are different in terms of their usage of additional technologies

1. Transactional Apps

 Usage of ABAP to provide the classic approach for functions of a business system

 Available for SAP S/4HANA and SAP Business Suite on any database

2. Analytical Apps

 Usage of analytical capabilities of SAP HANA to provide insights in business data

 Available for SAP S/4HANA and SAP Business Suite powered by SAP HANA

3. Fact Sheet Apps

 Usage of Enterprise Search capabilities of SAP HANA to provide search results

 Available for SAP S/4HANA and SAP Business Suite powered by SAP HANA
Catalog

Tiles

Groups

Spaces

Pages

Sections

SAP GUI

• The presentation level, the SAP GUI, enables you to interact with SAP systems that are based on
AS ABAP.

• The SAP GUI is based on the Windows Style Guide and available for several platforms

• The following types of SAP GUI are available:

1. SAP GUI for the Windows environments

2. SAP GUI for the Java environment

3. SAP GUI for HTML

SAP instance or SAP application server

• An administrative unit that combines SAP system components providing one or more services.

• The services provided by an application server are started or stopped together.

• You use a common instance profile to set parameters of all the components of an application
server.

• An application server runs on a host.

• Multiple application servers can run on a single host.

• AN application server is identified by its (three-character) SAP system ID (SID) and a (two-digit)
instance number.

• The database for an SAP system:

o Can be installed and operated on a separate host, separated from the application servers of the
SAP system.

o There is (usually) exactly one database for each SAP system.

o The database usually has the name SAP system ID (DB SID) as the SAP system (SAP SID).
• The following factors have an influence on the application server design of an SAP system:

o Release of the SAP system (due to architecture changes throughout the releases)

o Type of SAP system (AS ABAP-based or AS Java-based)

o Decision of the SAP customer (scalability, high availability)

• The installations options are:

o AS ABAP-based SAP system

o AS Java-based SAP system

o AS ABAB+AS Java-based SAP system (dual stack): dual stack are not supported since SAP
NetWeaver 7.5

Runtime environment:

• The runtime environment for ABAP (AS ABAP)

• The runtime environment for Java (AS Java)

AS ABAP architecture and processes:

• ABAP dispatcher: manage different types of work processes

• Work processes: take on different tasks when executing workflows in the SAP system

o Dialog work processes

o Background work processes

o Update work processes

o Spool work processes

Additional services provided by AS ABAP runtime system for internal and external communication:

• The ABAP Message Server (MS)

• The Enqueue Server (ES)

• The Remote Function Call (RFC) gateway reader (GW)

• The Internet Communication Manager (ICM)

The roles involved in developing and transporting:

• Development project team leader: manages transport requests

• Developer

• Tester

• Transport administrator

ABAP Workbench Tools:

• ABAP Editor (SE38)

• Object Navigator (SE80)

• ABA Dictionary (SE11)

• Screen Painter (SE51)

• Function Builder (SE37)

Tasks of the ABAP Dictionary can be subdivided into:

• Database object definitions

• Types definitions

• Services definitions

In line with the six phases of application management defined under ITIL, the lifecycle also has six
phases:

• The most important task in the requirements phase is to evaluate scenarios and the
corresponding business processes and to check whether they can be realized in the project.

• In the design phase, an implementation project manager oversees and directs the deployment
of new products, services, or projects for an organization. The project manager creates a blueprint for
the project, defines the milestone, and creates the work breakdown structure.

• In the build & test phase, the changes are implemented first. These changes might be a solution
extension with custom development activities, Customizing changes, or integration of a partner or third-
party application. Developers perform tests of the functions, while quality assurance prepares functional
tests and tests of user acceptance for the next phase. The list of relevant business processes determines
which tests are covered. Therefore, the build & test phase involves all relevant kinds of tests, including
the following:

o Regression tests
o Integration tests

o Scenario tests

o User acceptance tests

o Performance tests

• The objective of the deployment phase is to transition from the pre-production environment to
live operations. In this phase, support structures are created for end users that are available not only
during the critical period after going live, but also in the long term.

• The longest phase in the lifecycle is the operate phase, in which the end users work with the
product. In this phase, any errors that occur are fixed by SAP developers in the form of error corrections.

• During the operate phase, it may become apparent (through an analysis of compliance with
service level agreements, for example) that optimizations are needed. In the optimize phase, you carry
out the activities that are required to improve the results. This can also result in new requirements.

Skipped Pages:

• 79 – 104

o Unit 3 – Lesson 3: Describing SAP GUI functions, help, and personalization

o Unit 3 – Lesson 4: Describing navigation using a web browser

o Unit 3 – Lesson 5: Describing SAP business client

• 115 – 152

o Unit 4 – Lesson 2: Describing AS ABAP

o Unit 4 – Lesson 3: Describing AS Java

o Unit 5 – Lesson 1: Describing the data structure of an AS ABAP based SAP system

• 175 – 317

o Unit 5 – Lesson 4: Importing transport requests into AS ABAP based SAP systems

o Unit 5 – Lesson 5: Transporting non-ABAP objects

o Unit 5 – Lesson 6: Appendix: basic software development concepts for the cloud

o Unit 5 – Lesson 7: Appendix: describing SAP UI Technologies

o Unit 6 – Lesson 1: Describing application lifecycle management

o Unit 6 – Lesson 2: Implementing business processes and installing SAP systems

o Unit 6 – Lesson 3: Describing business processes operations

o Unit 6 – Lesson 4: Maintaining SAP systems

o Unit 7 – Lesson 1: Describing remote function calls and BAPIs

o Unit 7 – Lesson 2: Explaining cross-system business processes

o Unit 7 – Lesson 3: Explaining HTTP based communication

o Unit 7 – Lesson 4: Describing web services

o Unit 7 – Lesson 5: Describing SAP Gateway

o Unit 8 – Lesson 1: Describing SAP release strategy

o Unit 9 – Lesson 1: SAP support portal

o Unit 9 – Lesson 2: SAP help portal

o Unit 9 – Lesson 3: SAP community and SAP tutorial navigator

o Unit 9 – Lesson 4: SAP road map explorer

o Unit 9 – Lesson 5: SAP discovery center

o Unit 9 – Lesson 6: SAP Learning offerings