How to Upgrade to SAP BW 7.

5 on SAP HANA
— Potential Pitfalls and Tried and True
Instructions for Success

Dr. Bjarne Berg

PwC
Produced by Wellesley Information Services, LLC, publisher of SAPinsider. © 2016 Wellesley Information Services. All rights reserved.
What We’ll Cover

• SAP BW 7.5, edition for SAP HANA vs. SAP BW 7.5 on SAP HANA
• New enterprise data warehousing capabilities
• Hardware and landscape deployment options
• The DMO and the logical upgrade approach
• Wrap-up

1
 There Is a Difference Between SAP BW 7.5 “Powered by” and
“Edition” for SAP HANA

• BW 7.5, edition for HANA allows

you to develop objects faster
without having to use many of
the old objects from BW 3.x and
7.0/7.3/ 7.4
• This allows you to run BW in a
much more simplified way and use
only HANA-optimized objects
2
Why SAP BW 7.5, edition for SAP HANA?

 Simplified administration
 Faster development time
 Easier to maintain by
having less replicated
objects and data
 Smaller HANA memory
footprint
 Better modeling interface
in Eclipse
 Centralized development
and admin interface

3
SAP BW 7.5, “edition for SAP HANA” and “on SAP HANA”

• As you plan to move to SAP BW 7.5, you can still leverage the older objects, but long-
term you should migrate to the new BW 7.5, edition for HANA objects

4
 SAP BW 7.5, “edition for SAP HANA” — Compatibility Mode
• Administrative tasks are currently
maintained in the Warehousing
Workbench as is some objects, such
as DataSources
Technical BW requirements for
add-on “BW, edition for SAP • If you install add-on 1.x the system is moved to a
HANA” (SAP Note: 2285440)
BW, edition for HANA – pre-
requisites/installation/ de-
Installation/Update
(SAP Note: 2246699)
Date New Release
October 23rd, 2015 First release of BW 7.5
November 23rd, 2015
ServicePack 1 released and BW 7.5 supported for
production systems
February 29th, 2016 ServicePack 2 and BW Edition for HANA released
ServicePack 3 for BW released with enhanced admin
20162016
April 30th,
and modeling features
Source: Roland Kramer, SAP
July, 2016 Planned release date for new feature Pack for BW 7.5
* Source: Roland Kramer, SAP SE 2016
“Compatibility Mode” to allow the migration to new objects.
After that, the BW system can be switched from “Compatibility
Mode” to “Operation in B4H Mode” (if you have problems, you
can switch back to “Compatibility Mode”).
5
Getting to SAP BW 7.5, edition for SAP HANA

• For companies with BW 7.3 or 7.4

on HANA, or those who have not yet
migrated to HANA, it makes sense to
upgrade and migrate to BW 7.5 on
HANA first, and then migrate to the
new objects

• For those starting with a new

implementation, it makes sense to start
directly with BW 7.5, edition for HANA
and only use the new simplified and
faster objects
6
What We’ll Cover

• SAP BW 7.5, edition for SAP HANA vs. SAP BW 7.5 on SAP HANA
• New enterprise data warehousing capabilities
• Hardware and landscape deployment options
• The DMO and the logical upgrade approach
• Wrap-up

7
Simplifying Source Connectivity Options

• SAP BW 7.5 on HANA will consolidate

connectivity options so that:
 Operational Data Provisioning (ODP)
will be used for SLT and SAP source
systems
 HANA source system will be used for
other file system and database
connectivity

While the current source system connectivity

option are still available SAP is working on
simplifying and consolidated HANA objects.
8
 Advanced DataStore Object (ADSO) — New in SAP BW 7.4

• This new ADSO can be used to merge InfoCubes and

DSO into simpler data architectures, and the ADSO
can have up to 120 key fields

• The new table structure in ADSOs means that the

management and performance of frequent data
loads is also improved

• In the new SAP BW 7.5 you can also combine

InfoObjects and field-based modeling, while
leveraging SID entries can be used for query
optimization
In many cases you can even change
the usage scenario of Advanced
DataStore Objects without having to
delete the data
9
Advanced DataStore Object — New in SAP BW 7.5

• New migration tool that allows you to migrate older

BW objects to ADSOs
• ADSO support for planning and NLS
• Improved delta calculations for non cumulative key
figures (useful for areas such as inventory,
headcount and more)
• More dynamic tiering support for change logs and
data activation

SAP has said it is planning to add streaming

options in real time to the ADSO in the future
(source: Lothar Henkes, SAP SE)

10
 Enhanced CompositeProvider in SAP BW 7.5

