S4 HANA CORE An Introduction to S4 HANA Digital Core Flashcards
Digital Core
Has core applications necessary to run an enterprise m
SAP Business suite
Originally developed to run on a large number of databases
- Ran on a technology platform called SAP NetWeaver
- Underlying application design was based around disk-based, row store and old hardware technology
SAP Business Suite can now run on SAP HANA
- Called Suite on HANA (SoH)
- Underlying ABAP code is optimized to improve performance – massive speed-up of performance of existing applications
- OLAP and OLTP together
- Supports real-time reporting on operational data
- Supports a new interface called SAP Fiori to medernize user experience
- Provides a digital platform to power new innovative applications
Key Features of S/4 HANA
- Inherits the native capabilities of SAP HANA
- Provides several deployment choices to the customer via Cloud Edition and On-Premise edition
- Comes with a new user experience called SAP Fiori which is easy to understand and can be accessed from any device
- Massive reduction in data footprint
Native HANA Capabilities
SAP S/4 HANA inherits the built-in capabilities of SAP HANA
- Application services
- Processing Services
- Integration Services
- Database Services
Application Services
- SAP HANA supports web application development in 2-tier model
- Since SAP HANA can handle the business logic as well as database services, application server is not required
Processing Services
- SAP HANA provides native in-memory processing engines that process any type of data (text, spatial, graphs, etc. ) in real time
Integration Services
- SAP HANA provides multiple data consumption options that can connect to any type of source
- Separate software for data cleansing and profiling are not required
Database Services
- SAP HANA is an in-memory column and row store database that can support both OLTP and OLAP applications
- Since all the processing and calculations on data can be done on the fly, the application code and core data model are simplified
SAP S/4 HANA has two editions
- On-Premise edition
- Cloud edition
SAP S/4 HANA on-premise edition
Installed in customer’s premise and all aspects of the software are maintained by the customer
- Customers can customize the system according to their requirements
- HANA Enterprise Cloud (HEC) is a special case of on-premise solution where the system is managed by a third party and the customers access HEC via internet
SAP S/4 HANA cloud edition
provides access to the SAP Business Cloud that contains
- SAP Data Center
- SAP Managed Operations
- SAP Support
Offers three different cloud deployment models
- Private Cloud (typically single-tenant)
- Public Cloud (multi-tenant)
- Hybrid Cloud
Choice of Deployment
- On-premise
- Cloud
Private Cloud (typically single-tenant)
- System is assigned to a dedicated customer, access via VPN (Virtual Private Network)
- System is owened by customer, operations and management by customer or 3rd party or both
- Can be operated on customer site as well as remote
Public Cloud (mult-tenant)
- One system is used by different customers
- Selfservice acces and tools
- Operated by Service Provider, not by customer
Hybrid Cloud
- System is a mixture of two or more deployment models
- Integrated by standardized or custom interface technology, supporting the transfer of data and transaction
Mixed environment or “On-premise and cloud”
Every mix of on-premise and cloud solution
SAP Cloud Company Powered by HANA
As a cloud company, SAP provides three different services
- SAP HANA Enterprise Cloud
- SAP HANA Cloud Platform
- SAP Cloud Apps
SAP HANA Enterprise Cloud - Private Managed Cloud
Run mission critical SAP applications in the cloud
SAP HANA Cloud Platform - PaaS
- Build New Cloud Apps
- Extend On-premise & Cloud Apps
- Integrate Everything
SAP Cloud Apps - SaaS
Apps like SuccessFactors
Data Footprint Reduction
Data footprint reduction achieved by
- Compressing all the tables in SAP HANA database
- By removing tables that were not required along with the indexes
- By implementing data ageeing strategies (hot and warm data)
- Since SAP HANA can aggregate on the fly there is no need to create and store aggregates
- Since SAP HANA uses column store tables, indexes are not needed
Three scenarios for transitioning to SAP S/4 HANA
- New Implementation
- System Conversion
- Landscape Transformation
New Implementation
New or existing SAP customer implementing a new SAP S/4HANA system with initial data load
System Conversion
Complete conversion of an existing SAP Business Suite system to SAP S/4 HANA
Landscape Transformation
Consolidation of current regional SAP Business Suite landscape into one global SAP S/4HANA system or selective data migration
SAP Activate
A combination of SAP best practices, tools and methodology to help customers simplify and accelerate the adoption of SAP HANA.
Main pillars
- SAP Best Practices
- Methdology
- Tools
4 Phases
(Discover) Prepare, Explore, Realize, and Deploy
