SAP Hana Exam Content
SAP Hana Exam Content
Index
Lesson 1: SAP HANA Platform
Database Management
● Columnar OLTP + OLAP
● Row Store and Column Store
● Advanced Compression Techniques
● Primary Key Indexes
● Multicore and Parallelization
● Partitioning
Multitenancy
● Classic Architecture in SAP HANA 2.0: Multi-Tenant-DB (MDC)
● System Database (SystemDB) and Tenant Databases
● Services in System DB and Tenant DB
● Deployment Options: SCSO, MCOD, MCOS
Data Persistence
● In-Memory Storage for Performance
● Log Memory and Persistent Log Memory
● Asynchronous Writing of Changes
● High Availability: Scale Out and Disaster Recovery
Advanced Analytical Processing
● Data Modeling for Multi-Dimensional Structures
● Search, Text Analytics, and Mining
● Spatial Processing for Enriching Business Data
● Graph Engine for Discovering Relationships
● Predictive Analytics and Machine Learning
● Streaming Analytics for Real-Time Data
● Series Data Storage and Services
SAP HANA Application Development
● Webserver and Database in One System
● Consumer-Grade User Experiences
● Support for Standards and Languages
● Built-in Tools for Application Development
Data Integration and Quality
● Replication for Data Integration
L2
L3
HANA DEPLOYMENT OPTIONS: SAP HANA Hardware Options, Sizing, Scale-up & Scale-out, Multitenant Database Containers (MDC), and
Virtualization
L4
L5
L6
L7
L9
● Data Tiering
■ What is Data Tiering?
■ Data Aging and Top-Down Data Flow Through the Pyramid
■ Data Funnel and Bottom-Up Data Flow Through the Pyramid
■ Leveraging the Strengths of Each Tier in the Pyramid
● SAP HANA Cloud, Native Storage Extension (NSE)
● SQL on Files: Overview and Use Cases
L10 &11
L13
9
Lesson 12: SAP Analytics Cloud - Introduction
1. Implementation Approach:
2. Customer’s expectations and Accelerating delivery of outcomes
3. Key Elements Driving Successful Deployment:
4. Deploy SAP S/4HANA On-Premise with SAP Activate - Journey Overview and Key Milestones
7.1. Golden Rules 1 “Cloud Mindset” and 2 “Use Pre-configuration and Fiori” - Conduct Fit-to-Standard Workshops and
Technical Design
7.2. Golden Rule 3 “Use modern integration technologies” - Integration Planning and Design
7.3. Golden Rule 4 “Use modern extensions technologies” - Extension Planning and Design
7.4. Golden Rule 5 “Transparency on Deviations” - Document Exceptions
9. Enablers for Your Digital Transformation - SAP Activate Tools and Community
A. SAP S/4HANA Cloud Overview and Why SaaS Cloud ERP from SAP?
B. SAP S/4HANA Cloud - Strategic choice to embrace the future of ERP and General Architecture
C. Multi - tenant view
D. Accelerate Time to Value with SAP S/4HANA Cloud Implementation Tools
E. Administration and Maintenance:
1. SAP S/4HANA Cloud, public edition delivery with SaaS, Responsibilities Move from Customers to SAP and
Landscape overview
2. Release Schedule
F. Security and Trust- Network Architecture
G. SAP extension strategy-cloud extensibility
H. SAP Integration Strategy
I. Reporting and analytics - SAP analytics cloud
13
1) Database Management
● The column store allows for efficient compression of data. This makes it less costly for the SAP HANA database to keep data in main
memory. It also speeds up searches and calculations.
Advanced Compression:
● Dictionary compression is the default method of compression applied to all columns at write time in the delta storage - It involves the
mapping of distinct column values to consecutive numbers, so that instead of the actual value being stored, a much smaller
consecutive number is stored.
14
● Each column can be further compressed using different compression methods: prefix encoding, run length encoding, cluster
encoding, sparse encoding, and indirect encoding.
● Columnar storage allows for more efficient parallel processing - Each processor can scan a column or portion of a column in
parallel
● Columnar store to process transactions and queries where OLTP+OLAP on single copy of data
● Write operations are only performed on a Delta storage optimized for transactions
● Delta storage is merged periodically with main storage
● No data duplication – Data kept either in delta storage or in main storage
Calculations are typically executed on individual or a small The application needs to process only one single record at
number of columns. one time (many selects and /or updates of single records).
The table is searched based on the values of a few columns. The application typically needs to access the complete
record.
The table has a large number of columns. The columns contain mainly distinct values so compression
rate would be low.
The table has many rows and columnar operations are Neither aggregations nor fast searching are required.
required (aggregate, scan, and so on)
17
High compression rates can be achieved because the The table has a small number of rows (for example,
majority of the columns contain only a few distinct values configuration tables).
(compared to the number of rows).
• Parallelization
Multitenancy:
Data Persistence
High Availability:
- Scale Out is a Multi-Host System which consists of worker and standby nodes
o Worker Node – process data
o Standby nodes – wait until a takeover of a failed worker node
- Disaster Recovery (DR-Setup) via Storage Replication
o Replication of all persistent data (data & logs)
o Secondary SAP HANA DB is not active (cold standby)
- High Availability (HA-Setup) via System Replication
o 2 identical SAP HANA systems (same number of active hosts, same SID, ...)
o after the configuration, an initial transfer of all persistent data (data and logs) takes place
o after initial transfer, data transfer via synchronous or asynchronous log transfer (configurable)
Data Modeling:
Spatial processing: new insights from enriching business data with spatial data
Graph engine: Discover relationships and deeper insights on-the-fly from connected data
Predictive analystics/ML
22
Streaming analystics – Streaming and business data combined for real-time action
Series data storage and services – Native series data storage and processing:
Web Server:
24
25
4. Data Integration and Quality
Data virtualization:
Replication:
26
27
28
LESSON 2: SAP HANA – DATA ARCHITECTURE
Contents:
Main memory consumer in SAP HANA is the Index Server. It stores data mainly in two ways:
● Column Store – by far the largest amount-- The column store has a very strong compression ratio
● Row Store – small amount of customizing data- Mainly tables with many small Data Manipulation Language (DML) statements
30
3) Table Partitions
31
Partitioning:
● Partitioning allows tables to be subdivided into smaller pieces, enabling these database tables to be managed and accessed at a finer
level of granularity.
● SAP HANA provides a variety of partitioning strategies to address every business requirement. Being absolutely transparent to
applications, partitioning can be applied without the need for application changes.
● Typical Use Cases:
o Load balancing- Scale-out, Numa nodes
o Parallelization- Merges, Data access and Log replay
o Partition pruning- Optimize table access
o Explicit partition handling- Easy house keeping
● Specific to HANA
o Overcame the 2 billion record limit
o Faster delta merges
32
33
4) Data Tiering
Move data to the storage location that fits best to your business requirements
Value proposition:
Use cases:
● Any customer built, or SAP built HANA application that is challenged by growing data volumes
● S/4HANA data aging (NSE is an evolution of “paged attributes”)
● BW team currently uses extension nodes, but may evaluate NSE in the future
35
36
37
LESSON 3: HANA DEPLOYMENT OPTIONS
Contents:
● Differentiating Capabilities:
2) Sizing:
● Memory sizing:
40
Scale – Basics:
41
Scale in all directions:
- Data
- Memory
- Availability
- Throughput
- CPU
- Orchestration
Scale-Out:
Landscape - Overview
- Scale Out Landscape
● N active servers in one cluster
● M standy servers in one cluster
● Shared file system for all servers
- Scale Out Capabilities
● Large tables are distributed across servers
● Queries can be executed across servers
● Distributed transaction safety is ensured automatically
- Maximum Scale Out
● Maximum of 56 servers supported in high availability configuration
(Hardware Vendor dependent)
Table Distribution: ● A multi host system can use the advantages of table distribution
● Different tables may be assigned to different index servers that
normally run on different hosts
42
● When non-partitioned tables are created they are assigned
across available index servers using, by default, round-robin
approach:(see figure)
● It is also possible to explicitly assign a table to an index server
during creation with SQL:
● create [column] table <table_name> <table_contents_source> at
'host:port'
5) Virtualization:
In order to ensure optimal performance and stability of your SAP HANA system in a virtualized environment, it is important to adhere to the
following restrictions:
● Compliance with SAP and Vendor Guidelines: The configuration and setup of your SAP HANA virtualized system should be in
accordance with the current version of the "SAP HANA Guidelines for being virtualized" and any vendor-specific best practice
documents related to running SAP HANA on the corresponding hypervisor.
● Proper Sizing of Each SAP HANA Instance: It is crucial to size each SAP HANA instance or virtual machine as per the existing SAP HANA
sizing guidelines and the recommendations of the respective hypervisor vendor. Over-provisioning of CPU and memory resources
should be avoided to prevent potential system instability and performance degradation.
● Limitations on the Size of Virtual SAP HANA Instances: Except for "SAP BW, powered by SAP HANA in scale-out", the maximum size of
virtual SAP HANA instances is constrained by the maximum size the hypervisor supports per virtual machine and the specifics
dependent on the host.
44
● Certified SAP HANA System Setup: The SAP HANA system must be set up by an SAP HANA certified engineer using SAP HANA certified
hardware. The setup should be successfully verified with the SAP HANA hardware configuration check tool (HWCCT, SAP HANA Tailored
Data Center Integration) to ensure compliance with all required specifications and standards.
● Nested Virtualization Not Supported: SAP does not support nested virtualization, which involves running one hypervisor within
another. However, customers may run virtualized applications on physically separated hardware partitions to ensure system stability
and performance.
45
Lesson 4: HANA Reporting & Analysis
Contents:
● In-Memory Reporting and Analytics
o SAP HANA as an Analytics Platform
o Traditional Business Intelligence Vs HANA XSA 2(3)-Tier Architecture
o SAP HANA Data Modeling Overview & Native HANA BI Applications
o Three Types of Information Views
o SAP HANA Data Modeling Overview In XSA
o List of all SAP Analytics applications
o Analytics on SAP HANA
● SAP Web IDE Storyboarding
“Information views are used for analytical use cases such as operational data mart scenarios or multidimensional reporting” For example:
Reporting on revenue and profitability
● Attribute View
● Analytic View
● Calculation View (cv)
Remember! we did this in class (After creating all the views, we saw bar graphs and stuff)
49
50
Lesson 05 Data Modelling with SAP HANA
8. What does Multi target application MTA in SAP HANA XS Advance contain
● For example: Database Module, Java Module, Node.js Module
● Contains all design-time objects related to the SAP HANA database: calculation views, procedures, table definitions and
further
● Design-time objects are automatically transformed into runtime objects as soon as a file is saved
52
9. What are the Features of SAP HANA XSA – Database Explorer
● Allows developers accessing and testing SAP HANA database objects and content from SAP HANA database schemas
represented as HDI Containers
● Developers access the database explorer clicking on the corresponding symbol:
● Allows viewing and interacting with database content, such as calculation views or stored procedures (Also allows direct
SAP HANA Tenant and Schema access)
10. What are the functionalities of SAP HANA XSA – Database Explorer ?
SQL Debugger, SQL Console, SQL Analyzer, MDX Console, Database catalog browser
Data Preview
● Available for tables and views
● Can be used to confirm the correctness of the data model and the loaded data
26. Deployment
Save and activate
● When you save, your model is stored and activated
● Errors in activation can be analyzed in the console
● Activation creates a column view in the system schema _SYS_BIC
● For reporting, the Column View of this schema is used
60
Data Preview
● Available for tables and views
● Can be used to confirm the correctness of the data model and the data loaded
27. SAP Hana View Modelling 🡪 Virtual Data Models for Multidimensional Scenarios
61
28. SAP Hana View Modelling 🡪 Virtual Data Models for Normalized Data Model Scenarios
62
Lesson 06 : Machine Learning
Uses text, spatial, and graph processing along with machine learning.
Support both
Addresses key scenarios like Classification, Regression or Time Series Forecasting (and more) – Over 100+ classic and trending ensemble
algorithms – High performance parallel mass prediction, real-time transactional speed prediction – Segmented Modeling, like segmented
Forecasting – Automated cross validation and hyper parameter selection
64
• 1st Column must be of type Integer, Varchar or Nvarchar and should be an unique ID
• 2nd Column must be of type Double and represent a value for an unique ID
65
Parameter Table
● Parameter Table is deleted to make sure that no table with the same name exists New temporary table is created.
• General parameter table structure for PAL
• Parameter table name is free to choose
• Parameter table name has an „#“at the
Insert parameters with „Insert into “with
the necessary parameter name and value
in the correct column
66
SAP AI Strategy
70
SAP AI Technology Portfolio
SAP AI Portfolio
71
L7- Data Consumption & Native Application Dev
SLIDE 1:
Frameworks
High-level / Object
Interface: The high-level
or object interface
allows developers to
work with SAP HANA
using popular
frameworks and tools.
Network Protocol: The network protocol in SAP HANA is called SQLDBC. It is a communication protocol that allows applications to connect
and interact with SAP HANA over a network.
72
SLIDE 2:
SLIDE 1:
Programming Model –
Paradigm Shift: Responsibilities in Runtime Layers
SLIDE 2:
SLIDE 3:
What is XSA?
Is used for a set of functions that CAN - but NOT MUST – be used together as:
SLIDE 4:
● XSA provides application services which are fully integrated into HANA
● Controller applications can run natively on SAP HANA
● Exposing database
data model, tables, views and database procedures via OData services
● XSA connects to indexserver to read tables or views, modify
data or to execute SQLScript database procedures and calculations
● SLIDE 5:
SLIDE 6:
● Organizations can be
used to, e.g.
- Logical group Line of Business development
- Logical group security related development from other develoment
● Spaces can be used to, e.g.
-Separate Line of Business development
-Separate security related development from other development
-Separate privileges for role development
● Projects can be used to, e.g.
-Separate sets of roles for different target systems
SLIDE 7:
SLIDE 8:
HDI acts as a helpful tool that makes it easier to set up and distribute the database artifacts and the applications built on top of it within the
SAP HANA platform.
SLIDE 1:
-Modern web application are data-driven, meaning the application is build around the data
-This is reflected in the usual development cycle of SAP HANA native applications
-The data available in the database is processed by the different SAP HANA engines and presented to
the user through an SAPUI5 App.
Load Data: The first step is to load the required data into
SAP HANA. This data could come from various sources,
such as databases, files, or other systems.
Create SAPUI5 App: A SAPUI5 app is developed to build the user interface of the web application. SAPUI5 is a framework that provides
pre-built user interface controls and tools for creating responsive and interactive web applications.
Bind OData Service to App: The OData service created in the previous step is bound to the SAPUI5 app. This connection allows the app to
retrieve data from the calculation view and display it in the user interface.
Repeat: Once the initial version of the app is created, additional elements can be added to enhance its functionality. This can include
additional UI controls, navigation, or custom features)
76
SLIDE 3:
-The SAP HANA platform not only provides the application platform on which Apps can run, but also
includes all development tools required for the whole development process.
-SAP Web IDE is a powerful, extensible, web-based integrated development tool that simplifies end-to-end full-stack application that can be
accessed with the web browser.
-Development artifacts are stored in the XSA runtime and in HDI containers.
(The SAP HANA platform is not just a place where applications can run, but it also offers all the necessary tools for developing those
applications. One of these tools is SAP Web IDE, a web-based development tool that makes the entire application development process
easier.
SAP Web IDE is a powerful and flexible tool that you can access using a web browser. It allows developers to create full-stack applications
from start to finish. You can use it to write the code, design the user interface, and handle all aspects of application development.
When you develop applications using SAP Web IDE, the different components of your application, such as code, database objects, and other
related files, are stored in two main places: the XSA runtime and HDI containers.
The XSA runtime is like a storage area that holds all the necessary resources and components for running your application. It provides a
runtime environment where your application can execute and interact with other parts of the SAP HANA platform.
HDI containers, on the other hand, are used for managing and organizing the development artifacts of your application. They act as
containers or packages that hold related components together. You can think of them as folders that keep your application's code, database
objects, and other files organized in a structured manner.)
SAP HANA platform provides various tools and frameworks, such as SAP Web IDE and SAP HANA XS (Extended Application Services), to
support web development on the SAP HANA platform. These tools offer features and functionalities specifically designed for building and
deploying web applications.)
HDI container is a logical construct on database level (HDI (SAP HANA Deployment Infrastructure) container is like a virtual container within
a database. You can imagine it as a folder or a box that holds related things together.)
§ To simplify we imagine it as a database schema (HDI container has a schema, which is like a blueprint or a plan for how the objects are
organized and stored within the container, making it easier to manage and retrieve data from them.)
§ The container has an object owner (An HDI container has an owner who is responsible for managing and controlling the objects inside it.
This owner has certain permissions and rights to perform actions on the objects, such as creating, modifying, or deleting them.)
§ Some APIs and a schema for storage (An HDI container also provides some tools, known as APIs, that allow developers to interact with
the container and work with the objects it contains.)
77
“Zero” privileges by default: HDI Container Isolation ensures that the objects within the container have limited privileges and cannot access
or interact with objects outside the container.
Object owner is a restricted database user: The object owner has restricted access rights and can only operate within the container's
boundaries.
CREATE ANY Privilege: The object owner, despite being restricted, has the CREATE ANY privilege on the schema within the HDI container.
This privilege allows them to create, modify, and manage objects within the container.
§ Explicit Grant SELECT ON ERP.Y (with Grant Option) to the container‘s object owner: To break the "Zero" privileges, the object owner of
the container can be explicitly granted the SELECT privilege on an external object called ERP.Y. This permission allows the object owner to
access and retrieve data specifically from that external object.
§ Deployment-specific configuration artifacts can override target specifications (transport): During the deployment process of the HDI
container, specific configuration artifacts can be used to modify or override target specifications. These artifacts allow for adjustments to be
made to the container's settings, tailoring them to the specific requirements of the target system or environment.
Each app has its own HDI container: Each application within XSA has its own HDI container. Think of an HDI container as a separate space or
container that holds all the necessary components, objects, and data specific to that application. It acts as a self-contained environment for
the application.
In WebIDE, there is a sandbox container for each project: In the WebIDE (Web Integrated Development Environment), there is a sandbox
container created for each project. This sandbox container is like a dedicated space for each project within the WebIDE. It holds all the
development artifacts, such as code, database objects, and configuration settings, related to that specific project.
Change Management:
SLIDE 1:
SAP HANA is built for creating and running enterprise applications.
Tracking changes and testing is an integral part of the development process.
(Tracking changes: This involves keeping a record of modifications made to the application code, database schema, or configuration settings.
Tracking changes helps in maintaining a clear audit trail, facilitating collaboration among developers, and ensuring that changes are properly
documented and tested.
Testing: It involves verifying the functionality, performance, and quality of the application. Various types of testing, such as unit testing,
integration testing, and user acceptance testing, are performed to identify and address any issues or bugs before the application is deployed
to production.)
The development process for SAP HANA applications typically follows a 3-System-Landscape approach, which involves the use of three
separate systems: Development, Quality Assurance (QA), and Production.
Development System: The development system is where the actual coding and development of the SAP HANA application takes place.
Developers work in this system to write and test the application code, implement new features, and make enhancements.
Quality Assurance System: The QA system is used for testing and quality assurance purposes. Once the development work is completed in
the development system, the application is deployed to the QA system for rigorous testing.
Production System: The production system is the live environment where the SAP HANA application is deployed and used by end-users in a
real-world operational setting.
80
Lesson08 : SAP HANA Cloud
Architecture
● § Common replication SQL-Interface combining SDA Remote Table Replication and standard SDI based Replication
● § Optimized HANA to HANA replication with Remote Table Replication (Native HANA Engine Feature) using transaction layer logs
● § Flexible connectivity options via standard SDI replication supporting any source
● § Flexible storage options for table replicas in HANA Cloud (In-memory or Native Storage Extensions)
● § Remote Table Replication supported between on-premise SAP HANA SPS05+ and SAP HANA Cloud (via SAP Cloud Connector)
‘
83
Data Acquisition and Data Consumption
Capabilities
● § Integrated into HANA Cloud Instance
● § Automatically provisioned and administrated with HANA Cloud
● § Based on existing SAP technology
● § Highly optimized SDA connection include “query delegation”
● § Elastic scale, independently of SAP HANA DB
● § High-speed ingestion enablement
● § Access to cloud storage (e.g. AWS S3, GCP Cloud Storage)
● § Shared storage using the NetAppCloud Volumes Service
Benefits
● § Ingest any data from cloud or on-premises data sources
● § Easy to set up and use (single access layer in HANA Cloud)
● § Low TCO
● § Fast analytic processing through columnar architecture
84
Datacenter Locations
High Availability
One Availability Zone
SAP HANA Cloud controlled synchronous replication with autonomous failover capability
● § SAP HANA Cloud replicates all persistent data and changes to second server in same availability zone
● § Fail detection and autonomous, automatic host failover managed by SAP HANA Cloud
● § Failover
○ – Automatic switch in case of indexserver outage (e.g. hardware crash)
○ – Switch time < 30 second
○ – SAP HANA Cloud clients wait during the switch time
85
○ – Read transactions continue after switch
○ – Write transaction roll back, corresponding running statements fail
Multi-Zone Replication
Two Availability Zones
Based on SAP HANA System Replication
● § Replication of full system with all persistent data between availability zones
● § Asynchronous replication to absorb high latency due to distance
● § Takeover
○ – Switch service via ticket due to asynchronous replication
○ – Pure switch time < 2 minutes
○ – SAP HANA clients wait during the switch time
○ – Read transactions continue after switch
○ – Write transaction roll back, corresponding running statements fail
○ – Zone B replica automatically created after takeover
86
87
Monitoring & Administration
Security framework
88
Scenarios
Use cases
89
Lesson 09 Data Tiering
Data Aging
Top Down Data Flow Through the Pyramid
● § Data enters the pyramid at or near the top
● § Data is moved or copied to lower tiers
● § Consistent data schema is maintained in every layer
● § Consuming applications can choose:
○ – Only “current” rows (faster)
○ – Complete (all tiers)
▫ May be slower depending on query
▫ Pruning of tiers ideally gives similar performance
● § “Age” data by usage pattern not necessarily insert age– Table structure must support data tiering
○ Eg: ORDER_DATE < yyyymmdd AND ORDER_STATUS = “Closed”
● § Data remains updatable in HANA and HDLRE– Contrast with Data Archiving
Data Funnel
Bottom Up Data Flow Through the Pyramid
● § Data enters the pyramid at or near the bottom
● § Data is processed before being moved or copied to higher tiers
● § Data schema may vary between tiers
SAP HANA Cloud, Native Storage Extension enables PAGE LOADABLE data
• Hot COLUMN LOADABLE data:
• HANA is an in-memory database, and loads all data into memory for fast processing.
• Data is “column loadable” and resides completely in memory.
• Warm PAGE LOADABLE data:
• With NSE, less frequently accessed data may be specified as “page loadable”.
• “Page loadable” data is loaded into memory in granular units of pages as required for query processing.
• NSE will reduce memory footprint for “page loadable” data. Data is partly in memory, and partly on disk.
• Query performance on warm data may be somewhat reduced compared to hot data.
• Data may be converted between “column loadable” and “page loadable”.
91
SQL on Files
Overview
Provides a bridge between Data Lake Relational Engine and Data Lake Files
§ Virtual tables are defined in Data Lake Relational Engine over structured (.csv, Parquet) files in Data Lake Files
§ Allows for low TCO analysis of relational data with unknown value
• Pre-exploration and filtering of data before moving it up the pyramid into Data Lake Relational Engine, NSE, or HANA DB
• Data that must kept for regulatory purposes and is rarely queried
92
93
L10 : SAP HANA Database Explorer
SAP HANA Cloud Central : Web-based tool for managing SAP HANA Cloud, SAP HANA database and data lake instances.
SAP HANA Cockpit : Web-based application, used for monitoring, administration, security and user management of SAP HANA Cloud, SAP
HANA database and data lake instances.
SAP Business Application Studio : A modular development environment enabling the creation of business applications for SAP HANA Cloud.
It is the successor for the SAP Web IDE on SAP HANA Cloud.
Visual Studio Code : SAP provided extension enables SQL queries to SAP HANA Cloud or on-premise databases
SAP BTP Cockpit : Web-based administration interface that provides access to functions for configuring and managing applications, services,
and subaccounts.
SAP Data Warehouse Cloud : An enterprise-ready, data warehouse in the cloud. It addresses analytics needs and provides prebuilt business
content and advanced analytics.
Usage : Supports connections to – SAP HANA databases – HDI Containers – Data lake Relational Engine databases – Data lake Files
containers
Add Database dialog : Provide values to connect to a database § Search for existing HDI Containers or Cockpit database types.
Tracing : Find, view, and download trace files for SAP HANA or data lake databases.
SQLScript Analysis : Identify patterns indicating potential problems in code quality, security, or performance.
Create Instance
● § Create new database, data lake instances. § Choose to display only SAP HANA database
● instances, only data lake instances or both.
● § Stop, upgrade, add a data lake, delete, or edit the instance.
● § Administer the instance and execute SQL from the list.
● § Open SAP HANA cockpit and SAP HANA database explorer in a new tab.
● § Allows to copy the instance ID, SQL endpoint.
Index
1. SAP BTP – Business Technology Platform
2. Features – BTP
3. BTP Suite Qualities
4. BTP HANA Capabilities
4.1 Application Development
4.2 Automation
4.3 Integration
4.4 Data and Analytics
4.5 AI
SAP BTP Onboarding Center
5. SAP Discovery Center – one-stop shop for all SAP BTP resources
6. SAP BTP Commercial Models and Links
7.
2. Features – BTP
● Development environment for both, professional IT and citizen/business developers
● Has prebuilt data models, integrations, workflows, app templates, and AI business services
● Self-service data discovery, modeling, planning and analytics, for business users
● Availability on Microsoft™ Azure™, AWS™, Google Cloud™ and Alibaba Cloud™
3. BTP Suite Qualities
● Seamless user experience
● Consistent security and identity management
● Aligned Domain Models, APIs, and Events
● Embedded and cross-product analytics
● One workflow inbox
● Coordinated lifecycle management
● End-to-end process blueprints
4.2. Automation
Automate tasks visually using drag-and-drop and AI capabilities, seamless integration with tools for SAP and non-SAP systems and
collaborate securely. There are 100s of pre-built automations and API complexity is hidden.
4.3. Integration
● Holistic approach to data and process integration
● Thousands of SAP & third-party prebuilt integrations and a best-practices methodology
● AI-powered development and deploy to your cloud of choice
99
4.5. AI
● AI services embedded natively into SAP applications and services
● Deploying AI pre-trained & custom models built for business use cases
● Run AI responsibly according to SAPs guiding principles and AI Ethics Policy
6. SAP Discovery Center – one-stop shop for all SAP BTP resources
● Explore BTP Use Cases & Services
● Explore BTP Use Cases & Services
● Realize the Use Cases as a Mission
● Be Inspired by Customer Stories
● Gain More Insights into the Service(s)
● Analyze & Estimate Costs
● Adapt the Architecture
3.3. Collaboration
● Commenting: Comment on stories, applications, and specific data points in tables. Engage with other users by liking, replying, and
addressing them using @UserName.
● Discussions: Initiate discussions on your analytics to collaborate with other SAP Analytics Cloud users and teams. Easily engage in
discussions on both desktop and mobile devices.
● Sharing: Effortlessly share private or public stories and bookmarks with any SAP Analytics Cloud user or team using a customized
link. Simplify collaboration and knowledge sharing.
ERA Mainframe & PCs Client Server & Cloud, Mobile & Big Intelligent Technologies
1960s – 1980s Internet Data 2010s - 2020s
1990s - 2000s 2000s - 2010s
Enabled technologies • Transistors & silicon • Widespread PC • Mobile & Smartphone • Machine Learning &
revolution adoption ubiquity Artificial Intelligence
• Large scale Mainframe • Broadband Internet • Cloud Computing • IoT & Distributed
Computing adoption • ERP and business • Social Networks computing
• Emergence of PC’s process • Big Data • Blockchain
• Plant floor automation technologies
Customer value Industrial Business Digital Intelligent
creation Automation Process Transformation Enterprise
Automation
2- SAP Versions
ERP is a system that optimizes the flow of Information, materials and cash flow in an organization.
107
4- SAP Modules and their parts
Material Management Finance (FI) Production Planning (PP) Sales and Control (CO)
(MM) Distribution (SD)
Purchase request Account payable Forecast Sales order Accounts receivable
Approval Financial accounting Material resources Delivery Management
Purchase order General ledger planning (MRP) Goods issued accounting
Goods receipts Production Bill Real-estate
Invoice receipts manufacturing management
Inventory stock
Transactions, planning, analysis, simulation, prediction / Intelligent business automation / Immediate business insight at any level / Business
role–based.
In-memory database / Embedded AI, machine learning, and bots / Any data at any level with embedded analytics / On premise, cloud, and
hybrid.
SAP Fiori is a design system that enables you to create business apps with a consumer-grade user experience, turning casual users into SAP
experts with simple screens that run on any device.
HANA “High-Performance Analytic Appliance” is an in-memory, column-oriented, relational database management system. Its primary
function as the software running a database server is to store and retrieve data as requested by the applications.
The SAP HANA database has its own scripting language named SQLScript, supports specialized and optimized functional libraries, such as
SAP HANA Business Function Library (BFL) and the SAP HANA Predictive Analytics Library (PAL). SAP HANA also supports the development of
programs written in the statistics language R.
A Business Partner in SAP is an entity that you work with to exchange business data between your company and the other Business Partner.
A Business Partner can be a customer, supplier, or partner company.
Embedded Analytics
§ Deliver contextualized analytics for SAP S/4HANA embedded within the context of work and tailored to business needs and roles
§ Consist of Virtual Data Models based on Core Data Service (CDS) views covering role based operational reports for lines of business
§ Come with tools for Business Users, Power Users and Developers to analyze data and manage the lifecycle of reports and KPIs
110
Functional Highlights
§ Extended virtual data model and set of KPI’s, for LoBs (e.g. FIN, SD, MM, QM, MM, PLM, PP, etc.) and Industries (e.g. O&G)
§ New SAP Fiori applications (see SAP Fiori Apps Library) including Predictive and Machine Learning use-cases
§ New SAP Smart Business runtime
§ Extended Multidimensional Reporting client
§ Report function (guided process)
§ Other functional enhancements (e.g. Date Function)
Integration highlights
§ Integrated Applications using SAP Fiori 2.0 floorplans (Analytical List Page, Overview Page etc.)
§ Create Tile for SAP Analytics Cloud Story
■ Lists the analytical queries assigned to the roles of the current user
Buy, supply, make, sell, finance, design, maintain, service, people, cross topic.
As a product As a service
On premise Cloud
SAP S/4HANA system is installed and Public cloud Privet cloud
managed within the customer's own Multiple customers share the same Deployment in a private cloud
data center. infrastructure, SAAS. environment, either managed by the
customer or a third-party provider.
18.1 – SAP S/4 HANA Deployment flexibility
Monetary Gain –
Gain Productivity, Data Quality
Save Training Costs
Decrease Change Request, User Errors
Human Value –
Increase User Satisfaction, Inclusion, Customer Loyalty, Solution Adoption
Strengthen Relationship (IT and Business)
Q2) How does SAP Fiori help people to get business done easily?
SAP Fiori is user experience for the intelligent enterprise, enabling users to get their job done in an easy and delightful way. It is the target
user experience for each and every product developed at SAP. SAP Fiori can be implemented on various UI technologies and platforms.
Design system
Design principles, design guidelines & design artefacts
SAP Fiori apps provided by SAP
Responsive apps and native ones
Development tools
Such as SAP Fiori tools, SAP Fiori for mobile SDKs,
SAP Business Application Studio or SAP Screen Personas
Technology
Such as the SAP Fiori elements, SAPUI5, OData, and etc.
Design System
Values Principles Practices
Design Languages
• Look & Feel
• Controls & Floorplans
• Common Functions
• Guidelines & Stencils
Technologies
SAPUI5, iOS, Android, Other Technologies
Consistent
SAP Fiori visual design and SAP SuccessFactors have Horizon Themes
Integrated
What does AI mean for a user?
Helps users achieve more and better results with less effort
Integrated
Entry Point for users
Federation layer:
Get relevant content across all SAP Solutions
SAP solutions layer:
Get relevant content across one SAP Solution
Horizon supported today by:
SAP Start
SAP Mobile Start
SAP Build Work Zone
Collaborated
“Share to MS Teams” improves collaboration of SAP S/4HANA users
Seamless integration: Share content from SAP Fiori elements apps
Access to live data: Link to filtered data
Pre-integrated: Activation with only one setting
No additional costs
“Customers who don’t implement SAP Fiori or continue to use SAP GUI as their primary UI will have only a limited benefit from the
innovations in SAP S/4HANA”
“Selectively implementing only some individual SAP Fiori apps not only breaks the user experience but also results in very high
implementation costs … SAP Fiori apps are not designed to be used individually.”
SAP Offers Customers Choice of HOW they MOVE to S/4HANA. What are the choices that must be made?
Questions to ask:
● How much HANA do I need?
● Are my add-ons compatible with SAP S/4HANA?
122
● What SAP Fiori apps are available?
● What business functions are affected?
● What transactions are affected?
● Will my custom code work with
● SAP S/4HANA and if not, what do I do?
Prepare users and systems Determine the transition Adapt custom code Choose deployment
path destination
-Readiness Check -Greenfield (new -Assess custom code -On premise
-Business Value Advisor implementation) inventory* -Cloud
-Prototypes -Brownfield (conversion) -Address inefficiencies* -Hybrid/multi-tier
-Landscape transformation -Adapt code to S/4HANA
3. System Conversion
System Conversion
123
124
The Simplification List is a collection of Simplification Items. Within a Simplification Item it is described what is the difference of a
functionality between SAP Business Suite and SAP S/4HANA.
● Currently the Simplification List provides this information per each dedicated SAP S/4HANA on-premise release, and
● will be provided as part of the SAP S/4HANA documentation.
● A Simplification Item does have a simplification category and provides information about the potential impact for the customer.
125
● Based on the simplification item custom code check analysis can be executed.
● Will be used by the SAP Readiness Check
Detailed scope
Which products to use? -Product recommendation for all currently used products
126
Which solution to -Pre-load of solution profile from SAP Solution Manager + ability to add products
use in which use-case? -Capability based addition of product recommendations
-Recommendation sensitive to deployment strategy (e.g. Cloud vs. on-premise)
and
current scope of use (e.g. ERP modules/solution capabilities)
-Suitable for landscape transformation, business transformation and greenfield
approach
-3y roadmaps for on premise, rolling 4 quarter roadmaps for cloud products and
solutions
Cost of Migration? -Transition type (e.g. upgrade, conversion, process transformation) transparent
-Overview of necessary transitions and available services
Integration? -Integration technology guidance paper
-Integration guides
Value of innovation? -All products have capability-based value drivers
-Top value drivers have aspiration ranges
-Realization Tracking KPIs mapped
Cost of new solution? -Relevant licenses and conversion policies described
Roadmap Viewer
The SAP Road map viewer enables customers to easily get access to SAP Activate Methodologies and Solution Manager roadmaps. That
means the road map viewer is typically used at the beginning of S/4HANA implementations for discovery and validation purposes providing
an “always up-to-date” version of a S/4HANA road map. The purpose of this road map is to support implementation projects of SAP
S/4HANA with a structured documentation to:
● Manage risk proactively
● Make implementation projects predictable
● Create a viable foundation through transparency of all activities and tasks
The SAP Road map viewer serves as a starting point for project planning, and must be tailored and maintained continuously as part of the
project planning and execution activities. Customers can load the SAP Activate roadmaps from the road map viewer into SAP Solution
Manager 7.2 for use as project plan templates.
In case customers need additional help on top of the offered self-service, SAP provides dedicated services supporting the implementation of
SAP S/4HANA, the so-called “SAP S/4HANA Value Assurance service packages”.
127
Lesson 17: SAP HANA Activate methodology
13. Deploy SAP S/4HANA On-Premise with SAP Activate - Journey Overview and Key Milestones
15. Deploy with SAP Activate - Journey Overview and Key Milestones
16. Golden Rules for Implementing SAP S/4HANA with a Cloud Mindset
16.1. Golden Rules 1 “Cloud Mindset” and 2 “Use Pre-configuration and Fiori” - Conduct Fit-to-Standard Workshops and
Technical Design
16.2. Golden Rule 3 “Use modern integration technologies” - Integration Planning and Design
16.3. Golden Rule 4 “Use modern extensions technologies” - Extension Planning and Design
16.4. Golden Rule 5 “Transparency on Deviations” - Document Exceptions
18. Enablers for Your Digital Transformation - SAP Activate Tools and Community
------------------------------------------------------------------------------------------------------------------------------------
2. Customer’s expectations have changed and hence Software providers must adapt their Engagement Models:
● Faster deployment: Full deployment in weeks possible, Mobile grade user experience = less training
● More frequent innovation updates: Multiple innovation releases per year, Customer feedback a cornerstone of updates
● Agile deployment, con- figuration + integration: Rapid process configuration, Faster adoption, No lengthy upgrade
cycles § Packaged integration
● Lower CapEx & faster Time to Value: Lower initial solution and deployment fee, Lower maintenance or upgrade costs,
Prepackaged integrations
● Start with SAP’s Rich Best Practices + Fit-to-standard instead of traditional Business Blueprint + Build and Test =
Customer Value, Efficiency, Speed
4. Deploy SAP S/4HANA On-Premise with SAP Activate - Journey Overview and Key Milestones
128
1. Foster cloud mindset by adhering to Fit-to-Standard and Agile Deployment detailed in SAP Activate
Leverage SAP standard processes where possible and deploy your solution incrementally with short releases and sprints
2. Use pre-configured solutions with predefined processes and utilize SAP Fiori UX n SAP - Best Practices SAP Enterprise
Management Layer (*) and Partner templates*)
3. Use modern integration technologies
Use SAP Business Technology Platform (SAP BTP) functionality for Cloud integration n Use SAP API Business
Hub
4. Use modern extensions technologies
Develop customer extensions in a side-by-side approach using the SAP Business Technology Platform (SAP
BTP) n Follow SAP S/4HANA Cloud Extensibility Guide
Leverage business logic extensibility within in-app extensibility; avoid classic coding enhancements where
possible
5. Ensure transparency on deviations
Any deviation must be clearly documented as part of the implementation; this will help the customer replace
these with standard capabilities if they are offered in the future
Use standard capabilities of SAP Application Lifecycle Management tools to document the solution
7.2 Golden Rule 3 “Use modern integration technologies” - Integration Planning and Design
7.3 Golden Rule 4 “Use modern extensions technologies” - Extension Planning and Design
131
9. Enablers for Your Digital Transformation - SAP Activate Tools and Community
● Engage SAP Activate experts, Ask questions and collaborate, Stay up to date
SAP Roadmap Viewer:
● Access implementation guidance for your digital transformation, View and download SAP Activate methodology assets
and accelerators, Provide feedback to the Activate tea
133
● Access and download SAP Best Practices content, Power your project with ready-to-run business processes
134
Lesson 18: SAP S/4HANA Cloud, public edition
Contents:
J. SAP S/4HANA Cloud Overview and Why SaaS Cloud ERP from SAP?
K. SAP S/4HANA Cloud - Strategic choice to embrace the future of ERP and General Architecture
L. Multi - tenant view
M. Accelerate Time to Value with SAP S/4HANA Cloud Implementation Tools
N. Administration and Maintenance:
1. SAP S/4HANA Cloud, public edition delivery with SaaS, Responsibilities Move from Customers to SAP and
Landscape overview
2. Release Schedule
O. Security and Trust- Network Architecture
P. SAP extension strategy-cloud extensibility
Q. SAP Integration Strategy
R. Reporting and analytics - SAP analytics cloud
S.
A. SAP S/4HANA Cloud Overview and Why SaaS Cloud ERP from SAP?
B. SAP S/4HANA Cloud - Strategic choice to embrace the future of ERP and General Architecture
135
1) SAP S/4HANA Cloud, public edition delivery with SaaS, Responsibilities Move from Customers to SAP and Landscape
overview
137
● Governed by SAP
● Twice each year for three weeks
● Addition of new functionality and changes in SAP reference content only
● Reinvented and simplified automated testing for customers
Content Upgrade
G) Where to start???
144