• New improvement for BW 7.5

includes CompositeProviders
that now take advantage of the
performance improvements
introduced in HANA SP10 and
therefore executes faster

• You can also group similar

output structures for easier
access
SAP is working on adding the support for temporal joins
• In BW 7.5 you can also convert in CompositeProviders. This may allow customers to
existing CompositeProviders and completely remove the need for InfoSets.
BW MultiProviders automatically
11
 New Features in SAP BW 7.5 — Query Designer in Eclipse

• Most BEx query

developers will
find this
interface easier
to use and can
make the
transition
without the
need for major
re-training

12
 New Workspace Query Designer in BW 7.5

• In the new Workspace Query Designer

you can now let key business users
upload and merge data in queries
with local and BW data

• It leverages the data authorization

in BW

• To create SAP BW Workspaces, a

business user needs to have the role
SAP_BW_WORKSPACE_DESIGNER
assigned to them
Planned for future: Planned integration
into SAP BI front ends (BI Design Studio
Integration, Analysis Office)
13
 BW 7.5 and Near-Line Storage (NLS)

• NLS support has been available for InfoCubes with

non-cumulative key figures in BW 7.4 since 2014

• In BW 7.5 you now can:

 Use specific join types: CompositeProviders can
now use ADSOs stored on NLS
 Use BW process type to create NLS DB statistics
by leveraging virtual tables
 Use NLS for ADSOs and also display reporting
value help from NLS (SAP Note 2215265)

14
SAP BW 7.5 Dynamic Tiering — Enhanced Support

• Dynamic tiering of data in BW has been available since

BW 7.4. This means that:
 Data that is infrequently used automatically gets off-
loaded to disk and thereby saving memory for more
important tasks
 Saves memory (and money) by moving traditional
write-optimized DSOs and PSAs to “warm” storage
• New BW 7.5 features:
 Data movement to dynamic tiering automatically as
remodeling tasks
 ADSO dynamic tiring support for change logs and
activations
As first introduced in HANA in 2015, BW 7.5 now takes more advantage of dynamic tiering, thereby
keeping more low usage data in BW on disk instead of memory (costs savings)
15
 Operational Data Provisioning

• You can distribute your data using OData capabilities

in BW 7.5

• You can even use OData for Delta data loads from
ADSOs in BW 7.5

• You can create access by generating an SAP

NetWeaver Gateway Service based on a data provider.
This can be used by other SAP and non-SAP
applications using standard HTTP/OData.

With OData, SDI, SDA, ODBC, JDBC, DBSQL and standard SAP
interfaces, SAP BW 7.5 on HANA is a truly open data platform
16
 SAP BW 7.5 — Smart Data Integration (SDI) on HANA

• New SDI features for BW

 Real-time streaming possible

 Real-time direct access, ETL

and replication from
traditional landscapes and
the cloud • BW can be a source system
using SDI
 Twitter, files and OData  HANA source systems in
support in SDA BW have unified
connections to SDA, SDI
and local HANA sources
(see SAP Note: 2175904)
17
What We’ll Cover

• SAP BW 7.5, edition for SAP HANA vs. SAP BW 7.5 on SAP HANA
• New enterprise data warehousing capabilities
• Hardware and landscape deployment options
• The DMO and the logical upgrade approach
• Wrap-up

18
Hardware Options 2016 Onward

IBM Power 880

19
 Key Hardware Options 2016 Onward
CPU
Memory Target usage
Intel Ivy Bridge Intel Haswell
Vendor System Max Number CPU
Notes: (RAM) and Type
EX E7 15 Cores EX E7 18 Cores
(2014) (2015)
Speed
Scale- Scale- Business
out up Suite

1. All POWER8
bullion S2 512-1536 GB 2 x 8890v3 x 2.5 Ghz x x
Bull SAS bullion S4 1024-3072 GB 4 x 8890v3 x 2.5 Ghz x x

servers from bullion S8

UCS B260 M4
2048-6144 GB
512-1536 GB
8 x 8890v3
2 x 4890v2 x
x 2.5 Ghz
x
x
x
x
x
IBM are now Cisco
UCS B460 M4 1024 GB 4 x 4890v2 x 2.8 GHz x
UCS C460 M4 128-3072 GB 4 x 8890v3 x 2.5 Ghz x x x
also certified to UCS C880 M4 2048-6144GB 8 x 8890v2 x 2.8 Ghz x x x

run HANA Dell PowerEdge R930

