Technical Workshop Migration / Conversion to HANA and S/4HANA
Agenda HANA Technical Readiness Migration to Business Suite on HANA
S/4HANA Architecture and Conversion S/4HANA Finance S/4HANA Technical Innovations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
2
Technical Workshop HANA Technical Readiness
SAP HANA Backup & Recovery Overview of options B&R to file system
B&R to 3rd party backup tool
B&R using storage snapshots
Point in Time recovery
Point in Time recovery
Point in Time recovery
Check of physical consistency with header/trailer check sums
Check of physical consistency with header/trailer check sums
No check of physical consistency with header/trailer check sums
SAP HANA studio
SAP HANA studio
hdbsql
SAP HANA studio
hdbsql
Storage Tool
hdbsql
Create backup
SAP HANA Database
Create backup
Backup Storage, e.g. NFS
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Confirm storage snapshot
SAP HANA Database SAP HANA Database
3rd Party Backup Agent
Early option often with local or remote disk pools Follow-up work necessary to transport backup files to save location
Prepare database
3rd Party Backup Server
Most comfortable solution
SAP HANA has full control about B&R management
Data snapshot Data Area (Disk)
Create storage snapshot
External Storage
Very useful to create fast and adhoc backups in seconds to minutes Better combined with the other options to get check data for free External
4
SAP HANA Backup & Recovery Comparison of options
Advantages
File system
Backint
Storage snapshot
Consistency checks on block level
Consistency checks on block level
Fast
Ease of use – no explicit backup files management, integrated into Studio
Negligible network load
First storage partners offer integration in their tools
Data center integration Additional features, e.g. encryption or de-duplication Backups immediately available for recovery
Disadvantages
Additional storage required
Network load
File system fill level needs to be monitored
3rd
No consistency checks on block level
party backup tool necessary
Additional time needed to make backups available for recovery Network load In case of recoveries, backup files must be returned to staging area Size
Payload only
Payload only
~ Size data area, but usually compressed/deduplicated by storage
Duration
IO-bound (reading from data volume, writing to target)
IO-bound (reading from data volume)
Negligible (logical pointers are replicated)
Network-bound (writing to backup server)
Network-bound (writing to file system)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
5
SAP HANA Backup and Recovery Backint certification – certified tools Certification is an installation prerequisite for tools using the “Backint for SAP HANA” API See SAP Note 1730932 (Using backup tools with Backint)
Certified tools (as of 2015-09-01) Vendor
Backup tool
Support process (SAP Notes)
Allen Systems
ASG-Time Navigator 4.4
Commvault
Simpana 10.0, Hitachi Data Protection Suite 10 (via Simpana Backint interface)
1957450
EMC
Networker 8.2, Interface for Data Domain Boost 1.0
1999166, 1970559
HP
Data Protector 7.0, 8.1, 9.0; StoreOnce Plug-in for SAP HANA 1.0
IBM
Tivoli Storage Manager for Enterprise 6.4
1913500
Libelle
BusinessShadow 6.0.6 New
2212575
SEP
Sesam 4.4
2024234
Symantec
NetBackup 7.5
1913568
New
2212571
New
1970558
Online listing of certified tools: Application Development Partner Directory (enter the search term HANA-BRINT and click on a partner name ”SAP Certified Solutions” for further details) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
6
Ways to setup High Availability and Disaster Recovery Storage Replication
Cluster-like solution
Similar to classical shadow database solutions
Often already used by several customers
One data pool Includes Solution for HA with internal cluster manager Uses Storage Connector APIs for communication with environment
Ambivalent solution for HA & DR Automation possible with external cluster manager
Usual used for DR Automation possible with external cluster manager
Standby Server
Covers HW problems with additional host(s) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
(active, data pre-loaded)
Name Server
Index server
Index server
HANA database kernel
Internal Disks Data Disks
Transfer by
Name Server
Log Disks
Internal Disks Data Disks
Log Disks
Covers HW and data integrity problems with an additional set of individually driven data pools
OS: DNS, hostnames Secondary
Primary
(inactive) Name Server
Name Server
Name Server
Name Server
Name Server
Name Server
Index server
Index server
Index server
Index server
Index server
Index server
OS: Mounts Data Volumes
Data Volumes
Log Volume
Log Volume
Data Volumes
Data Volumes
Log Volume
Log Volume
HA Solution Partner
Secondary
(active)
Data Center 2
Data Center 1
Storage Mirroring
Name server
Server 3
Data Center OS: DNS, virt. hostnames, virt. IPs Primary
Application Servers
Clients
HA Solution Partner
Name server
Server 2
Application Servers
HA Solution Partner
Name server
Server 1
Clients
HA Solution Partner
Name server
SAN Storage
System Replication
Storage Connector API Storage Shared
Host Auto-Failover
Covers HW (data center) failures on a broader scale External
7
Ways to setup High Availability and Disaster Recovery Host Auto-Failover
System Replication
Storage Replication
Cluster-like solution
Similar to classical shadow database solutions
Often already used by several customers
Only single data center
Single or multiple data centers
Single or multiple data centers
Data Center
Data Center
Data Center
Data Center
Data Center
Async
Sync
Feature-set defined by SAP HANA
Feature-set defined by SAP HANA
Standby not pre-loaded
Shadow instances can be pre-loaded
Replacing often only parts (host or nodes) of a system © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Fast take-overs to prepared instances - min. performance ramp
Data Center
Possibilities defined by Storage partner tool features No pre-load
Whole system replaced/started fresh on alternative HW External
8
Ways to setup High Availability and Disaster Recovery Host Auto-Failover
System Replication
Storage Replication
Cluster-like solution
Similar to classical shadow database solutions
Often already used by several customers
Zero downtime maintenance SAP NetWeaver ABAP Server
Recently introduced HA/DR Provider Framework (SPS09) Failover groups for Dynamic Tiering (SPS10)
DBSL
Software Upgrade Order
virtual IP
SAP HANA Version
Settled solution
Connectivity Suspend
Walldorf
Primary
SAP HANA Version +1 Sync/Async mirrored redo log writing
Rot
Secondary
Driven by hardware and storage partners A lot of features and options available Certification for TDI not necessary, but success stories of customer projects With class. HANA appliances and . tailored datacenter integration
Transport incremental data Data
Log
Data
Log
A lot of features and increasing options © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
9
SAP HANA Administration and Monitoring Introduction Tools Overview – Status SPS11 The SAP HANA studio is both the central development environment and the main administration tool for the SAP HANA database. With SPS09 additionally a first version of the web-based tools SAP DB control center and SAP HANA cockpit are available for monitoring SAP HANA. They can also be used on mobile devices. Furthermore SAP HANA is fully integrated into SAP Solution Manager.
SAP DB Control Center Web-based tool for landscape monitoring of SAP databases
&
SAP HANA Cockpit Web-based tool to monitor individual SAP HANA databases
SAP HANA Studio Central development environment and main administration tool for SAP HANA, based on Eclipse
SAP HANA
SAP Solution Manager / DBA Cockpit Central tool to manage the SAP landscape, based on the SAP NetWeaver Application Server
SAP HANA also integrates with SAP Landscape and Virtualization Manager (LVM) for basic operation of larger/more complex SAP landscapes (start/stop & dependencies, etc.)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
10
SAP HANA Administration and Monitoring Introduction Tools Overview – Future Plan Following SAP’s cloud strategy, SAP HANA plans to offer web-based tools for monitoring and administration.
SAP DB Control Center Web-based tool for landscape monitoring of SAP databases
&
SAP HANA Cockpit Web-based tool to monitor individual SAP HANA databases
SAP HANA cockpit follows an alert-driven guided-procedure approach. A DBA will be enabled to drill-down to the root cause of an issue. It is planned to replace the administration perspective of HANA studio with SAP DB Control Center and SAP HANA cockpit in the long term.
.
SAP HANA
SAP Solution Manager / DBA Cockpit Central tool to manage the SAP landscape, based on the SAP NetWeaver Application Server
SAP HANA also integrates with SAP Landscape and Virtualization Manager (LVM) for basic operation of larger/more complex SAP landscapes (start/stop & dependencies, etc.)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
11
SAP HANA Administration and Monitoring SAP DB Control Center and SAP HANA Cockpit Overview
SAP DB Control Center Web-based tool for administration and monitoring of your landscape of SAP databases Theme for SPS09: Support thousands of SAP Databases in Data Center or Cloud
SAP HANA cockpit Web-based tool for administration and monitoring of a single SAP HANA database
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
12
SAP HANA Platform Ways to tackle data growth .Archiving
Memory Eviction
Tiered Data Storage
Application manages movement of data into some kind of archive (Suite ILM, BW NLS, …)
Unload “not so important” data from main memory
Offer data stores of different “priorities”
Active/non-active data (BW) Page-loadable columns (Suite)
SAP HANA
(Main Memory)
E.g. dynamic tiering Future: also Hadoop?
SAP HANA Hot Store
(Main Memory)
WarmStore (Disk)
SAP HANA
Archive store
But: do you really want to archive, or is it just a strategy for cost-evasion?
Data file
Process requires loading data into RAM Caching etc. lead to reduced but nonnegligible memory footprint
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
(Classical HANA)
(New DT Store)
Beginning of a journey Enterprise readiness Concept for data distribution, management, retrieval
External
13
SAP HANA Platform Ways to tackle data growth .Archiving
Memory Eviction
Tiered Data Storage
Application manages movement of data into some kind of archive (Suite ILM, BW NLS, …)
Unload “not so important” data from main memory
Offer data stores of different “priorities”
Active/non-active data (BW) Page-loadable columns (Suite)
SAP HANA
(Main Memory)
E.g. dynamic tiering Future: also Hadoop?
SAP HANA Hot Store
(Main Memory)
WarmStore (Disk)
SAP HANA
Archive store
But: do you really want to archive, or is it just a strategy for cost-evasion?
Data file
Process requires loading data into RAM Caching etc. lead to reduced but nonnegligible memory footprint
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
(Classical HANA)
(New DT Store)
Beginning of a journey Enterprise readiness Concept for data distribution, management, retrieval
External
14
SAP HANA Multitenant Database Containers Overview
System Database AS ABAP
App 1
App N
DB Schema
DB Schema
DB Schema
Tenant 1
Tenant 2
Tenant N
System DB
Shared HANA Hardware
System-wide parameter settings Complete backup of all databases Static resource management across all databases (CPU, memory, disk for specific database)
Tenant Database Multiple strictly separated database tenants on one HANA system Tenant specific life cycle management including backup/ restore Clear separation of application data and user management Local user management within each tenant-DB Session and transaction management per tenant-DB Move/copy of tenant-DBs to other systems/hosts
Future Roadmap: Support for cloud provisioning scenarios planned for delivery with next Steps
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
15
SAP HANA Persistence Startup in detail – possible optimization options
1.
Open Persistence files (Data Volume, Log Volume)
2.
Load RowStore • •
3.
•
•
Execution time depends a lot on size. Creation of secondary indexes happens decoupled after Restart (after 5.) Better thresholds for the size of LOBs moved into For HANA persistence RowStore is similar to a BLOB and finally opened logically on engine level Hybrid LOB structures
LOBs bigger than 1 Kbyte are usually extracted to HANA data volumes and organized via pointers as soon as this database was created since SPS07. Every ABAP text data type “string” is translated into a LOB on the database level. This produces effort to initialize this huge number of small LOBs during startup. With native applications you could try of utilize more data types next to LOB-like structures (varchar). Rollback information is located on Data Volumes, not Log Volumes (allows a consistent database recovery only with the help of a HANA data backup) Roll forward information (redo-log) is located on the online Log Volume First loads of columnar structures are executed as they are accessed to actually roll forward the log on them Next to roll forward also roll back operations can happen in this step if open transactions could not be finished before the database stopped. This is usually very fast, but in rare occasions we saw long running executions depending on the nature of these unfinished transactions. At the end of this redo-log operation the database is technically available – log-on possible Possible optimization 3:
Start loading columns marked with the preload flag
7.
Possible optimization 2:
Roll forward Log for Row and Columnar store • •
6.
RowStore size reduction – check following slide
Get open transactions to follow up on (Data Volumes) •
5.
Possible optimization 1:
Initialize Hybrid LOBs (can be millions especially with SoH)
4.
This and following steps are executed per HANA service individually Converter is loaded from the last successful Savepoint
Allows to load columns used by important business processes before the next step, if they are not already loaded by the roll-forward in the step before
Start loading tables from the list of lately used tables
Fast IO System - especially important for the steps 2., 6. and 7., but also good for the other steps
During the normal operation before the restart HANA tracks a list of tables which are currently loaded (once per day) This list is now the basis of loading the necessary tables into main memory
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
16
SAP HANA Persistence Startup in detail – Appendix Appendix to step 7:
1. Open Persistence Show info about list of tables to be preloaded (not the preload flag related columns): hdbcons „tablepreload i“
2a. Load RowStore
i: info – how many tables etc.
3. Initialize Hybrid LOBs
Show full content (list of tables): hdbcons „tablepreload c –f”
4. Get open transactions
c: content -f: full
Write additional preload info to virtual file inside data volumes: hdbcons „tablepreload w –s“ w: write -s: synchronous
5. Roll forward Redo Log Log-on 6. Load preload flag col.
2b. Create Sec. indexes on RowStore
7. Load tables loaded before restart
Full list of help: hdbcons help tablepreload
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
17
Technical Workshop Migration to Business Suite on HANA - Summary
SAP Business Suite powered by SAP HANA Recommendations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
19
SAP Business Suite powered by SAP HANA Recommendations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
20
SAP Business Suite powered by SAP HANA High-Level Implementation Considerations In this section, we want to explore the typical phases of an SAP Business Suite powered by SAP HANA implementation. Focus is on the PLAN and BUILD Phases.
Suite on HANA PLAN
Suite on HANA BUILD
Suite on HANA RUN
Value Discovery
Business Process Redesign/Optimization
SAP HANA Monitoring
System Prerequisites Technical Landscape Planning
Implementation Options
Custom Code Planning
Project Phases and Timelines
Operational Reporting (SAP HANA Live)
Resource Considerations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Data Center Readiness and Operations
External
21
Suite on HANA - PLAN System Prerequisites
System Prerequisites
SAP ERP 6.0 EHP7 is the recommended minimum release for SAP Suite on HANA
Min. Release Levels
SAP Business Suite on SAP HANA is based SAP NW AS ABAP 7.40
Not all SAP & 3rd party Add-Ons are currently supported
Not supporting dual-stack installations.
Check early: Table CVERS
Dual-stack systems must be split before migrating to HANA
Dual-Stack Systems © 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA runs natively on Unicode only
Unicode
Possible Restrictions External
22
SAP HANA Release Strategy Expect stability and predictability for your SAP HANA maintenance The newly introduced SAP HANA Datacenter Service Point (DC service point) provides SAP HANA customers with more guidance when and based on which SAP HANA Revision to plan their SAP HANA maintenance stack on.
As most customers have to plan their maintenance window between their quarterly end closings, the DC service point had been defined to be between the SAP HANA SPS, at the end of March and at the end of September. As prove of SAP’s commitment in its own software quality, the Revisions referenced by such DC service point will also be running in production enterprise applications at SAP for at least one week before they are finally released, assuring customers even more stability and predictability.
Recommended SAP HANA Datacenter Service Points for planned maintenance of SAP HANA 80 81
…. 73
….
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
74
74.xx …
…
90 91
83
…
85
92 …
??
85.xx …
Recommended revision update / patching path for key SAP HANA scenarios in production
External
23
SAP HANA Revision and Maintenance Strategy Summary Release of New SPS SAP HANA Revisions:
Datacenter Service Point
70 71 72
73
74
81 …
80
74.01
Zero Downtime SAP HANA Revision Update
74.02 74.xx
Revision Type
Schedule
Comprises of
Recommended to
RTC Revision
Every 6 months
New features and fixes
Early adapters and Non-production systems
DSP Revision
Every 6 months, Incremental fixes, after having run in SAP production system for based on latest SPS feature set 2+ weeks
Production systems (targeting planned maintenance)
Standard Revision
On demand
Incremental fixes, based on latest SPS feature set
Systems on DSP Revision and Non-production systems
Maintenance Revision
On demand, provisioned between RTC and DSP only
Incremental critical fixes only, based on predecessor SPS feature set
Production systems, (targeting unplanned maintenance)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
24
Suite on HANA - PLAN Technical Landscape Planning
Deployment, Installation and Sizing
On-premise or SAP Cloud powered by SAP HANA Scale-up: Increasing size of one server Scale-out: horizontally by adding servers Virtualization Multitenant Database Containers
Deployment Options
Multiple components on one database (MCOD): Deploy white-listed applications together on the same HANA DB Multiple components on one system (MCOS): Multiple SAP HANA databases on a single HANA system
Installation Options
See SAP Note 1514966 (SAP HANA: Sizing SAP In-Memory Database)
Switching to SAP HANA with DMO does not impact application servers or frontends
Sizing for New Installations: See http://service.sap.com/sizing
New SAP HANA DB HW is required, nothing else changes
ABAP sizing reports for migration to SAP HANA: SAP Business Suite: SAP Note 1872170
SAP HANA appliance runs on SUSE Linux (SLES) or Red Hat
Sizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Landscape Impact
External
25
SAP HANA Platform SAP HANA Technology Partners
SAP HANA Hardware Partners
Starting with HANA SPS08:
Linux on IBM POWER CPUs
1300+ certified appliance solutions (September 2015) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
26
SAP HANA Tailored Data Center Integration The concept
SAP HANA tailored data center integration is an additional option to the existing appliance delivery model Virtualization
Application Database
HANA HANA Server HANA Server Server
Operating System
HANA HANA Server HANA Server Server
Network Storage
SAP HANA appliance delivery © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Server certified
Virtualization Network
Server
Storage
defined
defined
Shared Network
Enterprise Storage
Storage certified
SAP HANA tailored data center integration External
27
Relaxed HW Specifications for Non-Production Notes: Hardware still from PAM or ICC o SAP Product Availability Matrix or http://scn.sap.com/docs/DO C-52522 Non-prod: Sizing flexible o Instances can be combined o SoH layouts can be used for BW
Processor
Intel Xeon E7 Westmere Ex (E7-x8xx v1) or IvyBridge EX (E7-x8xx V2)
Intel Xenon E5 - (E5-26xx v2/v3, min. 8 cores); 2 socket, up to 1.5TB; scale-up only Memory
Storage
128 GB of RAM to Maximum memory supported on the box Size: 2x Memory - Any local storage or shared storage w/ standard disk on proven file systems GPFS (IBM only), NFS or XFS w/ Raid 0 and above
Network
Operating System
Standard networking components
SUSE Linux 11.x or Red Hat 6.5
Virtualized or Bare Metal
Performance related support will only be provided on Production grade hardware (Certified hardware)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
28
SAP HANA scalability Scales from very small servers to very large clusters 12 PetaByte Data Warehouse with SAP HANA Guinness world record
Single Server
Scale Out Cluster
Cloud Deployment
•
•
2 to n servers per cluster
•
•
Each server is either 4 CPU/1TB or 8 CPU/3TB
SAP HANA instances can be deployed to AWS
•
Limited to developer license
•
Largest certified configuration: 112 servers
•
SAP HANA Enterprise Cloud
•
Largest tested configuration: 250+ servers
•
Support for high availability and disaster recovery
2 CPU 128GB to 8 CPU 3TB (Special layout for Suite on HANA for up to 12TB per host)
•
Single SAP HANA deployments for data marts or accelerators
•
Support for high availability and disaster recovery
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
29
SAP Business Suite powered by SAP HANA Scaling Suite on HANA
Scale-up (scale vertically) Increase the size of the hardware (main memory, number of CPUs) Challenge: availability of suitable hardware
Memory Size: 128 GB to 4 TB 12 TB will be available with Ivy-Bridge
Scale-out (scale horizontally) Several nodes (servers) are switched together for one database Data are distributed over the main memories of these different nodes
Challenge: – Cross-node communication is expensive
– Avoid cross-node joins / views – Table distribution has to be customer / usage pattern specific
Servers per Cluster: 2 to n
– Dynamic re-distribution must be allowed Controlled availability of Suite on HANA Scale-out started in Q3 2013 (Aug 13th) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
30
SAP Business Suite powered by SAP HANA – Scale-Out Controlled Availability and Outlook
Controlled availability of Suite on HANA Scale-out started in Q3 2013 (Aug 13th)
But: recommendation to scale-up memory by using a hardware configuration that maximizes available database memory
Current Limitations
In Business Suite systems with a HANA scale-out installation currently the local BW deployment option is not supported
Scenarios requiring a distribution of table partitions (e.g. single tables consuming more memory as provided by a single scale-out node) shall currently be avoided as it they will result in a weak overall system performance
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
31
SAP Business Suite powered by SAP HANA Sizing Typical Usage Case
Greenfield Sizing
• • •
Sizing based on an existing System
Expert sizing for existing system on HANA
• •
• • • • •
Black Box Sizing
Method/Tool
Prerequisite
HANA Rapid Prototyping New Implementation of Business Suite on HANA Standalone HANA
SAP Quick Sizer tool
Information about the (expected) data volume is available
Database migration of an existing Business Suite system to HANA SAP HANA Accelerators
A sizing report (see SAP Note 1872170) determines the overall database tables footprint for both row store and column store. Estimates the required memory for SAP HANA
SAP Business Suite system on AnyDB is already in place
Sizing verification New large or complex projects are planned Extraordinary use cases Define customer specific sizing guidelines
Combination of different approaches: • Workload analysis of existing HANA system • Analysis of sizing relevant input • Volume and load testing
Productive system on SAP HANA is already in place
Rough-estimates for the required HANA server size. Gives an initial indication
• See SAP Note 1793345 • Source_DB / 2 * 1.2 = approximated_HANA_DB
The source DB is uncompressed and Unicode. The source DB is well maintained.
For further details please refer to chapter Architecture → Sizing of HANA Deployment Best Practice. © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
32
SAP Business Suite powered by SAP HANA Sizing Report
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
33
SAP Business Suite powered by SAP HANA How to run the sizing report
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
34
SAP Business Suite powered by SAP HANA How to run the sizing report
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
35
Determine the right Building Blocks
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
36
Suite on HANA - PLAN Technical Landscape Planning – Updates 1/3
[Update Oct2015] VMware vSphere 6.0 with SAP HANA SPS 09 (or later) for non-production use cases •
Note that this is no guarantee for future production support, performance regressions do currently occur in specific test scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
37
Suite on HANA - PLAN Technical Landscape Planning – Updates 2/3 With SAP HANA 1.0 SPS09 the feature 'SAP HANA multitenant database containers' is introduced. The concept is based on having one single system with a system database that keeps the system-wide landscape information and which allows configuration and monitoring of the overall system. In addition there will be 0 to n tenant databases that are, with regards to application data and user management, strictly isolated from each other (except running on the same hardware in the same instance). All tenant databases can be backed up and recovered independently from one another. Note: All tenant databases are running with the same SAP HANA software version and the same HA/DR method. Q: Can we have SAP Business Suite and SAP BW combined on one SAP HANA system in separate tenants? A: It is supported to run SAP Business Suite and SAP BW on the same production SAP HANA system. An additive sizing approach is needed: perform a sizing estimation for each and then add them together (and avoid underestimating). For CPU core and memory ratio aspects, the features for allocating memory and influencing CPU core utilization per tenant can be utilized. © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
38
Suite on HANA - PLAN Technical Landscape Planning – Updates 3/3 Multitenant Database Containers vs. Virtualization Multitenant Database Containers
Lower TCO, single software stack Central configuration & administration (database level) Direct database resource management Optimized federation (performance benefits) Performance advantages (no virtualization overhead) Licensed via SAP HANA
Virtualization
HANA SystemDB
Strong isolation Separate SAP HANA revisions option Standard federation (SDA) Additional virtualization license (e.g. VMWARE)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
OS
HANA Tenant
VM+OS
VM+OS
HANA
HANA
VM+OS
VM+OS
HANA
HANA
External
39
SAP HANA Virtualization & Multi-tenancy Options Horizontal View
One Schema per DB
Multiple Schemas
One or more SAP HANA Databases
One SAP HANA Database (whitelisted scenarios)
App
App
Schema Schema
Multiple tenant databases One HANA Instance
App X
App Y
App X
App Y
App X
App Y
Schema X
Schema Y
Schema X
Schema Y
Schema X
Schema Y
Database SAP HANA Instance SAP HANA Instance
Multiple SAP HANA instances on one SAP HANA virtualized HW appliance (e.g., VMware)
Database SAP HANA Instance
Database
Database
SAP HANA Instance
SAP HANA Instance
OS
OS
Tenant DB
Tenant DB
SAP HANA Instance
OS
OS
Hypervisor
OS
HW
HW
HW
HW
SAP Note 1681092 for MCOS approval with HANA SPS09
See Notes 1661202
See SAP Note 1788665
See SAP Note 2096000
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
+ 1826100
External
40
Technical Upgrade - Plan JAVA Stack upgrade options Split ABAP+JAVA dual stack systems is a prerequisite to upgrade to SAP Netweaver 7.40. Once the ABAP and JAVA stacks are split, there are 2 main options to upgrade the JAVA stack to SAP Netweaver 7.40 on HANA 1.
Perform an upgrade to SAP Netweaver 7.40 using SUM and then perform a export/import to HANA using SAP SWPM tool.
2.
Perform a new and empty SAP Netweaver 7.40 JAVA on HANA and transport all the customer developments from the old JAVA stack to the new JAVA stack on HANA.
Option 1: Upgrade+Migration (2 steps) AS JAVA 7.0x
AnyDB
upgrade
AS JAVA 7.40
AnyDB
optional
Option 2: Fresh install
AS JAVA 7.40
AS JAVA 7.0x
HANA
AnyDB
HANA or ANYDB
Delete
Fresh Install
Transport custom objects
AS JAVA 7.40
Customers which use the BW JAVA Stack only for BEx Web don’t need to upgrade the JAVA stack as the JAVA stack contains no business data and is only used to render the BEx pages. Instead, it will be much faster and clean to use option 2, install a new AS JAVA 7.40 on HANA and re-import again the custom developments (if any).
1645590 - Java/Server SPs dependencies (and SupportDeskTool) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
41
System Landscape Interoperability Background (SAP Note 1388258)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
42
Suite on HANA - PLAN Custom Code Planning
Custom Code Planning
Is any of my custom ABAP code likely to cause issues with SAP HANA?
Which of my custom ABAP code shall be optimized to ensure good performance?
Which of my main businesses processes could potentially be massively sped up by SAP HANA?
Main Questions to Answer
In general, existing ABAP code runs on SAP HANA as before
Analyze your existing code before migration: Typically this consists of 3 parts: -
Code Analysis: SAP HANA code compliance checks. SAP Code Inspector tool (SCI)
-
Usage Analysis: Identify critical custom code. Usage and Procedure Logging tool (UPL)
-
Define Master Work List: Prioritized list of coding . SQL Performance Worklist tool (SWLT)
Services available to assist with custom code assessments, migrations and optimizations
SAP Note 1912445 - ABAP custom code migration for SAP HANA – Best Practices
Guidelines – How to Accomplish © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
43
HANA Readiness Check for Custom Code Code Analysis
Usage Analysis
Master List
Identify potentially affected custom code
Identify critical custom code Identify unused code
Create master work list containing a prioritized list of affected custom code
Tools
Tools
Code Inspector (DEV / Sandbox) Remote Check if necessary
UPL (PROD) SQLM (PROD) SQL Performance Tuning Work List
Issues identified
Relevant Issues
performance issues
compatibility issues
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
44
SAP Business Suite powered by SAP HANA Custom Code Adjustments and Optimization: Migration Preparation Activities There is no need to adapt all objects, focus on the most critical based on usage and impact. 1. Capture the Custom Code Footprint using Custom Development Management Cockpit (CDMC) or the Custom Code Lifecycle Management (CCLM)
1
2 3 4 Total Footprint
Used Objects
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Impacted Objects
Critical Objects
2. Reduce the scope to those objects that are used by leveraging Usage Procedure Logging (UPL) and ABAP SQL Monitoring (SQLM) 3. Identify the impacted objects using CDMC, Code Inspector, and ABAP Test Cockpit (ATC) 4. Focus on those objects that are critical for the business, and those with the most optimization potential External
45
Custom code optimization for HANA Tools overview and Usage scenario
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
46
Custom code optimization for HANA Tools overview and Usage scenario
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
47
Suite on HANA - BUILD Business Process Redesign and Optimization
500+ Accelerated Standard Transactions See SAP Note 1761546 (SAP ERP powered by SAP HANA – Optimizations
Accelerated Transactions
Execute Online Analytical Processing (OLAP) and Online Transactional Processing (OLTP) on one platform
Real-Time Analytics
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
23+ Core Business Value Scenarios delivering business process improvements Examples: Accelerated Financial Close, Accelerated MRP See Additional Resources: Suite on HANA Factbooks
Optimized Processes
Based on SAP Business Suite Data
Enable new, specialized applications for specific business domains
Examples: Working Capital Analytics, Invoice and Goods Reconciliation, SAP Supply Chain Info Center
New Applications
External
48
Suite on HANA - BUILD Optimizations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
49
Suite on HANA - BUILD Implementation Options
Option A New Installation
SAP System Traditional DB
You install new system on SAP HANA Greenfield: Creation of a completely new business system landscape. It is normally a much larger project Transformation: Transforming existing solution to SAP HANA by performing (selective) data migration
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Option B Classical Migration
Option C One-step Upgrade & Migration with DMO
Migration
To bring the original system on Release supported by SAP HANA, you perform update/upgrade (if required)
You use database migration option (DMO) that combines upgrade and database migration in one step
One process, one tool, one downtime
Then, you classically migrate your traditional database to SAP HANA
External
50
Migration options & tools
A New installation for transformation 1. Overview Address solution landscape changes by transformation with SAP Landscape Transformation software
– With reduced effort to build targeted landscape
– Such as via shell creation with carve-out + system consolidation for ABAP systems
App data Repository
Repository
Any DB
Any DB
+
Complemented by transformation services
– Such as Data Management Services or System Landscape Optimization services
Repository
Value proposition Provides opportunity to correct design issues as part of migration
– System consolidation, data harmonization (chart of account, master data) Leveraged flexibility by offering selective migration
– Migrate only specific data without business disruption (such as of last 2 years) – Combine data cleansing – leave unused master data behind – Smoothly introduce new business processes (such as new general ledger) Minimized downtime services available (such as NZDT)
To be considered
For more information: • http://service.sap.com/sapLT • Contact:
[email protected], subject: HANA
Project solution (addressed by services), ABAP only © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
51
Migration options & tools
B Classical migration: overview 2. Overview Phased approach: you perform upgrade (if required) + heterogeneous system copy with classical procedures Either in-place (DB migration) or combined with change of platform/hardware replacement (OS/DB migration)
Value proposition
Results in nearly identical system SAP Minimal impact on functional teams System Separation of concerns Supported for all product versions in maintenance, supports SAP ABAP and Java systems (only migration option for Java!)
Any DB
1
Upgrade
2
Migrate
1:1
To be considered With inclusion of upgrade, fallback to original state only possible via restore Typically implies extended downtime and several downtime windows – depending on size of database and required scope (Unicode conversion, SAP system upgrade, DB update, migration) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
52
Migration options & tools
C One-step upgrade and migration with DMO of SUM – overview 3.
SAP System
Any DB
Prepare
Update/Upgrade
Migrate
Database Migration Option (DMO) of Software Update Manager (SUM)
Overview Relevant steps in one tool and one process Supported for migration of SAP ABAP systems to SAP HANA only
Value proposition (also see next slides) Manual effort and error-proneness reduced, only intermediate fallback effort Downtime optimized (depending on scenario), only one downtime window
To be considered “Big bang” approach ABAP only © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
53
Migration to HANA DMO supported versions (ERP) – SPS16
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
54
Migration to HANA DMO supported versions (ERP) - Implications
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
55
Migration options & tools
C One-step upgrade and migration with DMO of SUM – phases during procedure 3. Any DB
1 2
Upgrade “Prepare”
Setup SAP HANA specifics (client, schema …)
Execute upgrade
Uptime
(until downtime phase)
Switch
3 database
Note Traditional database continues to run, but is no longer used to store data
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
connection
Downtime
4
Migrate application data
5
Finalize upgrade
6
Start SAP HANA-based system
(incl. data conversion)
External
56
System considerations – what changes and what doesn’t C Migration of database server only + benefits
Frontends
No Change
Migration of database to SAP HANA appliance required Co-deployment of application servers (e.g. central instances) on database hardware not possible with SAP HANA
Application Servers AnyOS
No change of frontends Re-use of available application servers Sizing of current application servers remains valid
Change
AnyDB/ AnyOS
SAP HANA migration
SAP HANA/ SUSE Linux (SLES)
No Functional Changes: IMG, Customization, Modifications, Connectivity, Security, Transports, Monitoring (DBACockpit & SolMa) stay all the same
Application and Reporting Benefits: No dialog process in batch, acceleration/elimination of batch, Run operational reports in realtime inside Suite © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
57
Migration to HANA DMO supported versions (ERP) - Implications Recommended path for two-step approach: go to ERP 6.0 EPH7 on HANA As discussed above, a two-step approach is required: for non-UC systems and for R/3 4.7 & SAP ECC 5.0 Recommendation: • first step to for SAP ECC 6.0 EHP 7 on HANA (6.17 oH) with SUM w/ DMO • second step later then with SUM (w/o DMO) to SAP S/4HANA 1511 ff Exception: DMO not supported for R/3 4.7: • use SUM (w/o DMO) to 6.17 on sourceDB • later SUM w/ DMO to SAP S/4HANA Alternative for SAP ECC 6.0 EHP 0...7 on anyDB: • You may only do the Unicode Conversion without update & migration (stay on software level) • Benefit: no change of business processes, so project effort may be reduced • Disadvantage: you need additional hardware to support a parallel DB export/import to minimize the Unicode conversion downtime, which would not be required for SUM w/ DMO Discussion: • Targeting 6.17 oH as first step is a handy general rule, although exeption exist • Targeting EHP8 not possible, it is based on 7.50 => requires UC source system • Targeting "sFIN" 1503 (based on 7.40) as first step would technically be possible as well, but not targeting "sFIN" 1602 next year (based on 7.50: UC required) - awkwardly and not easy to explain
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
58
Migration to HANA Overview on Downtime Optimization 1) "Classical" SUM Maintenance: • nZDM is an option (in preconfiguration mode Advanced) • update some application tables during uptime • not possible with DMO 2) "Classical" DMO: • SHD REP is created and migrated during uptime • application tables are migrated during downtime
3) "downtime optimized" DMO (DMO/SLT): • migrate some application tables during uptime Downtime Optimization for DMO is currently available on request
4) ZDO / ZDM • Zero Downtime Option / Zero Downtime Maintenance • not possible with DMO 5) nZDT • Service from SLO, add. costs © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
59
SAP DMO for SUM How to migrate the SAP Application Servers to a new hardware / operating system SAP DMO for SUM is an in-place migration procedure, the SAP Kernel running in th SAP Application Server will be migrated from SAP Netweaver 7.x Oracle to SAP Netweaver 7.40 HANA as part of the DMO process:
Initial state
Tasks executed by the SAP DMO for SUM
SAP NW 7.x Oracle
SAP NW 7.x Oracle
Oracle 11g
Oracle 11g
Win 2008
Win 2008
SAP NW 7.40 Oracle
Step1
Oracle 11g
HANA
Linux
Connect the SAP Application Server with the SAP HANA Appliance
Win 2008
Step2 HANA
Linux
DMO install a new SAP SHADOW Instance based on SAP Kernel 7.40 Oracle to perform the upgrade
Final state SAP NW 7.40 HANA Oracle 11g
Win 2008
SAP NW 7.40 HANA HANA
Linux
DMO changes the Kernel from SAP NW 7.20 Oracle to SAP NW 7.40 HANA and migrate the DB contents from Oracle to HANA
Oracle 11g
Win 2008
SAP NW 7.40 HANA HANA
Linux
HANA
Win 2008
Linux
Oracle DB is still there but can be removed manually, the SAP Kernel running in the SAP Application Server is connected to HANA.
By default, during the DMO Process it’s not possible to install a new SAP Application running on a different server.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
60
SAP DMO for SUM How to migrate the SAP Application Servers to a new hardware / operating system As part of the migration process, Customer XYZ wants to install new SAP Application Servers, replacing the old hardware with new servers (and optionally replacing Windows Server 2008 R2 x64 with Windows Server 2012 R2 x64).
As this is not possible by default, the proposed approach is to perform standard DMO process and perform the manual installation of the new SAP Application Servers after the DMO process: Initial state
Tasks executed by the SAP DMO for SUM
SAP NW 7.x Oracle
SAP NW 7.x Oracle
Oracle 11g
Oracle 11g
Win 2008
Win 2008
SAP NW 7.40 Oracle
Step1
Oracle 11g
HANA
Linux
Connect the SAP Application Server with the SAP HANA Appliance
Win 2008
Step2 HANA
Linux
DMO install a new SAP SHADOW Instance based on SAP Kernel 7.40 Oracle to perform the upgrade
Final state SAP NW 7.40 HANA Oracle 11g
Win 2008
SAP NW 7.40 HANA HANA
Linux
DMO changes the Kernel from SAP NW 7.20 Oracle to SAP NW 7.40 HANA and migrate the DB contents from Oracle to HANA
Oracle 11g
Win 2008
SAP NW 7.40 HANA HANA
Linux
Oracle DB is still there but can be removed manually, the SAP Kernel running in the SAP Application Server is connected to HANA.
HANA
Win 2008
Linux
SAP NW 7.40 HANA
Win 2012 Install a new SAP Primary Application Server in a new hardware. Delete old Application Server
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
61
SAP DMO for SUM How to migrate the SAP Application Servers to a new hardware / operating system
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
62
SAP DMO for SUM SP15 News and last updates
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
63
Downtime optimized DMO (1/2) Regular DMO •
Repository migrated during uptime, other tables during downtime (both via R3load)
Downtime optimized DMO (based on DMIS AddOn) •
Reduce downtime by migrating selected application tables already during uptime
•
Change recording and replay for these tables
•
Available on request, see blog http://scn.sap.com/community/it-management/alm/software-logistics/blog/2014/09/08/dmodowntime-optimization-by-migrating-app-tables-during-uptime-preview
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
64
Downtime optimized DMO (2/2) PAS Host
Uptime
PRD Instance
0) SHD REP was created & copied to target
PAS
Source Kernel
SHD Instance
2
DMIS Reader
SHD Kernel R3load
1
1) Initial transfer of triggered tables
3
4
TMP Instance DMIS Writer
TGT Kernel R3load
2) Delta transfer of triggered tables Downtime 3) Remaining Delta transfer of triggered tables 4) Non-triggered application tables are migrated -> DMO cont’d (kernel switch, app data update)
PRD REP
0 TGT REP
SHD REP Application Data Source DB Host © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Application Data SAP HANA DB Host External
65
Table comparison in DMO Content checks for selected tables of source & target database (using cyclic redundancy checksums) •
Generates checksums for e. g. every 10000 rows on source and target side and compare
•
Dig deeper where checksums do not match until conflicting rows are found
•
Stop after discovering more than e. g. 200 differences -> points to systematic errors
•
Checking happens in parallel for multiple tables / one table via table splits
•
Checking all tables only for test systems due to performance load
•
Only for application tables, repository tables not allowed
•
Runs during downtime -> configuring downtime processes
Will be made available as standalone table checker, e.g. for checks during classical migration
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
66
Choosing the right option Standard recommendation – ABAP systems General Recommendation
Reasonable Alternative
Possible Exception
DMO of SUM is the standard procedure for migrations to SAP HANA – profit from a simplified migration to SAP HANA with minimized overall project costs!
Classical migration If DMO of SUM does not fit your requirements, consider to use classical migration with software provisioning manager (continuously improved for this migration use case)
New installation for transformation In addition, there are further migration procedures for special use cases, such as system consolidation or carve-out with SLO Shell Creation
Use as starting point for your individual assessment © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
67
Suite on HANA - BUILD Project Phase and Timelines (1 of 2)
Effort, Time and Risk Influencers
How well the test scripts are defined prior to testing General testing and approval requirements of the organization
Testing Protocol
.
#leverages of custom objects influences both CAM SAP-internal systems (e.g. ISP, CRM)the to create a consistent view on&HANA SAP ERP EhP update effort project information. It runs as one of the first needed to recognize full benefit of productive systems in the Hana Enterprise the SAP HANA database (custom Cloud.
Number of Systems/DB Size
objects need to be evaluated for code optimization)
Level of Customization
The number of CPUs and the amount of memory are fundamental items affecting the time required for tasks and the costs of hardware
Hardware Specifications
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Number of Systems and Size of the overall database (impacts initial hardware costs as well as operational costs & time required for many technical and functional steps)
Current application release may require an EhP upgrade, which may introduce additional steps (e.g. regression testing).
System Release Level
Bandwidth influences the data transfer rate between systems
Network Bandwidth
The size of these tables influences the time required for converting the tables into transparent tables
Pool & Cluster Tables
Evaluate SAP and 3rd party addons prior to the migration. SAP recommends 3rd party add-ons to be certified for SAP HANA. See appendix for details
Interfaces & Add-ons
HANA skills and experience of key project team members impact the project schedule and efficiency of completing many tasks
Project Team Expertise
External
68
Suite on HANA - BUILD Project Phase and Timelines – Example (2 of 2) Implementation Timelines for Suite on HANA projects will range from 3 – 12+ months SoH Implementation: Migration Example Preparation
Key Phases and Activtities Preparation
Value Discovery: Identify and quantify the value potential for business processes HANA Assessment Hardware Order/Delivery/Setup and Installation (or Deployment in the Cloud)
Update/Upgrade SAP Business Suite Components (duration depending on current state)
Update Suite
Dual Stack Split Unicode Conversion Upgrade/Update to Latest EHP for Suite on HANA
Migration (duration depending on number of systems and migration cycles etc.)
Migration
Heterogeneous System Copy / Migration Cycles (SBX, DEV, QA, PROD, Dress Rehearsal, Cutover) Migration Post Steps
SAP HANA Adoption
HANA Adoption
Custom Code Migration Custom Code Optimization, Enable Business Functions
Go-Live
Go-Live
Go Live Education
Quality Assurance
Testing
HANA Operations
HANA Operations
Project Management © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Project Management External
69
Suite on HANA - BUILD Resource Considerations – Key Roles and Activities Key SAP Roles
Responsibilities: New Implementation
Responsibilities: Upgrade & Migration Project
SAP Business Suite Line of Business Consultant (ERP, CRM, SCM…)
• • • •
Business Process Evaluation Functional Design Functional Configuration Functional Testing
• • •
Business Process Evaluation Solution Planning Functional Testing
Technical Architect
•
System landscape and data volume optimization before migrating to HANA
•
System landscape and data volume optimization before migrating to HANA
Technical Consultant (Platform Architects, OS/DB Subject Matter Experts)
• •
Suite Installation / EHP upgrade Installing, upgrading, and administrating SAP HANA
• • •
EHP upgrade OS/DB Migration Installing, upgrading, and administrating SAP HANA
Development Consultant (ABAP SME)
•
Creating new custom reports and transactions optimized to run on HANA
•
Assess and optimize existing custom reports and ABAP code to run on SAP HANA
Reporting/Analytics Consultant
• •
Customizing SAP HANA Live Data Models Modifying or creating new reports on top of the HANA Live Data Models
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
70
Project planning aspects Example of project plan for classical migration Migration Execution Cycle 1 PRD to SAP HANA “Sandbox” Source / Target P01 Copy P01 HW Purpose Test upgrade and migration steps with copy from production Create upgrade / migration cookbook Execute multiple technical iterations to familiarize with process Note Perform ABAP code analysis, housekeeping before the migration
Cycle 2 DEV to SAP HANA DEV
Cycle 3 QA to SAP HANA QA
Cycle 4
Cycle 5
PRD to SAP HANA “Sandbox”
PRD to SAP HANA “Sandbox”
Source / Target D01 DH1
Source / Target Q01 QH1
Source / Target P01 Copy P01 HW
Source / Target P01 Copy P01 HW
Purpose Establish SAP HANA dev environment (DH1) Refine cookbook
Purpose Establish SAP HANA QA environment (QH1) Enhance cookbook Testing environment:
Purpose Mock cutover Optimize/verify E2E business downtime Finalize cookbook Finalize cutover plan Testing environment:
Purpose Final dress rehearsal Validate E2E business downtime Validate final cookbook Validate cutover plan
Note Upgrade & migration steps will differ from production Perform mandatory code adaptations and simple code optimizations
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
− − − −
Integration Functional regression Operational readiness User acceptance
− Infrastructure testing − Post-cutover operational performance testing
Cycle 6 PRD Migration Source / Target P01 P01 Purpose Establish new SAP HANA PRD env Utilize downtimeminimized approach
Note Execute end-to-end business downtime precisely as defined within cutover plan Execute technical steps precisely as defined in cookbook Plan code optimization projects External
71
Project planning aspects Example of project plan for classical migration (minimized freeze period)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
72
Project planning aspects Alternatives
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
73
Migration Facts
Key Facts
System Size / HANA Size
1st system productive since April 2013 No cancellation of the migration project The shortest downtime is 2h Sole mandatory change to customer ABAP code ‘order-by’ statement 100+ partners active
Migration Times
Installations
Comparable to sole EHP update No project delays due to DB migration
42 % New Install 58% Install Base
© 2014 SE ororan affiliate company. All rights reserved. SAP SEAG anSAP SAP affiliate company. All rights reserved. © 2015 2014SAP SAP or an SAP affiliate company. All rights reserved.
256GB – 14% 512GB – 42% 1TB – 18% 2TB – 14% 4TB – 7% 8TB – 5%
Project Duration
Public External
74 74
SAP Business Suite powered by SAP HANA Migration 1% 8%
17%
32%
3 weeks
74% of customer
3 month
migration projects took less than 6 month
6 month
4 month 5 month 8 month 9-12 month
17% 14% 11%
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
75
SAP Business Suite powered by SAP HANA Customer projects Project duration
Duration from project start to go-live (in months)
Duration from contract to go-live (in months)
Status: May 2014 © 2014 SAP SE or an SAP affiliate company. All rights reserved.
76
SAP Business Suite on SAP HANA Lessons Learned
1
Conduct a thorough Technical Assessment as part of the Planning Phase
4
2
Leave room in the Plan for Custom Code Assessment and Optimizations and start this early
Identify Critical Business Transactions and high value Business Scenarios early in the project phase together with business
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
3
Ensure SAP Solution Manager system is up to date (Latest Version and SP Stack), connected and integrated
Leverage experienced SAP HANA Technical Resources (certified OS/DB migration experts) and ABAP for SAP HANA Resources
External
77
Technical Workshop S4/HANA architecture and conversion approach
High Level Overview of SAP Financial Solutions on HANA 2011
Side Car Solutions – Secondary Database Suite on HANA – Primary Database
Simple Finance / S4HANA
Today / Future © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Increased Performance
Increased Usability / Visualization Reduction in Footprint
External
79
High Level Stack Architecture – Cloud & On-Premise SAP S/4HANA Architecture differs from the classical Business Suite architecture – compatibility is build in
Fiori Shell Fiori Apps, ALV (UI5)
Design Studio Analysis App
Search
Data structures (Compatibility provided through Core Data Services)
Application engines UI layer (Launchpad / Fiori)
OData
SAP S/4HANA ABAP
R
lnA
R
lnA
R
Gateway R
R
(WinGUI still available for compatibility reasons) Transactional Logic R
HANA
Analytic Engine R
(Enterprise-)Search R
CDS View
Suite Tables
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
80
Example of dramatic simplification: invoice posting Before Customer
Supplier
General Ledger
KNA1
LFA1
SKA1
After Customer
Supplier
General Ledger
KNA1
LFA1
SKA1
KNC1
LFC1
GLT0
COSS COBK
COEP COSP
KNC1
LFC1
GLT0
BSIS BKPF
BSID
BSET
BSIK
BSAK
BSEG BSAS
14 tables, 3 primary indices, numerous secondary indices, 10 inserts, 5 subtotals
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
BSAD
Virtualized Compatibility Views
BKPF
BSEG
5 tables, 3 primary indices, 4 inserts. Secondary indices and subtotals are virtualized with compatibility views
External
81
Investment Protection Non Disruptive with Compatibility Views
Program Reading Aggregate
Program Reading Aggregate
Compatibility views calculate on the fly
Aggregate / Index Aggregate Aggregate
Header
SAP HANA
Item
Virtual Tables
DB Tables
Suite on HANA © 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP S/4HANA External
82
Summary Key Take Aways Text Mining
Analytics & Prediction
SAP Simple Finance
NEW DEVELOPMENTS
Decision Support
Simulation
SAP Simple Logistics
NATIVE HANA CAPABILITIES
USER EXPERIENCE SAP S/4HANA On-Premise Edition
SAP S/4HANA Cloud Edition
CHOICE OF DEPLOYMENT © 2015 SAP SE or an SAP affiliate company. All rights reserved.
TECHNICAL INNOVATION External
83
Deployment Options One Codeline, Different Products Following the “principle of one”, SAP S/4HANA will offer all main features* in different deployment options
SAP S/4HANA
Development
S/4HANA
On-premise Edition Dev. Consolidation
SAP S/4HANA Cloud Edition
Selected corrections
Classical Suite
Business Suite
*Detailed product features may differ in different deployment options
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
84
SAP S/4HANA Release Strategy
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
85
SAP S/4HANA Enterprise Management, on-premise edition 1511 Why Compatibility Pack?
Transformation
ERP
SAP S/4HANA Enterprise Management
Compatibility Pack Scope**
LoB & Industry Engines
SAP S/4HANA ready Lob & Industry solutions
Compatibility Pack Scope**
on-premise edition 1511
on-premise edition xx11
No functional equivalent SAP S/4HANA ready LoB & Industry solutions Reduced Compatibility Pack Scope**
Customer Project
New SAP S/4HANA Solution SAP S/4HANA Enterprise Management
Merged with another SAP S/4HANA solution Allows customers to continue using classical functionality as they are being simplified by development ** Scope may include commercialized solutions or noncommercialized components
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
86
SAP S/4HANA Enterprise Management, on-premise edition 1511 Compatibility Pack Definition KEY MESSAGE “Compatibility Packs” allow the use of certain “non SAP S/4HANA” SAP functionality, for a specified period of time, in a licensed SAP S/4HANA installation, provided the customer has [or acquires] licenses to such solutions from the classical SAP price list
Classical ERP Scope + LoB and Industry solutions
SAP S/4HANA On-Premise Scope Compatibility Scope
1. “Compatibility Packs” fill the gap between the capabilities of today's classical portfolio and the capabilities of the SAP S/4HANA, on-premise edition 1511. Over time, the compatibility packs will be phased out, as the scope of SAP S/4HANA on-premise edition 1511 increases 2. Only “Non-SAP S/4HANA” functionality included in the “compatibility pack 1” is available for the SAP S/4HANA on-premise edition 1511 Installation
3. Compatibility packs are implemented via legal language in SUR - there are no material codes for it 4. Customers must have [ or acquire] licenses of the non-S/4HANA solutions from the classical price list. The current documentation of the nonSAP S/4HANA solution applies. 5. Non-SAP S/4HANA solutions have the same restrictions as any other SAP S/4HANA applications when used in an SAP S/4HANA installat ion. Note: the same classical solution can also be deployed on a non-SAP S/4HANA installation where SAP S/4HANA restrictions do not apply 6. Compatibility Packs are only available for a period of 5 years 1
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Usage of compatibility packs for SAP S/4HANA is individually regulated by contract.
External
87
SAP S/4HANA Enterprise Management, on-premise edition 1511 Compatibility Scope Matrix Classical Solutions Name
SAP S/4HANA Compatibility Pack Solutions*
SAP Learning Solution
CP-SAP Learning Solution
SAP Enterprise Learning Environment
CP-SAP Enterprise Learning Environment
SAP EHS Management: product and REACH compliance (DI)
CP-SAP EHS Management: product and REACH compliance (DI)
SAP Financial Closing cockpit
CP-SAP Financial Closing cockpit
SAP EHS Management, product safety
CP-SAP EHS Management, product safety
SAP Knowledge Acceleration Bundle for ERP
CP-SAP Knowledge Acceleration Bundle for ERP
SAP Learning Solution, option for the extended learning community
CP-SAP Learning Solution, option for the extended learning community
SAP Collaborative Finance Operations, receivables management
CP-SAP Collaborative Finance Operations, receivables management
SAP Commercial Project Management, option for workspaces
CP-SAP Commercial Project Management, option for workspaces
SAP Commercial Project Management, option for cost and revenue planning
CP-SAP Commercial Project Management, option for cost and revenue planning
SAP Commercial Project Management, opt. for issue and change manag.
CP-SAP Commercial Project Management, opt. for issue and change manag.
SAP Payroll Processing
CP-SAP Payroll Processing
SAP Shared Service Framework, Human Resources
CP-SAP Shared Service Framework, Human Resources
SAP Capital Yield Tax Mgmt, international version
CP-SAP Capital Yield Tax Mgmt, international version
SAP Capital Yield Tax Mgmt, version for Germany / Switzerland
CP-SAP Capital Yield Tax Mgmt, version for Germany / Switzerland
SAP ERP Foundation Starter
CP-SAP ERP Foundation Starter**
* SAP S/4HANA Enterprise Management, SAP S/4HANA Enterprise Management for ERP, or SAP S/4HANA Foundation-Promotion is a prerequisite of any SAP S/4HANA Compatibility Pack Solution. Provided Licensee has a license for one of the prerequisites set forth in the preceding sentence, and if Licensee also has a license to a Classical Solution shown under the Classical Solutions column above, they shall automatically also have a license for the corresponding compatibility pack solution shown in the SAP S/4HANA Compatibility Pack Solutions column above, in accordance with the terms of their Agreement referencing this Matrix. ** CP-SAP ERP Foundation Starter does not contain all of the functionality of the corresponding Classical Solution.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
(Expiration Date: Dezember 31, 2020: This is the current state of planning and may be changed by SAP at any time.)
External
88
Custom Code Refactoring An end-to-end view in system conversion scenario HANA compatibility
Access to obsolete tables INSERT, UPDATE, DELETE, MODIFY
Native SQL, db hints UNICODE
ECC on Any DB
SoH
pure refactoring HANA performance
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Custom code dependent on deprecated / changed components
sFIN (Add-On), On Premise
functional substitution & refactoring
Zero modifications, “Whitelist APIs” only
S/4 HANA v.1511, On Premise
S/4HANA Cloud
clean-up & functional substitution & refactoring
S/4 performance
External
89
SAP S/4HANA: The Customer Has The Choice SAP S/4HANA On-Premise Edition
Traditional licensing with customer control of deployment and maintenance
SAP S/4HANA on-Premise is already available with the combination of Suite on HANA with an exchange innovation add-on for Simple Finance. As of Q4/2015 with integrated Simple Logistics.
Subscription licensing with deployment in the private cloud, maintained by SAP
The scope of this solution is close to a full ERP scope (Business All in One scope) however focusing on supporting standard scenarios.
Subscription licensing with deployment in the private cloud, maintained by SAP
Providing simplified key scenarios with a clear focus and priority on the cloud qualities, which are guaranteed across all UIs and all processes to ensure that a true SaaS solution is offered.
SAP S/4HANA Cloud enterprise edition
SAP S/4HANA Cloud marketing edition Cloud project services edition
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
90
Your way to SAP S/4HANA - Summary Scenario 1: New Implementation
Scenario 2: System Conversion
Scenario 3: Landscape Transformation
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
DESCRIPTION
BENEFITS
TARGET GROUP
New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
• New implementation of industry-leading Business Suite • Reengineering and process simplification based on ready-to-run business processes and reference solution delivered with the product
SAP Business Suite customers or net new customers
DESCRIPTION
BENEFITS
TARGET GROUP
Customers who want to change their current system into a SAP S/4HANA system.
• Migration without reimplementation • No disruption for existing business processes • Re-evaluation of customization and existing process flows • Transformation over time
SAP Business Suite customers with SAP ERP or SAP Business Suite on SAP HANA as starting point
DESCRIPTION
BENEFITS
TARGET GROUP
Customers who want to consolidate their landscape or carve out selected entities or processes into a SAP S/4HANA system.
• Stay with current business processes and move gradually to S/4HANA innovations • Harmonized business processes and shared master data through consolidation • Carve out of single entities of the company to SAP S/4HANA and leverage process simplification.
SAP Business Suite customers with multiple SAP ERP or SAP Business Suite on SAP HANA systems, or hybrid cases
External
91
SAP Best Practices for Migration to SAP S/4HANA New Implementation
SCENARIO
CONTENT
TOOL
Install new S/4HANA, OnPremise Edition
Predefined SAP Data Services content including mapping and business transformation rules based on pre-configuration.
SAP Data Services
Install new S/4HANA, cloud edition: net new customers (non-SAP sources) or installed base (SAP ERP)
Predefined ABAP coding in SAP Landscape Transformation for extraction, transformation and loading of data. Predefined mapping and business transformation rules based on pre-configuration. Supports Cloud Project Services and Enterprise Editions.
SAP Landscape Transformation
Implement S/4HANA, Cloud Marketing Edition
Pre-defined content to load data for interactions, contacts and products from nonSAP systems and for Social Media channels (Twitter and Facebook fan pages)
SAP HCI (PI)
SCENARIO
CONTENT
TOOL
Migrate complete SAP ERP system to S/4HANA, OnPremise Edition
Guidance and procedures for one-step migration projects (Upgrade & Migration)
DMO for SUM
SCENARIO
CONTENT
TOOL
Install new S/4HANA, OnPremise Edition
Predefined SAP Data Services content including mapping and business transformation rules based on pre-configuration.
SAP Data Services
Install new S/4HANA, cloud edition: net new customers (non-SAP sources) or installed base (SAP ERP source)
Predefined ABAP coding in SAP Landscape Transformation for extraction, transformation and loading of data. Predefined mapping and business transformation rules based on pre-configuration. Supports Cloud Project Services and Enterprise Editions.
SAP Landscape Transformation
System Conversion
Landscape Transformation*
(*) SAP S/4HANA, Cloud Marketing Edition possible scenario
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
92
The Road to SAP S/4HANA The Transition to SAP S/4HANA, on-premise edition 1511 Technically, the SAP S/4HANA, on-premise edition 1511 is based on: • SAP S/4HANA core components (including simplified financials and simplified logistics) • SAP NetWeaver 7.50 • SAP HANA database In the following constellations, a one-step transition path from SAP Business Suite to SAP S/4HANA, on-premise edition is supported: • One-Step Procedure for customers on anyDB, ABAP AS 7.0x, SAP ERP6.0 EHPx (Unicode) • One-Step Procedure for customers on SAP HANA, ABAP AS 7.0x, SAP ERP6.0 EHPx • One-Step Procedure for customers on SAP HANA, ABAP AS 7.40, SAP ERP6.0 EHP7, SAP Simple Finance add-on 1.0 / SAP Simple Finance, onpremise edition 1503 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
93
The Road to SAP S/4HANA Scenario 1 – System Conversion Focused on existing SAP Business Suite customers that want to change their current system into a SAP S/4HANA, on-premise 1511 system. This includes technically the following steps (main steps – not the complete technical piece list):
Update to SAP NetWeaver Application Server ABAP 7.5
Migrating of the database to SAP HANA (in case, the SAP Business Suite system is not yet on SAP HANA).
Installation of SAP S/4HANA, onpremise edition
Installation of SAP Fiori for SAP S/4HANA, on-premise edition
Migration of data from the old data structures to the new simplified structures
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
94
The Road to SAP S/4HANA Scenario 1 – System Conversion Scenario description Customers who want to change their current system into a SAP S/4HANA system.
SAP S/4HANA On-premise Edition
Start Release ERP 6 / ERP 6.0, EhP 0-7
Benefits for the customer ●
Migration without reimplementation
●
No disruption for existing business processes
●
Re-evaluation of customization and existing process flows
●
Transformation over time
SAP Fiori
SAP ERP Core AnyDB / SAP HANA
SAP S/4HANA Best Practices SAP Update Manager (SUM) with Database Migration Option (DMO)
SAP HANA
Available SAP Best Practices
Target group
●
Migration best practices including respective tools
●
●
Integration best practices with cloud line of business solutions
●
Deployment support with new methodology for on-premise deployments
SAP Business Suite customers with SAP ERP or SAP Business Suite on SAP HANA as starting point
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
95
System Conversion System Conversion & SAP Simple Finance
Technical Procedure based on Software Update Manager (SUM) with Database Migration Option (DMO)
SAP S/4HANA, on-premise edition 1511
SAP S/4HANA Core (S/4HANA Enterprise Mgmt. [FIN + LOG]) Technical Procedure based on Software Update Manager (SUM)
SAP HANA
SAP S/4HANA Finance, on-premise edition SAP ERP 6.0 Netweaver 7.40 / Enhancement Package 7
SAP HANA
Start Release ERP 6.0, EhP 0-7 SAP Netweaver 7.0x
The Road to SAP S/4HANA
AnyDB or SAP HANA
• SAP S/4HANA Finance (SAP sFinancials), on-premise edition is the first offering under the S/4HANA product family • The decision to go for SAP S/4HANA Finance, on-premise edition should be based on the business benefits but is not a mandatory prerequisite for any system conversion
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
96
Conversion Scenario Description Customers who want to change their current system into a SAP S/4HANA system.
SAP Update Manager (SUM)
NetWeaver and Application transition in one step.
SAP GUI
SAP ERP Core
Within Guided Beta only customers with HANA DB could participate.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP S/4HANA On-premise Edition
(SAP GUI) / SAP Fiori
*
SAP HANA
SAP S/4HANA Core SAP HANA
What
How
1
Perform Pre Checks
Maintenance Planner, S/4HANA Transition Checks, Custom Code Checks
2
Conversion
SUM (Software Update Manager)
3
Configure Fiori
Generic Config + App specific Configuration
4
Post steps
e. g. Custom Code adaption
External
97
Transition to SAP S/4HANA Major Elements of Deploy Phase in Transition Process
1
Preparation Preparation steps on start release Analysis of used business processes – mapping to SAP S/4HANA innovations Identify required integration scenarios of target state Run pre-Transformation Checks on source system Used functionality, supported industries, available add-on, custom code …
Mandatory preparation steps to be executed on source system.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
2
Technical Implementation “Installation” of SAP S/4HANA • HANA Database • SAP S/4HANA application core
Customizing adjustment Adjustment of technical infrastructure
3
Semantical Adoption Adapt custom code to comply with SAP S/4HANA scope & data structure Adapt business processes to leverage new SAP S/4HANA innovation functionality Adapt integration (if applicable) Implement Fiori UIs Introduce new SAP S/4HANA innovation scenarios
External
98
System Conversion SUM Phases
Downtime minimizing steps using "switch upgrade" technology
Table replacement Kernel switch AIM, XPRA …
Uptime
Shadow System Target Release
Switch Upgrade Technology
Post Processing
Regular Uptime
Downtime Uptime Start Release
Preparation Phase Pre-Transformation Checks Application specific adaptions on start release
Time
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
99
The Road to SAP S/4HANA Unicode
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
100
The Road to SAP S/4HANA Unicode – one step
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
101
The Road to SAP S/4HANA non-Unicode – two steps
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
102
The Road to SAP S/4HANA Procedure
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
103
The Road to SAP S/4HANA New tools: Maintenance Planner Maintenance Planner is available now and allows planning changes in the landscape, based on SAP Solution Manager’s processes and data. It will enable customers using SAP Solution Manager 7.2 to plan and manage their SAP landscapes. Maintenance Planner can already be leveraged by SAP Solution Manager 7.1 customers as well. Maintenance Optimizer continues to fully support SAP Solution Manager 7.1 customers and will be replaced in SAP Solution Manager 7.2 by Maintenance Planner
Check the following link for more information http://scn.sap.com/docs/DOC-65243
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
104
Guided Beta S/4HANA On Premise 1511 Maintenance Planner With “SAP S/4HANA On Premise 1511” all the “MOPZ activities” (Stack calculation and checks) will replaced by the Maintenance Planner. •
Maintenance Planner is the next generation tool for planning landscape maintenance.
•
It is a solution hosted by SAP.
•
It simplifies the landscape maintenance process to update, upgrade and install new systems with greater ease and efficiency.
•
It provides easy visualization of maintenance dependencies.
•
It prevents inconsistency across systems in SAP customer landscape.
Maintenance Planner User Guide:
http://help.sap.com/maintenanceplanner
Access to Maintenance Planner:
https://apps.support.sap.com/sap/support/mp
External Information Sources:
http://scn.sap.com/docs/DOC-65243
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
105
S/4HANA On Premise 1511 Maintenance Planner Checks Goal: Fulfillment by: Prerequisite: More Info:
Ensure detailed technical consistency before conversion (e. g. Checking for Add-Ons,…) The Maintenance Planner will try to generate a valid stack from source -> target release Customer will perform the Check via the Maintenance Planner Connect the SAP system with the Maintenance Planner. See http://scn.sap.com/docs/DOC-65243 Conversion Guide, Section 4.1
Non supported Add-Ons and Business functions needed to be deactivated before the conversion. 2214409 SAP S/4HANA, on-premise edition 1511: Compatible Add-ons 2240359 SAP S/4HANA, on-premise edition 1511: Always-Off Business Functions 2240360 SAP S/4HANA, on-premise edition 1511: Always-On Business Functions
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
106
The Road to SAP S/4HANA Preparation Phase – Assessment Options Technical system assessment SAP S/4HANA transition pre-checks
Semantical assessment Simplification List
Preparation
Technical system assessment Custom Code Analysis © 2015 SAP SE or an SAP affiliate company. All rights reserved.
ERP DEV or ERP Q System
Custom code Metadata • Used SAP objects • Extended SAP objects • Modified SAP objects
Custom Code Extractor
Run Custom Code Extractor and transfer metadata to analysis system
ERP Productive System
Optional: get usage data to restrict effort for productively used custom code
Analysis System Custom Code Metadata Simplification Database Usage Data
Work on customer specific hits • Affected custom code • Affected extensions • Affected modifications
External
107
The Road to SAP S/4HANA Pre-Checks SAP supports the customer by providing pre-checks. These identify the steps you need to take to ensure your system is compatible with the conversion process. Note Perform these checks before starting the Software Update Manager (SUM). Pre-checks are shipped as SAP Notes to customers that want to convert to S/4HANA . Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist. Procedure 1. Implement SAP Note 2182725, and all the related notes attached to it. 2. Run Report R_S4_PRE_TRANSITION_CHECKS
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
108
S/4HANA On Premise 1511 S/4HANA Transition Checks Goal:
Ensure detailed consistency from application perspective before conversion
Fulfillment by:
Customer will perform the Checks on the source system. Need to perform before the SUM process
Prerequisite:
Implement all the relevant SAP notes (e. g. 2182725 - S4TC Delivery of the S/4 System Conversion Checks) as mentioned in the Conversion Guide.
Follow up actions:
Clean up all the listed inconsistency's.
More Info:
Conversion Guide, Section 4.2
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
109
Guided Beta S/4HANA On Premise 1511 S/4HANA Transition Checks – Some examples… Issue topic
Reason
Action
Customer Vendor Integration
Customers without contact persons
functionality implemented
MARDH/MARCH/MARD/MARC
Historical data on storage location and Mat-Id for deleted storage locations
Delete entries
MSTB
4 corrupt records
deleted
MSEG/MARA
MSEG/MARA not in MARA anymore
entries deleted
T001W/MARC/MARCH/MCHBH/MARA
Inconsistencies between these tables
entries deleted
T001K/T001W
Inconsistencies between T001K and T001W
corrected
MM periodic run
Periodic run not executed for „inactive“ plants
executed
…
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
110
The Road to SAP S/4HANA Simplification List – Overview: Technical & Semantical Conversion Maintenance Planner
SUM
DMO
Technical procedure based on Software Update Manager (SUM) with Database Migration Option (DMO)
SAP GUI SAP ERP Core (SD, MM, LO, FIN, HR …) AnyDB / SAP HANA
Technical
SAP S/4HANA On-premise Edition
(SAP GUI) / SAP Fiori SAP S/4HANA Enterprise Mgmt.
Semantical Adaption supported by Simplification List and tool-support
(Sales, Service, Procurement Supply Chain, Manufacturing, Financials …)
SAP HANA
SAP S/4HANA conversion pre-checks Custom Code Analysis
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
111
S/4HANA On Premise 1511 Custom Code Checks Goal:
Identify custom code, that will have to be adapted during the conversion project Although it is not mandatory, it is highly recommended that you perform this check prior to beginning the conversion process.
Fulfillment by:
Implement note 2185390 (non 7.50 system) or run the check directly in the system (>= NW7.50)
Follow up actions:
Clean up all the listed inconsistency's (after the conversion)
More Info:
Conversion Guide, Section 4.3
•
Analyzing Custom Code – General approach https://uacp.hana.ondemand.com/http.svc/rc/PRODUCTION/7b7a606d728810148a4b1a83b0e91070/1511%20000/enUS/frameset.htm?0bb83ef76fbf46c89fd9fa5f3af8c0c6.html
•
Analyzing Simplifications (how to read the output) http://help.sap.com/saphelp_nw75/helpdata/en/89/e42fbda75f487f8e9a1024d734c006/content.htm
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
112
The Road to SAP S/4HANA Custom Code Check
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
113
S/4HANA – Custom Code Adaption SAP will provide tools, which allow customers before the conversion (upgrade) to SAP S/4 HANA to assess the impact of S/4 HANA simplifications on customer coding, as well as guidance how to adapt the coding.
Migration Analysis Tool Customer system before the conversion to SAP S/4 HANA
Compare to lists of SAP objects with incompatible changes in SAP S/4 HANA
Analyze customer code and extract usage of SAP objects
Customer objects affected by the changes (with Navigation to IDE)
Show customer objects affected by the changes
Referring to Simplification Database (delivered by SAP via SAP Service Marketplace) Lists of objects with incompatible changes in SAP S/4HANA + corresponding SAP notes describing how to adapt to the changes.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Notes giving guidance for each Simplification/type of change how to adapt customer code. External
114
The Road to SAP S/4HANA ABAP custom code migration – Adapt S/4HANA changes – Tool support Analysis System
Task
Simplification DB
1
Download Simplification Database from SMP and upload to analysis system Customer ERP DEV or Q System
2
Run Custom Code Extractor and transfer metadata to analysis system
3
Optional: Get usage data to restrict effort for productively used custom code
Customer ERP Productive System
Changed/deprecated functionality
Changed/deprecated business processes
& Custom code metadata Used SAP objects
Custom Code Extractor
Extended SAP objects Modified SAP objects
& Customer specific metadata
Collect Usage Data
Usage data from productive System
= Result of Analysis
4
Work on customer specific hits
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Affected custom code
Affected extensions Affected modifications External
115
System Conversion Example - Activities During the Different Phases in Logistics
Material Ledger
Inventory valuation not supported in S/4HANA. Switch to material ledger can be done before migration (activation of ML supported via dedicated report) During downtime ML migration to new logic.
Pattern 1: Activity before Migration + Downtime Pattern 2: Activity before or after Migration Pattern 3: Activity after Migration
Pattern 4: Technical Migration
One Logic for BOM-Determination only via production version.
BOM-Determination
Simplification of MRP areas
MM-IM
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Conversion to new logic via report possible before and after migration possible, has to run before starting MRP in S/4HANA
One logic for all storage location MRP-Logic. In case of using such logic, program needed to create missing MRP-areas and MRP-File before running MRP in S/4HANA
Conversion of IM-Tables (MSEG) into new MATDOC
External
116
SAP S/4HANA Simplification List – Phase-wise sorting of items: Examples Preperation Phase
Migration Phase
• Logistics Information System (LIS): The LIS based analytics capabilities are considered as not strategic. The strategic analytics architecture within SAP S/4HANA is based on open CDS views.
WILL-Do Tasks
After Go–Live Phase
• Logistics Information System (LIS): The LIS based analytics capabilities are considered as not strategic. The strategic analytics architecture within SAP S/4HANA is based on open CDS views.
• Master Data: Activation of Business Partner Approach (Customer-Vendor Integration)
MUST-Do Tasks
• Inventory Management: Switch from Inventory valuation to material ledger (activation of ML supported via dedicated report). Note: it is still possible to decide e.g. per material and plan whether Actual Costing shall be applied or not. • Automated logic (triggered as part of the technical procedure within the Software Update Manager [SUM]) to transfer application-specific data (for example specific transactional data) from old data structure into new SP S/4HANA data structure
Automated Tasks
Custom Code related Tasks
• Execute Custom Code Check Analysis • Custom Code optimizations (not SAP S/4HANA specific – following best practice guidelines)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
• Custom Code Adaption to comply to SAP S/4HANA data structure and scope
• Additional Custom Code optimizations (for example: following SAP S/4HANA cloud guidelines)
External
117
The Road to SAP S/4HANA Scenario 2 – Landscape Transformation Focused on existing SAP Business Suite customers that want to change their current system or system landscape into a SAP S/4HANA, on-premise 1511 system (or system landscape). This scenario covers more complex migration scenarios.
This includes technically the following steps (main steps – not the complete technical piece list):
Possibly a new installation of a SAP S/4HANA, on-premise edition 1511 system
Possibly an “upgrade” move to SAP S/4HANA, on-premise edition 1511 system
Additional migration steps that are based on SAP Landscape Transformation combined with SAP Landscape Optimization services
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Examples of SAP S/4HANA Landscape Conversion Consolidation of several (local, regional) SAP Business Suite systems into one (global/central) SAP S/4HANA, on-premise edition 1511 system. Adding a central finance system to an existing distributed ERP system landscape, which may consist of (several) SAP Business Suite systems and/or (several) Non-SAP systems. Company-code-wise migration to SAP S/4HANA, on-premise edition 1511 (more commonly called “Carve-Out” scenarios) External
121
The Road to SAP S/4HANA Scenario 2 – Landscape Transformation Scenario description e.g. Central Finance
Customers who want to consolidate their landscape or carve out selected entities or processes into a SAP S/4HANA system.
● ●
●
●
AnyDB or SAP HANA
SAP S/4HANA Best Practices SAP HANA
Harmonized business processes and shared master data through consolidation
Start Release SAP ERP Core
Carve out of single entities of the company to SAP S/4HANA and leverage process simplification
SAP Business Suite customers with multiple SAP ERP or SAP Business Suite on SAP HANA systems, or hybrid cases
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Cloud Edition
SAP Fiori
Stay with current business processes and move gradually to S/4HANA innovations
Target group
SAP S/4HANA
Start Release SAP ERP Core
Benefits for the customer
SAP S/4HANA On-premise Edition
AnyDB or SAP HANA
Available SAP Best Practices ●
Data migration best practices and integration best practices with cloud line of business solutions
●
Deployment support with new methodology for cloud and on-premise deployments
●
Ready-to-run business processes, e.g. as basis for Central Finance External
122
The Road to SAP S/4HANA Scenario 3 – New Implementation Focused on net-new customers (coming from any legacy system) or SAP Business Suite customer that starts for different reasons with a new installation. This includes technically the following installation steps (main steps – not the complete technical piece list):
Installation SAP NetWeaver Application Server ABAP 7.5 based on SAP HANA
Installation of SAP S/4HANA, on-premise edition
Installation SAP Fiori for SAP S/4HANA, onpremise edition
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP S/4HANA
SAP S/4HANA
On-premise Edition
Cloud Edition
SAP Fiori Legacy Any customers legacy system
Option: Data Migration from Legacy System
SAP S/4HANA Core SAP HANA
External
123
The Road to SAP S/4HANA Scenario 3 – New Implementation Scenario description New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
New implementation of industry-leading Business Suite
●
Reengineering and process simplification based on ready-to-run business processes and reference solution delivered with the product
SAP S/4HANA Cloud Edition
SAP Fiori
Benefits for the customer ●
SAP S/4HANA On-premise Edition
Legacy Any customers legacy system
Option: Data Migration from Legacy System
SAP S/4HANA Best Practices SAP HANA
Target group ●
SAP Business Suite customers or net new customers
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Available SAP Best Practices ●
Data migration best practices and integration best practices with cloud line of business solutions
●
Deployment support with new methodology for cloud and on-premise deployments
●
Ready-to-run business processes and reference solution External
124
New Installation Scenario Description New installation of SAP S/4HANA e.g. for complete Greenfield approach or customers migrating a legacy system.
SAP S/4HANA Download from SMP
On-premise Edition
Implementation via SWPM
Within the Guided Beta Program there was no migration of a legacy system.
SAP Fiori SAP S/4HANA Core SAP HANA
Pre-configured content for core business processes for S/4HANA. Role specific Customizing and Guided configuration.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
What
How
1
Install S/4HANA
SWPM (Software Provisioning Manager)
2
Configure Fiori
Generic Config + App specific Configuration
3
Implement and configure the “Best practice content”
Download, Solution Builder, manual tasks
External
125
S/4HANA Cookbook SAP S/4HANA cookbook: Guiding you through your implementation To answer your implementation questions, we plan to release a structured and regularly updated guide (the SAP S/4HANA cookbook) within the SAP S/4HANA SCN community that links to relevant information around the implementation of SAP S/4HANA.
Find more information here: http://scn.sap.com/docs/DOC-65072 The purpose of the blog entry is:
»
To bring more clarity in the discussions what are the different pre-requisite for SAP Simple Finance, on-premise edition 1503 and SAP S/4HANA, on-premise edition 1511.
»
Currently we get questions like: • • •
Is it required to go to EHP7 first to go to SAP S/4HANA? Is sLOG included in EHP8? Is RDS is only way to deploy exchange innovation code on top of business suite on Hana? See question from SCN (http://scn.sap.com/thread/3764287)
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
126
SAP S/4HANA Cookbook http://scn.sap.com/docs/DOC-64980
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
127
SAP Help http://help.sap.com/s4hana_op_1511#section3
The System Conversion to SAP S/4HANA, on-premise edition 1511 - Technical procedure and semantic adaption tasks http://scn.sap.com/docs/DOC-68976
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
128
S/4HANA On Premise 1511 Major SAP Notes
2189824
SAP S/4HANA, on-premise edition 1511: Release Information Note
http://service.sap.com/sap/support/notes/2189824
2182725
Delivery of the S/4 System Conversion Checks
http://service.sap.com/sap/support/notes/2182725
2233962
Add. info on converting to S/4HANA, on-premise edition, using SUM SP15
http://service.sap.com/sap/support/notes/2233962
2214213
SAP S/4HANA, on-premise edition 1511: Restriction Note
http://service.sap.com/sap/support/notes/2214213
2214409
SAP S/4HANA, on-premise edition 1511: Compatible Add-ons
http://service.sap.com/sap/support/notes/2214409
2240359
SAP S/4HANA, on-premise edition 1511: Always-Off Business Functions
http://service.sap.com/sap/support/notes/2240359
2240360
SAP S/4HANA, on-premise edition 1511: Always-On Business Functions
http://service.sap.com/sap/support/notes/2240360
2185390
Repository Information System: Custom Code Extractor
http://service.sap.com/sap/support/notes/2185390
2241080
Custom code check content for SAP S/4HANA on-premise edition
http://service.sap.com/sap/support/notes/2241080
2214245
SAP S/4HANA "SAP FIORI FOR SAP S/4HANA 1511": Release information
http://service.sap.com/sap/support/notes/2214245
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
129
Technical Workshop S/4HANA Finance
S/4HANA Finance Add-on for SAP Business Suite on HANA
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
131
SAP Simple Finance Add-On 2.0 (1503) Related Product Versions
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
132
SAP Simple Finance Add-On 2.0 (1503) Related Product Versions – Technical Names
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
133
SAP Simple Finance Add-On 2.0 (1503) Upgrade Paths to SAP Simple Finance in one step
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
134
SAP Simple Finance Add-On 2.0 (1503) Installation or Upgrade knoledge
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
135
SAP Simple Finance Add-On 2.0 (1503) Migration process
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
136
Installation Hints for SAP Simple Finance Add-on installation will be possible?
Check Prerequisites
To check whether the add-on installation will be possible, verify the currently installed software components in regards to their compatibility with the SAP Simple Finance add-on. How-to
1
Read SAP note 1976158 (compatible add-ons) and compare with the content of database table CVERS*.
2
Download table CVERS and ask your SAP contact / development angel to perform the check for you.
Deploy and use the check report provided with SAP note 3 2105948 .
* CVERS = Release of Software Components in System; use t-code SE16N to list the content © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
137
SAP Simple Finance Add-On 2.0 Dependencies to other ERP components Summary •
All SAP ERP 6.0 software components, that need to be updated to EhP 7 during the installation of the SAP Simple Finance add-on are included in the Instance / Technical Usage Applications for FIN 700
•
ERP Enterprise Extensions, Industry Solutions and (Partner) Add-Ons are released for usage with SAP Simple Finance once successfully tested – refer to the listed SAP Notes to check for the currently released scope
•
SAP Simple Finance cannot be installed with components, that are not yet released for a combined usage
Release Information for SAP Simple Finance add-on [SAP Note IDs] Examples
1.0
2.0
ERP Enterprise Extensions and Industry Solutions
EA-PS, RETAIL, FI-CA, IS-OIL, IS-H
1968568
2119188
ERP Add-Ons
C-CEE
1976158
2103558
ERP Partner Add-Ons
OTEXVIM (OpenText VIM)
2012817
2100133
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
138
SAP Simple Finance Add-On 2.0 (1503) Check custom code
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
139
SAP Simple Finance Add-On 2.0 (1503) Sizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
140
SAP Simple Finance Add-On 2.0 (1503) Prepare XML Stack
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
141
SAP Simple Finance Add-On 2.0 (1503) Automatic check for Simple Finance on-premise edition 1503 You can use the program to perform the following checks: 1) Collecting general information of system usage 2) Check functional Restrictions / Differences compared to ERP 6.0 EhP7, i.e. classic Financials 3) Check the installed components 4) Check customer-specific source code 5) Data migration pre-checks 6) Quick compare version of check report code Implement note: 2176077 - Check report for Simple Finance on-premise edition 1503
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
142
High Level migration steps Business Downtime
Uptime
Preparation
Close activities Several Data Migration steps Job stops User locking
Business Reconciliation
Technical Prerequisites incl. SFIN Installation
SPAU
Reporting snap Upgrade from SPAU shots for ERP xyz to adjustment comparisons ERP xyz (EHP) Incl. NW 7xx SPSx sFIN xx Addon SP0
Uptime
Data Migration
Preparation and Customizing in General Ledger
Preparation Preparation and Customizing and Customizing in Asset Accounting in Controlling
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Post Processing
Migration of Checks after tbd: migration: FI (Financials) CO (Controlling) AA (Asset Accounting)
Migration
Data Migration Preparation General Preparation
Business Reconciliation
Accounting table partitioning and CDS View Generation
Migration cost elements and customizing
Enrich Data
Migration of line Items in new data structure
Migration of Balances
Finish Data Migration
External
143
Installation / Upgrade Special Hints for SAP Simple Finance - Overview Planning
Preparation
•
Check functional scope and restrictions
•
Check whether the technical upgrade is possible
•
Check custom code for needed adaptations to the new SAP data model etc.
Prepare Data Migration Pre-Installation Steps* for upgrade only
Prepare Installation/ Upgrade
Check Prerequisites
•
SolMan/MOPZ: Prepare stack XML and download software
•
Check & get latest SUM release !
•
Apply important bug fixes acc. to Release Information Notes (RINs)
• Sizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Installation
•
The application data migration must be prepared before the add-on is installed
•
Application knowhow in FI, CO and AA needed !
•
Resolve data inconsistencies !
Data Migration
Deploy SAP HANA Content
Install Add-On
Data Migration Post-Installation Steps* for upgrade only
•
Use SUM to install the add-on - SAINT is not supported
•
Apply important bug fixes acc. to Release Information Notes (RINs)
•
Default Switches
•
Use SAP HANA ALM** to deploy SAP HANA content
•
Unless the application data migration is completed, business cannot continue
for SAP Simple Finance application consultants need to be involved to prepare the data migration before the add-on is installed ! External
144
Migration to SAP S/4HANA Finance 1503 Cookbook
http://scn.sap.com/docs/DOC-65111 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
145
Migration to SAP S/4HANA Finance 1503 Checklist
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
146
Migration to sFIN Details and guides
Link
Link
Link © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
147
Technical Workshop S4/HANA Technical Innovations
SAP S/4HANA Innovations Overview
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
149
SAP S/4HANA Innovations Overview
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
150
SAP S/4HANA Innovations Overview ABAP Core Data Services (CDS) • General concept to define new Data Dictionary Views ABAP Open SQL • Modern Syntax, Expressions • Complex Joins, Removing Restrictions ABAP Managed Database Procedures (AMDP) • ABAP “Look & Feel” for calling HANA SQLScript © 2015 SAP SE or an SAP affiliate company. All rights reserved.
HANA Only
External
151
SAP S/4HANA Innovations Architecture
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
152
CDS ABAP Integration
Infrastructure ensures Any DB support
Consistent Lifecycle Management and extensibility as with all other ABAP artifacts
SAP NetWeaver ABAP
OPEN SQL CDS ABAP
(S)QL Engine
Highly reusable and extensible CDS artifacts
Lifecycle Management
Leverage DDIC semantics
CDS also available in native SAP HANA (see: DEV 160 - Encounter Core Data Services with SAP HANA) © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Any SAP Supported DB
External
153
SAP S/4HANA Innovations CDS Views – Scope in ABAP
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
154
SAP S/4HANA Innovations CDS Views - Example
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
155
Exploit SAP HANA in Productive Applications Application logic with performance relevant coding
Open SQL, Core Data Services, ABAP Managed Database Procedures
ABAP Managed Code-Pushdown
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
156
SAP HANA ABAP Managed Code Pushdown
Code Complexity Adjustments
(more)
(less)
Advanced SQL programming Reuse components Transparent optimizations Fast Data Access For all entries
(low)
ALV with integrated data access Enhanced search help …
Open SQL enhancements Advanced view building with Core Data Services (CDS)
Use all benefits of SAP HANA
Exploit SAP HANA native features ABAP managed database procedures CDS table functions via ABAP managed database functions * (Native SQL , ADBC)
(high) (*) Introduced with ABAP 7.5
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
157
CDS Common Basis for Domain-Specific Frameworks Reusable and unified view model for all use cases Annotations enabling flexible usage in different contexts
Business Logic
Planning
Analytics
CDS Efficient development BI-Tools
OData
Search
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
158
SAP Fiori Apps New Programming Model Classic GUI based transactions
Role based Fiori apps
Fiori Programming Model
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
159
SAP S/4HANA Architecture and Programming Model
Transition to the Fiori programming model User experience on all devices drives the model
Combine transactions, search and analytics Common cloud qualities (e.g. extensibility) Optimized for SAP HANA Simplify the transition from GUI to Fiori apps © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
160
Fiori Effective ABAP Programming Model for Apps Fiori Shell
One data model for all consumers (CDS)
Fiori App, UI5 ALV R
Directly publish CDS views to the UI (OData Service)
OData
NW / ABAP Gateway
ALV like HANA optimized services for analytic apps (SADL)
R
Transaction, error and event handling services (BOPF) Manual Impl. (ABAP/SQL Script)
GW API
Application Frameworks (SADL,BOPF)
R
*SQL
CDS View R
deploy
SAP HANA CDS OData SADL BOPF
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Core Data Services Open Data Protocol Service Adaptation Definition Language Business Object Process Framework
SQL Engine
SQL View
External
161
SAP S/4HANA Customer Extensions for Cloud and On-Premise
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
1
Key user can do easy changes directly in the app
2
ABAP based extensions and custom code
3
SAP HANA Cloud Platform for side by side extensions and cloud integration
External
162
SAP S/4HANA Extensibility Key User Extensibility – Easy Changes & Extensions of a Fiori App UI-Layout-Changes e.g. hide, move, add existing fields
Fiori UI Add customer specific logic (BAdI)
Add custom fields
OData Service
Application
Database Table © 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
163
SAP S/4HANA Extensibility Key User Extensibility – Scope and Roadmap
Field extensibility (custom fields)
UI extensibility (hide, move, add fields, change labels)
Table extensibility* (Custom objects, node extensibility)
Report extensibility, new reports
Business logic extensibility (Code breakouts)
Forms extensibility, new reports (Print forms and e-mail templates)
Key user transport capabilities
Key user in-app extensibility scenarios
*Note: Outlook – Planned Innovation
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
164
SAP S/4HANA Extensibility ABAP Based Extensions and Custom Code ABAP Extensions Designed for Cloud
Classic ABAP custom code On-Premise
ABAP extensions
ABAP extensions
No modifications use only public APIs
SAP Standard
SAP objects are modified, enhanced and used without restrictions
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Public Model / Whitelist CDS
BAdi
API
SAP Standard
Automated SAP software deployment needs clear separation of SAP and custom code
External
165
SAP S/4HANA Cloud Enterprise Edition Process for Custom and Partner Code Development Automated Gate Check to guarantee Separation of Concerns compliance of custom / partner code before take over in cloud operations
1. Check that modification-free 2. Check SAP objects are accessed only via whitelisted APIs 3. Ensure scannable code, i.e. no dynamic calls, no runtime code generation Custom / Partner Development Landscape (individual)
SAP Standard
Gate Check
Extension Add-On Check Tools
No other SAP objects used
S/4 Cloud Enterprise Edition Key User Extensions
Extension Add-On SAP Standard
Whitelisted SAP Objects No incompatible changes
Existing Custom / Partner Code © 2015 SAP SE or an SAP affiliate company. All rights reserved.
SAP Dev. Landscape
External
166
SAP S/4HANA Extensibility SAP HANA Cloud Platform – Side-by-Side Extensibility
On-Premise
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Cloud
Hybrid
External
167
SAP S/4HANA Extensibility SAP HANA Cloud Platform – Side-by-Side Extensibility User Interface (Fiori) Frontend
Frontend
Backend: ABAP Server
Custom
Custom User Interface (Fiori)
Backend: HCP
OData Service
OData Service
Application
Application
Database Table
Database Table
SAP
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
External
168
