1. SAP S/4HANA Migration

2. S/4HANA Key Enablers
SAP HANA
SAP Fiori
Real Time &
Simplified
SAP HANA as underlying platform:
•OLTP & OLAP merge
•In-memory compression
•Increase in speed
• SAP Fiori as user experience
(UX) Paradigm
• Unified cross-application
user experience
•Web based, all devices
•Role based
Simplified of underlying data
models:
•No Aggregates & No Indices
•Higher throughput
•Higher flexibility
•Data footprint reduction

3. Upgrade Paths

4. Migration from SAP Business Suite on Any Database
1
PLAN
Scope migration effort and
identify key business
scenarios
For customers already on SAP ERP 6.0, upgrading to SAP S/4HANA Finance is done in
four phases
1 1
Upgrade
Upgrade to Enhancement
Package 7 and Unicode data
type
2
OS DB Migration
Install and migrate database
to SAP HANA
3
Install
Install Innovation package
(add-on/new code)
4
•The technical upgrade procedure is based on SAP’s Software Update Manager (SUM) using the database migration
option (DMO) and near-zero downtime maintenance (nZDM) capabilities as part of SUM.

5. ECC Upgrade & HANA DB Migration
Traditional DB
ABAP 7.x
ECC 6 EHP x
Kernal 7.x
SAP Frontend
Traditional DB
ABAP 7.4
ECC 6 EHP 7
Kernal 7.4
SAP Frontend
HANA DB
ABAP 7.4
ECC 6 EHP 7
SAP Frontend
BOBJ
HTML5
Upgrade
HANA DB Migrate

6. High Level Project Planning – DB Migration
M1 M2 M3 M4 M5
Preparation & Planning
HANA Assessment
Execute readiness checks
Conduct Hardware Sizing
Finalize Migration Option (DMO) & Upgrade steps
Update SP Install & upgrades required
HANA Installation of hardware
HANA Install & Set up
Conduct HANA health check
HANA Migration & Testing
Prod client Copy to Sandbox
Sandbox HANA DB migration
Functional Testing & Technical Validation
Checkpoint & lessons learned
Development Box HANA DB migration
Functional Testing & Technical Validation
Prod client Copy to QA
QA Box HANA DB Migration
Functional Testing & Technical Validation
UAT / Regression Testing (Business users involved)
Deploy
Back-up Production and contingency planning
PROD box HANA DB Migration
Cutover Activities
Perform Go-Live
Support
Support Key Technical users
Go-live
Business Sign-off

7. Migration to Simple Finance
Install Simple
Finance Add-on
HANA DB
ABAP 7.4
ECC 6 EHP 7
SAP Frontend
BOBJ
HTML5
Ariba Concur Fieldglass Hybris SuccessFactors
Native integration for hybrid scenarios
HANA Views
Physical Tables
Hot Warm Cold
SAP HANA Platform
SAP Business Suite Applications – Simple Finance
SAP Fiori UX
Mobile & Other
Devices
SAP Accounting
Powered by
HANA
SAP Cash
Management
Powered by HANA
SAP IBP for
Finance

8. Post Migration
Data Migration
Customizing
Installation
Preparation
S/4 Simple Finance Migration Process
For customers already on SAP HANA DB, upgrading to SAP S/4HANA Simple Finance is done
as below:
• Perform process tests to ensure successful migration
• Transfer data to cold database area
• Update due date and offsetting account
• Migration of financial data (GL/AP/AR/AA/CO/ML)
• Reconciliation & Checks within and after migration
• Customize General Ledger Accounting
• Customize and activate New Asset Accounting
• Customize Management Accounting (Account Based CO-PA)
• Install simple finance add-on
• System backs up index and total tables automatically
• Create blueprint for process redesign & reporting
• Perform reconciliation, period-end activities, gather reporting snapshots for before/after
comparisons

9. Preparation
• Perform Period end closing activities
• Financial Reporting
• Reconciliation for ensuring the data consistency
• Pre Checks – Check Customizing Settings prior to upgrade to Simple Finance (SAP
Note: 2129306)
• Run Special Check Report (SAP Note: 1939592)
• Closure of Posting Periods
• Execute and Save Financial reports for comparison after migration