PQ 2400 E/S/L
128-3072 GB
128-1024 GB
4 x 8890v3
4 x 8890v3
x
x
2.5 Ghz
2.5 Ghz
x
x
x
x

2. New Intel Fujitsu 128-6144 GB 8 x 8890v3

PQ 2800B2/E2 x 2.5 Ghz x x
RX4770 M2 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x

Broadwell HP
CS-500
CS-900
128-3072 GB
1024-12288 GB
4 x 8880v3
8 x 2890v2 x
x 2.3 Ghz
2.8 GHz
x
x
x
x
x
x
processors are Hitachi CB520X B2 256-6144 GB 8 x 8880v3 x 2.3 Ghz x x x

now emerging
FusionCube E9000 512-1024 GB 4 x 4890v2 x 2.8 GHz x
Huawei RH5885H V3 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x x

with 20-24 RH8100 V3

Flex x880 X6
128-6144 GB
128-6144 GB
8 x 8880v2
8 x 8890v2
x
x
2.5 Ghz
2.8 Ghz
x
x
x
x
x
x
cores Lenovo x3850 X6 128-3072 GB 4 x 8880v3 x 2.3 Ghz x x x
x3950 X6 512-6144 GB 8 x 8880v3 x 2.3 Ghz x x x
NEC Exp. 5800/A2040b 128-2048 GB 4 x 4890v2 x 2.8 GHz x x
Silicon Graphics UV 300H 256-6144 GB 8 x 8890v2 x 2.8 Ghz x x
Unisys Forward! 4150-B 128-3072 GB 4 x 4880v2 x 2.5 GHz x 20
x
Key Cloud Options

21
HANA Sizing Tool for Existing BW Implementations

Using the BW Automated Sizing Tool in the Migration cockpit

22
 HANA Sizing Tool for Existing BW
Implementations (cont.)
To increase speed, you can
suppress analysis tables
SAP has an updated tool that generates a with less than 1 MB size
report significantly better for sizing SAP BW
than using the QuickSizer

This tool should be used by all existing BW The higher

implementations for sizing (QuickSizer is only precision you run
the estimate at, the
for new implementations) longer the program
is going to run
This program takes into consideration existing
databases, table types, and includes the
effects of non-active data on the HANA system
With 8 parallel processors and 10TB database, it is not
unusual to see 4-5 hours runtime
23
 SAP BW on HANA Automated Sizing Tool

Since timeouts are common when running the sizing

program, you can temporarily change the parameter
in rdisp/max_wprun_time to 0 in BW transaction
RZ11. Finally, you estimate the growth for the
system as a percentage or as absolute growth.

The output is stored in the file you specified and

the file can now be emailed to hardware vendors
for sizing input and hardware selection

This program is referenced in SAP Notes 1909597

and 1736976 on the SAP Service Marketplace

24
Historical Landscape Deployment Planning Options

Deployment Virtualization MCOS MCOD Technical

Scenario Co-Deployment

HANA DBs Multiple Multiple One One

DB Schema Multiple Multiple Multiple One

Availability Supported for DEV Supported for DEV Defined by: Business Suite components
& QA systems & QA systems White List 1661202 for BW SCM and/or SCM co-
White List 1826100 for Suite deployed with ERP

25
Save Money with MCOD and MCOS

• You may not need separate hardware for sandbox and development environments
• Using Multiple Components One Database (MCOD) and/or Multiple Components One
System (MCOS) you can simplify the number of hardware environments you need
 SAP BW on SAP HANA
 SAP Finance and Controlling Accelerator for the material ledger
 ERP operational reporting with SAP HANA
 SAP Finance and Controlling Accelerator: Production Cost Planning
 SAP Rapid Marts
 SAP COPA Accelerator
 SAP Operational Process Intelligence
 SAP Cash Forecasting
 SAP Application Accelerator/Suite Accelerator
 Smart Meter Analytics In addition to custom developed datamarts, all items above can
run in an MCOD setup (see SAP Note 1666670 for more details)
26
MCOS Example from Real Company

MCOS

Note that the QA and Production system are kept the same size so that performance
tests are accurate and so that the QA system can be used for disaster recovery
27
New Deployment Option —
Multitenant Database Containers (MDC) Deployments

• A tenant database is a single database container

• You can save money by running multiple tenant

databases on a single HANA system

• MDC is supported for production systems

and you can backup for each tenant database

• You can manage resources such as memory

and CPU for each of the tenant databases

MDC became available with SP9 of HANA in 2015

28
 MDC Deployments Details

• MDC can be used in Platform & Enterprise Cloud

