This series of publication intends to provide an overview and explanation of major steps and considerations for BW on HANA migrations from anyDB (any database). The complex procedure involves: 1) Preparatory work in the BW system 2) SUM DMO Upgrade and Actual migration 3) Post processing on the migrated systems This first part focuses on the preparation tasks on the BW system. By OZSoft Consulting for ITConductor.com Author: Terry Kempis Editor: Linh Nguyen

1. BW Migration to HANA
Part 1 of 3
Preparation in BW System
By OZSoft Consulting for ITConductor.com
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 1

2. Introduction
• This series of publication intends to provide an overview and
explanation of major steps and considerations for BW on
HANA migrations
• Migrating a BW system from anyDB (any database) to HANA
involves
1. Preparatory work in the BW system
2. DMO and Actual migration
3. Post processing on the migrated systems
• This first part focuses on the preparation tasks on the BW
system.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 2

3. Preparatory work in the BW system
Preparation is a collaborative work between Basis, BW
support team and ABAP/development team.
Create a production copy Sandbox
Best practice in doing an upgrade is to create and use a
production copy sandbox first before starting with the
development system. It offers the following benefits:
1. Identify potential issue and get a fix ready before hitting
the other systems used in development and production.
2. Allows optimization of the process to reduce the
downtime and impact to the business. The update and
migrate tool, SUM’s DMO, provides a special feature which
allows repetition of the downtime for optimization.
• .
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 3

4. Target BW and HANA DB
• Recommended to always use the latest BW release/level for
the target system.
• The target HANA system has been installed as per SAP
requirements.
• The target support package should be the latest, and ideally
installed with the DSP (datacenter service point).
• The capacity should meet the result from the sizing report -
discussed at later stage.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 4

5. BW Housekeeping/data clean-up
Similar to preparing a BW system for upgrade and/or Unicode
conversion, reduction of the data volume should be done -
normally referred to as BW housekeeping tasks. This will
reduce the data to be exported from the source system and
imported to the target DB. This will reduce the downtime of
the system during the upgrade, and it also reduces the
capacity requirement of the target HANA DB.
The normal housekeeping/clean-up tasks involves the BW
functional team, which includes
• PSA reduction and change log
• Infocube compression
• Deletion of temporary objects
• Deletion of statistics data
In addition, the ‘SAP BW Migration Cockpit’ includes a
Housekeeping section for common housekeeping tasks.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 5

6. SAP BW Migration Cockpit for SAP HANA
SAP provides the BW migration cockpit program, which is the
main entry point to all the tools for the BW to HANA
migration preparation. It also includes some post-task items
(e.g. ASU, Down-sizing – Near-line Storage, extended tables)
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 6

7. Migration Cockpit
• From the cockpit, all the tools needed for can be executed (e.g.
sizing, list program codes that can be optimized for HANA). Also
incorporated previous tools like ASU, normal housekeeping tasks,
BW Checks.
• Each tab has different tasks within it. If you hover to the right side
‘Documentation’, it provides either
• OSS note which contains the ABAP program to be uploaded to perform
the check, and ‘how-to-guide’, e.g. BW Checklist for SAP HANA
• Link to the relevant SAP HELP page
• The cockpit is installed by creating ABAP program
ZBW_HANA_MIGRATION_COCKPIT from OSS note 1909597, which
also contains the guide ’SAP Migration Cockpit’.
• The document SAP First Guidance - BW Housekeeping and BW-
PCA covers some of the major checks/tools
• HANA checklist
• Sizing Check
• Note Analyzer
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 7

8. Checks tab
This section has several items
Upgrade Paths
• Install ABAP program from
OSS note 2296693, which
also contains the
documentation.
• Sample report below – note
that DMO will be used
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 8

9. Checklist Tool
• Install the program
ZBW_HANA_CHECKLIST
from OSS note 1729988 –
which also contains two
documents:
• How to … Checklist Tool for
SAP BW powered by SAP
HANA
• SAP BW powered by SAP
HANA Checklist Tool
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 9

10. Sample BW Checklist Report
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 10

11. Other Checks
The lower screen contains more checks. The Documentation
tab points to the SAP Help page.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 11

12. BW (consistency) Checks
These are standard BW
transactions/programs.
• BW Object Checks – this is
transaction RSRV
• BEx Query Check – this runs the
ABAP program
ANALYZE_RSZ_TABLES
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 12

13. Planning Function Check
This run program RSPLS_PLANNING_HDB_ANALYSIS – it
checks if a planning function can be executed in memory, with
the following default screen
• ‘How to check whether a Planning function or
Disaggregation in PAK is executed in Memory’ ← provides
very good explanation on this subject.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 13

14. Sizing
This tab contains several sections
Sizing Tool
• The tool provides an estimated size of eventual BW system
in the HANA database.
• Note that the figure from this report does not include other
memory requirements within HANA (e.g. calculation space).
• OSS note 2296290 provides more detail/guide on how the
sizing program works, prerequisite, how to run it, and how
to read the summary report. One of the attached guide also
provide overview on HANA BW Scale Out.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 14