10. Installation
• Installation is performed by the System Administrator
• Following steps are executed automatically by the system
▫ Creation of Backup tables for Totals and Index tables (*_BCK in FI and *_BAK
in CO)
▫ Save the Totals and Index tables in backup tables
▫ Delete the original totals and index tables
▫ Creation of SAP HANA views (with the same names) for the totals and index
tables and new table ACDOCA for Universal Journal

11. Customization
• General Ledger Customization
• New Asset Accounting Customization
• Controlling Customization
Activate Business Functions
• In this customizing activity you activate the business functions that are
necessary for migrating to the SAP Simple Finance add-on for SAP Business
Suite powered by SAP HANA.
• You have to activate the following business functions in the customizing
system and import them into the productive system:
– FIN_GL_CI_1
– FIN_GL_CI_2
– FIN_GL_CI_3
• These business functions activate functionality in general ledger which is
mandatory for the SAP Simple Finance Add-on.

12. Migration
• Cost Element Master Data
• Migration of Line Items
• Migration of Balances
• Reconciliation of Migrated Data
• Finalization of Migration

13. Post Migration
• Filling of Offsetting Account
• Filling of Due Dates
• House Bank Migration
• Create Cold partitions for backup tables created during migration

14. Suggested Migration Sequence (1/3)
Productive system
uptime
Downtime
-Preparation
-Installation
-Import
Customization
-Migration
-Completeness
Check
C
o
p
y
Import
Development/Test System
System
Preparation
Phase
Installation of
add-on
Customization
for migration
Data migration
Post Data
Migration
Data checks
and process test
Checks:
Pre-checks
Consistency
& data clean
up
 Custom
Code
Closing
activities
Reporting
Installation:
Installation
of SAP Simple
Finance Add-
on
Fiori
HANA Live
Customization:
Customization of
General Ledger
Asset Accounting
Controlling
Data Migration:
Cost Elements
Enrich
items/documents
Line items
Balances
Post
Migration:
• Add further
information to
documents
•Cold data store
Data Check:
Data
comparison
Reporting
checks
Process Test

15. Suggested Migration Sequence (2/3)
1. Start migration in separate copy of productive environment (DEV1)
2. Start migration in Development environment (DEV1)
3. Copy productive environment (PRD) to test environment (QA1)
4. Import customizing requests from development system (DEV1)
5. Migrate test environment (QA1), correct the errors found directly in test
environment (QA1).
6. Repeat step 3, 4 and 5 test migration again to ensure error free migration
7. Migrate productive environment after successful test migration (QA1)

16. Suggested Migration Sequence (3/3)
DEV QA PRD
Existing landscape
Transport Transport
DEV1
1.Copy
QA1
2. Migration to
S4 Activities
3.Copy
Import
4.Import Customizing
Requests 5.Perform
Migration and
correct errors
6.Repeat 3,4 and 5
to ensure error
free environment
Import
7. Import the
Customization to
Production and
complete rest
migration steps in
production

17. Duration of Migration Project
Factors that can affect the duration are
 Support from customer
 Experience of project members and consultants
 Quality of Data
 Size of system
Test migration is the best input for calculation of duration and potential challenges
during the migration project

18. New Document Structure
With SAP S/4HANA Finance, new universal data table ACDOCA has been installed. This table contains all of the line
item documents from FI, FI-AA, and CO. All postings of these applications are written to the new table after the
installation and migration are complete.

19. Safeguarding Current Investments
The following tables were replaced by SAP HANA views with the same
names:
• The line item, totals tables and application index tables of
General Ledger Accounting (GLT0, BSIS, BSAS and
FAGLFLEXA, FAGLFLEXT, FAGLBSIS, FAGLBSAS)
• The totals tables and application index tables of Accounts
Receivable and Accounts Payable (KNC1, KNC3, LFC1, LFC3,
BSID, BSIK, BSAD, BSAK)
• The line item and totals tables of Controlling (COEP for certain
value types, COSP and COSS)
• The material ledger tables for parallel valuations (MLIT, MLPP,
MLPPF, MLCR, MLCD, CKMI1, BSIM)
• The Asset Accounting tables (ANEK, ANEP, ANEA, ANLP,
ANLC)
Replacing these tables with views with the same names ensures the
continuation of all read accesses to the tables mentioned.