• For on-premise it can replace most MCOS
deployments and many of the MCOD scenarios
• There is no virtualization overhead, and scale-out
systems with standby nodes are supported
• You can use SQL to query across databases:
I.e., SELECT *
Individual database backups and FROM schema1.Customers AS tab1, db2.schema2.Customers as tab2
restores can be done from HANA Studio WHERE tab2.column2 = ‘Johnson’
NOTE: Attribute and analytic views must be converted to calculation views
to be used as remote tenant database objects

• A new privilege “Database Admin” allows you to separate admin access to each database
• You can convert a HANA system to MDC, but it cannot be converted back
(command: hdbnsutil –convertToMultiDB)
29
What We’ll Cover

• SAP BW 7.5, edition for SAP HANA vs. SAP BW 7.5 on SAP HANA
• New enterprise data warehousing capabilities
• Hardware and landscape deployment options
• The DMO and the logical upgrade approach
• Wrap-up

30
Optional: The SAP_BW_HOUSEKEEPING Task List

• If you are on 7.0 SP32 of higher, you can generate an SAP BW Housekeeping tasks list
and get automated help in cleaning the system weeks before upgrading it

1. Check BW metadata with DDIC 7. Re-assign requests written into the incorrect PSA partition
2. Delete RSTT traces 8. Verify DataSource segments assignment to PSA
3. Delete BW statistical data 9. Deletes the entries no longer required in table RSIXW
4. Delete Aggregate data via deactivation 10. Clear all OLAP Cache parameters
5. Ensure partitioned tables are correctly indexed for PSA 11. Repair InfoCube fact table indices at Data Dictionary level
6. Ensure request consistencies in the PSA 12. Reorganize and delete bookmark IDs and view IDs

You first have to install the program from SAP Note 1829728 before you can
generate the SAP_BW_HOUSEKEEPING task list using tcode STC01 31
Optional: The SAP_BW_BEFORE_UPGRADE Task List

• If you are on 7.0 SP31 or

higher, you can generate an
“SAP BW Before the Upgrade
task list” and get help in
preparing the system for the
upgrade

• The more of these tasks you

complete, the faster the
upgrade may proceed since
you are reducing size and
complexity, while assuring
You first have to install the program from SAP Note that your system is ready for
1734333 before you can generate the the 7.5 upgrade
SAP_BW_BEFORE_UPGRADE task list using tcode STC01
32
Optional: Pre-Steps: BI Content Consistency Checks
• If you suspect inconsistency in the BI content,
or are planning to deploy new BI content, you
can run the BI Content Analyzer. This can
be as a transparent table or loaded to a DSO
(tcode RSBICA)
• The automated BI Content Analyzer Checks include:
 Inactive transfer structure checks

 List of InfoObjects without an InfoObject catalog

 Inconsistent roles check

 Routines that refer to fixed, programmed structures
 Query elements with duplicate GUIDs
 Several object collection errors
To help plan any testing, you can also get a list of
where the objects in your SAP NetWeaver system
are used (SAP Note: 28022)

 Several object status checks

 Many checks for inconsistent naming conventions

33
 Pre-Planning: BEx 3.5 Query Designer Is Obsolete

• BEx Query Designer 3.x is obsolete and not

supported. The runtime and tools from SAP BW 3.5 are
not available in version 7.5.

• SAP has created a tool that checks your system and

will let you know what old query features you may be
using that are no longer supported. The check tool can
be found in SAP Note 1911469.

• More information on BEx 3.5 can be found in SAP Note

1932461

You can find step-by-step help to migrate your old BW BEx to 7.x in the “cookbook note” 1807522
34
BW to HANA Readiness Check
You can run the BW to HANA readiness check found
in the HANA migration cockpit of your BW system

35
BW to HANA Readiness Check — Findings — P1

This is a real example of typical

checklist findings at a company

Yours may differ, but having some

items flagged is common and a
plan should be developed to
address these

36
BW to HANA Readiness Check
Findings — P2

There are some steps that have

to be completed before the
migration can occur

The precheck program outlines

these

37
Other Mandatory Tasks and Gotchas with BW 7.5

• Some companies did not do the recommended security migration when upgrading to BW 7.0.
They now have to migrate to the “new” analysis authorization concept. The old 3.x is no
longer supported.

• Unicode conversion was also strongly recommended with the BW 7.0 upgrade, but many
companies did not compete that either. Now it is required. For non-unicode compliant
systems, you may have to go to BW 7.4, and do the Unicode conversion during that upgrade,
before moving to BW 7.5.