15. Sizing Tool
• Provides several
options/factors/simulation
• Output report is written into
a file, into the work
directory
The report has several
sections:
• Source DB contents, e.g. size
of different table types (e.g.
infocubes, PSA)
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 15

16. Sizing Tool Sample Report
• Minimum Sizing
Requirements - with
recommended number of
nodes
• Sizing Details
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 16

17. Iterative Sizing
• Run the sizing tool several
times with or without selecting
any option to compare results
of the clean-up/data reduction
activities:
• Change the filename of the
output result for comparison
purposes.
• Result of each table are shown
in the report’s Table Details,
broken down by row/column
types, and for each table -
estimated ABAP and HANA size.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 17
• There is also an CSV file
containing the Table Detail, for
easier comparison, containing
total_size, ABAP size, HANA
size.
• Note that some of options can
only be implemented after the
migration, e.g. Dynamic
Tiering. However, it is a good
idea to run this several times
with several options to see the
impact if they are done after
the migration, i.e. ‘what if’.
• Reference : OSS note 1736976
– Sizing Report for BW on
HANA, which contains two
document on sizing and Scale-
out.

18. Future Growth Simulation
• This option allows you to extrapolate the size based on
growth factor or absolute number.
• With the example above, the report will show minimum and
recommended size per year
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 18

19. Non-Active Data, Dynamic Tiering
• This options are another ‘what-if’ scenario, e.g. what if
dynamic tiering is used.
Non-Active Data
• This is in relation to the new ‘multi-colored’ - refer to blog
SAP BW on HANA : Data Classification (HOT/WARM/COLD)
• If selected, there will be a section ‘Non-Active data’ in the
report.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 19

20. Dynamic Tiering
• BW on HANA introduced the multi-temperature data. Briefly,
data are classified as:
• HOT data – accessed very often, should stay in HANA memory
• WARM data – infrequent access, using HANA dynamic tiering (i.e.
extended storage, extended table), e.g. data more than 2 years old
• COLD data – sporadic/infrequent access, using Near-line Storage
(NLS)
• PSA tables and Change Logs are considered ‘non-active
automatically’ – Reference OSS Note
• References:
• ‘Big Data Management in HANA BW.pdf’ from OSS note 1983178
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 20

21. Dynamic Tiering - Brief
• Dynamic Tiering (aka extended storage) is another way of
reducing HANA memory footprint by moving some data into
Dynamic storage server.
• For example, data from an infocube which are more 12 months
old can be moved to the dynamic storage, hence only the current
year’s data are the only ones that occupy the HANA memory. This
is done by
1. defining another table with the same definition as the
current table, with additional ‘extended storage’ clause.
2. moving the data from the current table to the ‘extended
table’
3. creating a view with a join of the current table and the
‘extended table’. If an SQL issue a select SQL which include
data from the extended table, then it is retrieved from the
‘extended storage’ into the Dynamic Tiering server’s
memory - but still does not occupy HANA memory
• References:
• SAP HANA Dynamic Tiering for Using Extended Tables
• OSS note 1983178 - HANA Dynamic Tiering
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 21

22. Memory Configurations
• Allowed Memory Configurations
• Down-sizing (configuration) – these are post-task activities
• The document points to SAP Help portal on the subjects of NLS and
Data Archiving
• Down-sizing (execution)
• The ‘Move to Extended Tables’ document refers to
• OSS note 2557636 – conversion of PSA and write-optimized DSO in
SAP-HANA extended tables which also contains document ‘Changing
the Multi-Temperature Category of BW objects’.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 22

23. Housekeeping
The tasks in this section are
to be used in conjunction
with the ASU tool (under
Migration). This has 2
sections:
• Housekeeping Automation -
this is transaction STC01
• Housekeeping Tasks
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 23

24. Migration
ASU Toolbox:
• Refer to 1000009 - ASU
Toolbox 2008, upload the
relevant DMO task list
(ASU_BW_70x_75x_DMO_3
.zip). As in other upgrade,
there are pre and post-
tasks.
• There are other tools on this
tab, but note below.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 24

25. WHM
• This contains the
‘Transformation Finder’. There
are several options/selection
on the transformation
• Install ABAP program
ZBC_TRANSFORMATION_FIND
ER from OSS note 1908367 ,
which also contains the ‘SAP
BW Transformation Finder’, a
how-to-guide.
• The following blog provides a
good understanding of the
transformation and links to
various blogs on this subject,
HANA Transformations
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 25

26. Optimization
• Program to scan custom ABAP codes for potential
optimization for HANA.
• Install the ABAP program from OSS note 1847431, which also
contain the how-to-guide.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 26

27. Next – SUM DMO and Migration
• Now that we have prepared the source BW system, we are
ready to proceed with SAP SUM (Software Update Manager)
using DMO (Database Migration Option) to carry out the
upgrade and migration of the BW system from anyDB to BW
on HANA.
• Stay tuned for the next section DMO and Migration.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 27

28. • Any Questions?
• Contact Info:
Linh Nguyen linh.nguyen@itconductor.com
Terry Kempis terry.kempis@itconductor.com
Let
itconductor.com
@itconductor