• The maximum length of characteristic values has been increased from 60 to 250 characters.
This can cause issues with key fields that are also assigned to this domain (RSCHAVL),
since the max field length may be exceeded. (Look in SAP Note 1879618 to avoid issues with
this). Since this domain uses the data type “SSTRING” you should also test any custom
coding using this data type.
38
 Useful Hints for Older 3.x Systems

• If some of the InfoSets become inactive, you can still use the program RSQ_ISET_MASS_OPERATIONS
to activate all InfoSets

• If you are still on 3.5 queries or older versions (e.g., 3.1c, 3.0B), consider running the program
RSR_GEN_DIRECT_ALL_QUERIES to regenerate all queries in the system into the 7.0 release

• BW 7.0 had a new transformation concept that replaced transfer and update rules, but not all
companies have migrated

• To do so now, you can convert the DataSources and the Persistent Staging Area to the new DTP
process (see SAP Note 906789). (Note: The PSA becomes less important in 7.5 when using Operational
Data Provisioning [ODP], since it does not use the PSA). To test the conversion of the DataSources you
can also run: RSSM_CREATE_REQDONE_FROM_SEL; RSSM_HASH_ENTRIES_CREATE for all
requests; RSSTATMAN_CHECK_CONVERT_DTA; RSSTATMAN_CHECK_CONVERT_PSA.

39
BW InfoCube Data Classes That Are Incorrectly Assigned

• DDART data classes may have been set up in your system that don’t follow standard
naming conventions (see SAP Note 46272)

• These data classes were assigned to InfoCubes in the RSDCBE transaction. To correct a
data class assignment, you should use the report RSDG_DATCLS_ASSIGN

• During the upgrade, if you don’t assign them correctly, these classes are lost and tables
that are generated for the InfoCube may not be correctly activated

To ensure that all DataSources web services run correctly after the upgrade, you could
run RSDS_DATASOURCE_ACTIVATE_ALL after the upgrade (see SAP Note 1494272)

40
Pre-Steps Before Staring SUM (Software Update Manager)
• To start the process, you will need some disk space for the SUM tool, the download directory, the Trans directory,
as well as some space for the shadow system that will be created during the upgrade
• SAP recommends that you have at least the following disk space available in your source system:

 20GB for the temporary download directory and the DIR_TRANS directories (each)

 8GB for the SUM directory

 The size for the shadow system is equal to the size found in these directories:
 /usr/sap/<sapsid> (Windows systems)

 /usr/sap/<SID> (IBM i systems)

 /usr/sap/<sapsid> (UNIX systems)

During your upgrade, the SUM will create a “shadow” system

for your non-data files and you will need some space for this

41
 Upgrade Decision: Low, Standard, and High Resources
• A major decision is: Are you going to minimize the
system downtime or do a low resource upgrade? The
trade-off is between using more system resources or
downtime.

• In the “standard” upgrade, you create a shadow system

while the BW system is still operating. You turn off any
archiving to make sure you do not miss any data and
do your system backup right before the downtime
starts. Therefore, you can do much of the upgrade
before the downtime (shorten the outage).
When possible, you should consider
• In a very high system resource upgrade, you also use using the single system option, thereby
making the upgrade and migration much
a shadow system, but imports are much faster and you
faster (may require more outage).
can keep archiving (may create large logs), but
downtime starts earlier.
42
 Shadow System During the Upgrade
Application Data

You use a shadow system to SAP NW

Target Release

reduce the system outage BW 7.5 XPRA Import &

Data Conversion
Target Release
System

- High system resource – locks

system in the REPACHK2 phase Application Data

Source Target
- Standard system resource – locks Shadow Release Release

system in the REPACHK2 phase System

- Low system resource – locks Source Release

System
Target Release
System
system in the LOCKEU_PRE phase SPDD

Shadow System Installation

NOTE: During the lock, only certain types

Application
of BW objects for which changes are Data Target
Release
explicitly allowed can be changed (see BW 7.0
SAP Note 337950). (or higher)
BW 7.x
43
 Step 1: Hardware Install, Dev Copy, and Sandbox Upgrade
BW 7.x BW 7.x BW 7.x BW 7.x
Sandbox Dev. Box QA Box Prod Box
• In this example, we are installing new hardware.
This creates a lot of flexibility and less project risk!
1

• First, we copy the BW 7.x development box to the new

hardware BW 7.5
Sandbox

• Second, we upgrade the new sandbox in

a controlled manner and document all activities

We want to create a repeatable process, so no ad hoc activities are allowed. Remember, extra
time has to be set aside for notes research and unforeseen issues.
BENEFITS: This is also a test run for upgrading the development box (!), thereby reducing the
upgrade risk. After the upgrade, we also get a refreshed sandbox environment.
44
 Step 2: Development Box Copy and Upgrade
BW 7.x BW 7.x BW 7.x BW 7.x
• Now we have to freeze all development activities Sandbox Dev. Box QA Box Prod Box

1
• Normally, the work in the 7.x dev box is 2

transported to QA for testing and the dev box

is locked BW 7.5
Sandbox
BW 7.5
Dev. Box

• Using the upgrade “runbook” and all steps collected and written during the sandbox upgrade,
we are upgrading the new development box. This is intended to be a structured approach that
is repeatable.

• The developers participate in in-depth testing of the new 7.5 dev box
BENEFITS: The outage of the development box occurred after the sandbox upgrade and the development outage is
minimized. This is also the second time we have upgraded the development box, so any issues should be well known.
45
 Step 3: Production Box Copy and QA Upgrade
BW 7.x BW 7.x BW 7.x BW 7.x
Sandbox Dev. Box QA Box Prod Box

• We copy the production environment to the

development box after all testing in the QA has 1
2 3
been completed and all the objects have been
transported to the production system
BW 7.5 BW 7.5 BW 7.5
Sandbox Dev. Box QA Box

• Notice that no copies of Sandbox or

QA are made. Instead, we get to upgrade the development box and the production box “twice.”

• This is a significant risk mitigation strategy, but requires that transports and client-dependent
objects are switched back on in the new Sandbox and QA systems
BENEFITS: This approach turns the QA upgrade into a real “dress rehearsal” for the production box upgrade. Also, since
we are switching the hardware, the risk to the upgrade is minimal (BW 7.x prod is not taken offline until after the upgrade).
46
 Step 4: Production Box Copy and QA Upgrade
BW 7.x BW 7.x BW 7.x BW 7.x
• You are now ready for the cutover weekend Sandbox Dev. Box QA Box Prod Box

2
• The best timing is to start the production box 1 3 4

on Thursday evening after the BW system has

completed data loads. A full backup is taken. BW 7.5 BW 7.5 BW 7.5 BW 7.5
Sandbox Dev. Box QA Box Prod Box

• The system is unavailable on Friday and is

completely upgraded by Saturday 6 am

• Consider the time it takes for security

conversion, unless already Plan for having Basis and technical people working the night from Thursday to
done in the 7.0/7.3/7.4 upgrade Friday and possibly to Saturday, depending how long the upgrade takes
47
 Database Migration Option (DMO)

• During the upgrade from BW 3.x to version

7.0 many companies decided not to
complete Unicode conversions, security
conversion and other recommended steps

• Since these are now required for the BW 7.5 and the subsequent migration to HANA, some
companies are planning first to do the upgrade and then do a migration project. That is a
mistake! With the database migration option tool you can accomplish both the 7.5 upgrade
and, often, all the HANA migration in one step. DMO is a key option in the Software Update
Manager (SUM), for those that want to migrate to HANA.

NOTE: If you are already on BW 7.3/7.4 on HANA, you must have at least
HANA SP10 before migrating to 7.5 using DMO
48
 Software Update Manager — SP 16
• To do a migration of your existing SAP BW system, you should first look at the Product
Availability Matrix (PAM) on the SAP Service Marketplace
• The DMO option support for SAP BW 7.5 was recently released, but required SUM
ServicePack 16 (or higher). In SPS 16, the brand new “Zero downtime option” (ZDO)
is available on request

Number Good reference notes to pre-read before upgrade

2198483 DMO with SUM 1.0 SPS 16
2197897 Central Note: SUM 1.0 SPS 16 (Features)
2096202 Row store/column store inconsistencies after system migration with DMO
1968508 Release Change & Single Code Page Conversion to Unicode with DMO
1959955 SUM upgrade/migration to HANA fails during HDB_MIGCONFIG
1908075 BW on SAP HANA: Table placement and landscape redistribution
1813548 Database Migration Option (DMO) for Software Update Manager
1799545 Using DMO of SUM for SAP BW systems
1784377 Checking pool tables and cluster tables
49
Creating a DMO Migration Runbook

• The best way to approach this is to start with

the sandbox system and create a runbook with
step-by-step lists on how each problem and
software task are created. It is not unusual to
have a 90-100 page word document with
screenshots and documentation at the end of
this first migration.

• The “runbook” is the key to success. You should build

Speed is not important in the first
sandbox migration. The creation of a
repeatable process is far more important.
on this when you migrate to the Development and
then the QA and the Production systems
• DMO also supports Unicode conversions to BW 7.4
50
 DMO and Unicode (May Have to GOTO 7.4 Before 7.5)
5.0 Unicode Preparations 13
• For those doing a Unicode conversion, there are many additional 5.1 Check consistency between DB & DD
Create table CLU4 & VER_CLUSTR in the database for the sake of
13

steps. We first need to check what is already in-place. Thankfully, 5.2

5.3
Unicode checks in DMO
Re-check consistency between DB & DD
13

14
SAP provides programs to help you with these to check the config. 5.4
5.5
Run report UCCHECK
Conversion of customer-defined code pages
14
15
5.6 Pre-conversion correction of table data BDCP* 16
5.7 Consistency check for cluster tables 17
5.8 Check installed langauges 18
5.9 Check tables TCPDB and TCP0I 18
5.10 Run Program TWTOOL01 to find Match Code IDs 18
5.11 Run report RSCPINST 19

5.12 Run report TERM_DELETE_INCORRECT_CHARSET SAP Note 1280494 19

5.13 Re-run report TERM_DELETE_INCORRECT_CHARSET 20
5.14 Check table DBTABLOG SAP Note 1255556 21
5.15 Delete the contents of ADR tables as described in OSS Note 673941 21
5.16 Remove temporary objects SAP note 449891 22
5.17 Delete QCM invalid temp tables 22
5.18 Run report RADNTLANG SAP Note 480671 23
5.19 Reset nametab buffer after RADNTLANG report 24
5.20 Database statistics update 24
5.21 Check Nametab 24
5.22 SPUMG 25
5.23 Upload newest exception tables according to OSS Note 996990 25
5.24 Start additional preparation steps 26
5.25 Continue with transaction SPUMG 27
5.26 Check language lists 27
5.27 Set global fall-back codepage 28
5.28 Initialise the worklist 28
5.29 Schedule Worker jobs 29
5.30 Check status of consistency check 30
5.31 Update worklist 30
5.32 Nametab Handling 31
5.33 Generate statistics for active nametab tables 31
You can get this report by running the report UCCHECK and seeing the 5.34
5.35
Create the Unicode nametabs
Run UMG_SHOW_UCTABS
31
33
installed languages in the source system by using the transaction SMLT 5.36
5.37
Generate statistics for active nametab tables
Run additional downtime steps
34
51
34
 Staffing a HANA Migration Project — Small Team
Area Role Staff area Jun Jul Aug Sep
System Profile Project manager Company 50% 50% 50% 50%
Raw data size: 2.7 TB Core
BW Basis Support
HANA Basis Support
Company 75% 75% 100%
Consultant 100% 100% 100%
75%
75%
team
Complexity: Medium HANA Optimization developer Consultant 100% 100% 100% 50%
HANA Test & resolution lead Consultant 100% 100% 100% 50%
DataStores: 87 Test
Functional Tester - Finance & COPA Business 25% 50%
Functional Tester - Sales and Distribution Business 25% 50%
InfoCubes: 63 team
Functional Tester - MFG & Sourcing Business 25% 50%

Queries: 409
• The test team was dedicated for 9 weeks during the migration of QA and Prod
environments
Duration: 14 weeks
• The test team from the business was comprised of experienced users of the
Environments: 4+1
BW system and needed minimal training
Risk aversion: Medium
Other usage: Integrated • HANA optimization of InfoCubes was done for SD reports only in this
Planning migration

This organization was using BWA 7.0 and retired it as part of the HANA
migration, thereby saving licensing costs for this platform
52
Staffing a HANA Migration Project — Medium Team
System Profile Area Role Staff area Jan Feb Mar Apr May
Project manager Company 25% 25% 25% 25% 25%
Raw data size: 5.6 TB Core
Technical project manager Consultant 100% 100% 100% 100% 100%
Project Advisor Consultant 20% 20% 20% 20% 20%
Complexity: Medium
team
BW / HANA Basis Support Company 75% 100% 100% 100% 75%
HANA Basis Support Consultant 100% 100% 100% 100%
DataStores: 439 Test Team: BW Technical test lead Company 75% 100% 100%
Finance Functional Tester - Finance Business 50% 50%
InfoCubes: 603 Test Team: HANA Test & resolution lead Consultant 75% 100% 100%
SD & Commissions Functional Tester - Sales & Distribution Business 50% 50%
Queries: 1,300+ Test Team: BW Technical tester Company 75% 100% 100%
(incl. BOBJ) Other Areas Functional Tester - Other areas Business 50% 50%

Duration: 18 weeks • The testing of core queries in BEx and Web Intelligence was done by the
Environments: 4 business
Risk aversion: HIGH • The data reconciliation and process chain testing were done by dedicated
Other usage: None resources in each team

The team must be staffed with experienced resources. HANA training for team
members and hardware installs should be in place prior to project start.
53
 Staffing a HANA Migration Project — Very Large Team
System Profile Area Role Staff Mar Apr May June July Aug
Project manager Company 100% 100% 100% 100% 100% 75%
Raw data size: 38TB Technical project manager Consultant 100% 100% 100% 100% 100% 75%
BW Basis Support Company 75% 75% 50% 50% 100% 75%
Complexity: High
Core
HANA Basis Support Consultant 100% 100% 100% 100% 100% 75%
team
Project Advisor Consultant 20% 20% 20% 20% 20% 20%
DataStores: 1,300+ HANA Optimization developer Consultant 100% 100% 100% 100% 100%
Support team Representative Company 50% 50% 50% 50% 50% 100%
InfoCubes: 1,720+ Test Team:
BW Technical test lead Company 50% 50% 50% 100% 100%
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Queries: 2,600+
Finance and
Functional Tester - Finance Business 25% 25% 50%
BPC
Functional Tester - BPC Business 25% 25% 50%
BW Technical test lead Company 50% 50% 50% 100% 100%
Test Team:
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Duration: 5 mos Sales and
Distribution
Consultant Test team lead and Sales Business 25% 25% 50%
Functional Tester - Delivery Business 25% 25% 50%
Environments: 4 BW Technical test lead Company 50% 50% 50% 100% 100%
Test Team: HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Risk aversion: HIGH Manufacturing Consultant Test team lead and Sales Business 25% 25% 50%
Functional Tester - Delivery Business 25% 25% 50%
Other usage: APO, IP, BPC Test Team:
BW Technical test lead Company 50% 50% 50% 100% 100%
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Global
Functional Tester - PO and Spend Business 25% 25% 50%
Sourcing
Functional Tester - AP and Performance Business 25% 25% 50%
BW Technical test lead Company 50% 50% 50% 100% 100%
This assumed minimal additional Test Team:
HR and
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Functional Tester - HR Business 25% 25% 50%
functional optimization Planning
Functional Tester - IP Business 25% 25% 50%
54
 Last Hint: De-Clustering of Tables for Products
Based on SAP NetWeaver 7.5

• To take of advantage of the new

table structures of HANA,
pooled and cluster tables in
legacy databases are
declustered and depooled as a
default in SAP NetWeaver 7.5

You will have the option to keep the cluster and pooled tables if you want.
However, for the vast majority of customers this is a step that will simplify
table structures and increase speed in HANA
55
What We’ll Cover

• SAP BW 7.5, edition for SAP HANA vs. SAP BW 7.5 on SAP HANA
• New enterprise data warehousing capabilities
• Hardware and landscape deployment options
• The DMO and the logical upgrade approach
• Wrap-up

56
Where to Find More Information

• www.sap-press.com/sap-hana_3687
 Bjarne Berg and Penny Silvia, SAP HANA: An introduction (SAP PRESS, 2014).

• http://scn.sap.com/docs/DOC-70034
 Daniel Rutschmann, “BW 7.5” (SCN, January 2016).

 SAP BW 7.5 Frequently Asked Questions

• http://scn.sap.com/docs/DOC-68023
 Roland Kramer, “Update to SAP BW 7.5” (SCN, April 2016).

• http://sapexperts.wispubs.com/BI
 Ned Falk, “The Future of SAP BW: SAP BW 7.5, Edition for SAP HANA” (BI Expert,
March 2016).
• https://help.sap.com/nw75
 SAP NetWeaver 7.5 on the SAP Help Portal
57
7 Key Points to Take Home

• BW 7.5 on SAP HANA and BW 7.5, edition for HANA are different
• BW 7.5 has major benefits in terms of object simplification and faster development times
• A migration to BW 7.5 for older BW systems will normally be to BW on HANA first
• Unicode conversion is mandatory for BW 7.5 systems
• Migrations can be done in as little as 8-10 weeks for smaller and mid-sized systems
• Staffing should be a mix of test teams; strong HANA and BW skilled Basis people are
essential
• BW 7.5 removes many of the old “legacy” objects and simplifies modeling and query
development in the new Eclipse-based modeling interface

58
Your Turn!

How to contact me:

Dr. Bjarne Berg
bjarne.berg@pwc.co

Please remember to complete your session evaluation

59
Disclaimer
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP SE.

60