How to upgrade to SAP BW4HANA and BW

7.5 on SAP HANA — Potential pitfalls and

tried and true instructions for success

Dr. Bjarne Berg

PwC
What We’ll Cover
• Introductions
• BW 7.5 Edition for HANA Vs. BW 7.5 on HANA
• New enterprise Data Warehousing Capabilities
• Hardware and Landscape Deployment Options
• The DMO and the Logical Upgrade Approach
• Wrap-up

2
 There is a Difference Between BW 7.5 “Powered by” & “Edition” for 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

3
 Why SAP BW 7.5, edition for SAP HANA

 Simplified administration
 Faster development time
 Easierto maintain by having
less replicated object and
data
 Smaller HANA memory
footprint
 Bettermodeling interface in
Eclipse
 Centralized
development
and admin interface.
4
 SAP BW 7.5, ‘edition for HANA’ and ‘on 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

5
 SAP BW 7.5, ‘edition for HANA’ – Compatibility Mode
Date New Release
• Administrative tasks are currently October 23rd, 2015 First release of BW 7.5

maintained in the Warehousing November 23rd, 2015

ServicePack 1 released and BW 7.5 supported for
production systems
Workbench as is some objects, such as
February 29th, 2016 ServicePack 2 and BW Edition for HANA released
DataSources.
ServicePack 3 for BW released with enhanced admin
April 30th, 2016
and modeling features
July, 2016 Planned release date for new feature Pack for BW 7.5

Technical BW requirements for * S o urc e : Rola nd Kra me r, S AP S E 2016

AddOn "BW, edition for SAP

HANA“ (SAP Note: 2285440)
BW, edition for HANA - pre-
requisites/installation/ de-
Installation/Update (SAP Note:
2246699)
If you install Add-On 1.x the system is moved to a “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”).
6
Getting to SAP BW 7.5, edition for 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 staring 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

7
What We’ll Cover
• Introductions
• BW 7.5 Edition for HANA Vs. BW 7.5 on HANA
• New Enterprise Data Warehousing Capabilities
• Hardware and Landscape Deployment Options
• The DMO and the Logical Upgrade Approach
• Wrap-up

8
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.
9
 Advanced DataStoreObject (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

10
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 and headcount
and more).
• More dynamic tiering support for with 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)

11
 Enhanced Composite provider in SAP BW 7.5

• New improvement for BW 7.5 include

CompositeProviders that now take
advantage of the performance
improvements introduced in HANA
SP-10 and therefore executes faster.

• You can also group similar output

structures for easier access.

• In
BW 7.5 you can also convert
existing CompositeProviders and BW
SAP is working on adding the support for temporal joins in
MultiProvider automatically. CompositeProviders. This may allow customers to completely
remove the need for InfoSets
12
 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

13
 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.

• Tocreate SAP BW Workspaces, a business

user need 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)
14
 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:

 Using 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 (note 2215265)

15
 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 of low usage data in BW on disk instead of memory (costs savings).
16
 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 a NetWeaver

Gateway Service based on an 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
17
 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.
 Twitter, files and OData
• BW can be a source system
support in SDA using SDI
 HANA Source system in BW
have unified connections to
SDA, SDI and local HANA
sources (see note: 2175904)
18
What We’ll Cover
• Introductions
• BW 7.5 Edition for HANA Vs. BW 7.5 on HANA
• New Enterprise Data Warehousing Capabilities
• Hardware and Landscape Deployment Options
• The DMO and the Logical Upgrade Approach
• Wrap-up

19
Hardware Options 2016 Onward

IBM Power 880

20
Key Hardware Options 2016 Onward
Note:

1. Power8 servers from

IBM are now also
approved to run HANA

2. Also, new Intel

Broadwell processors
are now emerging with
20-24 cores

21
Key Cloud Options

22
HANA Sizing Tool for Existing BW Implementations
Using the BW Automated Sizing tool in the Migration Cockpit

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

This tool should be used by all existing BW

The higher precision
implementations for sizing (QuickSizer is only for you run the estimate
new implementations). at, the 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 24
 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 Service Marketplace

25
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 & QA Supported for DEV & QA Defined by: Business Suite components
systems systems White List 1661202 for BW SCM and/or SCM co-
White List 1826100 for Suite deployed with ERP

26
 Save Money with MCOD and MCOS
1. You may not need separate hardware for sandbox and development environments
2. Using Multiple Components One Database (MCOD) and/or Multiple Components One System
(MCOS) you can simplify the number of hardware environments you need
a) SAP BW on SAP HANA
b) SAP Finance and Controlling Accelerator for the material ledger
c) ERP operational reporting with SAP HANA
d) SAP Finance and Controlling Accelerator: Production Cost Planning
e) SAP Rapid Marts
f) SAP COPA Accelerator
g) SAP Operational Process Intelligence
h) SAP Cash Forecasting
i) SAP Application Accelerator/Suite Accelerator
j) 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)
27
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 as for disaster recovery
28
New Deployment Option –
Multitenant Database Containers (MDC) Deployments

APPLICATIONS
•A tenant database is a single database container
Application A Application B

• Youcan save money by running multiple tenant

SAP HANA databases on a single HANA system
System
• MDC is supported for production systems and you can
Database
backup for each tenant database
Tenant Tenant
Database Database • You can manage resources such as memory and CPU
for each of the tenant databases

MDC
MDCbecame
becameavailable
availablewith
withSP-9
SP-9ofofHANA
HANAinin2015
2015
29
 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 is supported
• You can use SQL to query across databases:
I.e., SELECT *
Individual
Individualdatabase
databasebackups
backupsand
andrestores
restores FROM schema1.Customers AS tab1, db2.schema2.Customers as tab2
WHERE tab2.column2 = ‘Johnson’
can
canbe
bedone
donefrom
fromHANA
HANAStudio
Studio 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)
30
What We’ll Cover
• Introductions
• BW 7.5 Edition for HANA Vs. BW 7.5 on HANA
• New Enterprise Data Warehousing Capabilities
• Hardware and Landscape Deployment Options
• The DMO and the Logical Upgrade Approach
• Wrap-up

31
 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 32
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 that your system is
ready for the 7.5 upgrade
You first have to install the program from SAP Note 1734333
before you can generate the SAP_BW_BEFORE_UPGRADE
task list using tcode STC01
33
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 To help plan any testing, you can also get a list of where
 Query Elements with Duplicate GUIDs the objects in your SAP NetWeaver system are used
(SAP Note: 28022)
 Several Object Collection Errors
 Several Object Status checks

 Many checks for Inconsistent Naming Conventions

34
 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
35
BW to HANA Readiness Check

You can run the BW to HANA readiness check found in the

HANA migration cockpit your BW system

36
BW to HANA Readiness Check – Findings – p1
Re
a lE
xa
mp
le

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

37
BW to HANA Readiness Check
Findings – p2
Re
a lE
xa
mp
le

There are some steps that have to

be completed before the migration
can occur.

The Precheck program outlines

these as:

38
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.

39
 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 (i.e., 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.

40
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 assure that all DataSources Web services run correctly after the upgrade, you could run
RSDS_DATASOURCE_ACTIVATE_ALL after the upgrade (see SAP Note 1494272)

41
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 equal to the size found in this
directory:
 \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 42
 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).

• Ina very high system resource upgrade, you also use a When
Whenpossible,
possible,you
youshould
shouldconsider
considerusing
using
shadow system, but imports are much faster and you can the
thesingle
singlesystem
systemoption,
option,thereby
therebymaking
making
keep archiving on (may create large logs), but downtime the
theupgrade
upgradeandandmigration
migrationmuch
muchfaster
faster(may
(may
require
requiremore
moreoutage).
outage).
starts earlier.

43
 Shadow System During the Upgrade
Application Data

You use a shadow system to SAP NW BW

Target Release

7.5
reduce the system outage
XPRA Import &
Data Conversion
Target Release
System

- -High
Highsystem
systemresource
resource––locks
locks
system
systemininthe
theREPACHK2
REPACHK2phasephase Application Data

Source Target
--Standard
Standardsystem
systemresource
resource––locks
locks Shadow Release Release

system
systemininthe
theREPACHK2
REPACHK2phasephase System

--Low
Lowsystem
systemresource
resource––locks
locks
Source Release
System
Target Release
System
system
systemininthe
theLOCKEU_PRE
LOCKEU_PREphase phase SPDD

Shadow System Installation

NOTE:
NOTE: during
duringthe
thelock,
lock,only
onlycertain
certaintypes
types Application
ofofBW
BWobjects
objectsfor
forwhich
whichchanges
changesare are Data Target
explicitly BW 7.0 Release
explicitly allowed can be changed (see
allowed can be changed (see (or higher)
note
note337950).
337950).
BW
BW7.x
7.x 44
 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! pl
e
1 x am
E
An
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:
BENEFITS:This
Thisisisalso
alsoaatest
testrun
runfor
forupgrading
upgradingthe
thedevelopment
developmentbox
box(!),
(!),thereby
therebyreducing
reducingthe
theupgrade
upgrade
risk.
risk.After
Afterthe
theupgrade,
upgrade,wewealso
alsoget
getaarefreshed
refreshedsandbox
sandboxenvironment.
environment.
45
 Step 2: Development Box Copy and Upgrade
BW 7.x BW 7.x BW 7.x BW 7.x
Sandbox Dev. Box QA Box Prod Box
Now we have to freeze all development activities
e
m pl
1 a
Normally, the work in the 7.x dev box is transported to 2 Ex
An
QA for testing and the dev box is locked
BW 7.5 BW 7.5
Sandbox 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:
BENEFITS:The
Theoutage
outageofofthe
thedevelopment
developmentbox
boxoccurred
occurredafter
afterthe
thesandbox
sandboxupgrade
upgradeand
andthe
thedevelopment
developmentoutage
outageisisminimized.
minimized.This
Thisisis
also
alsothe
thesecond
secondtime
timewe
wehave
haveupgraded
upgradedthe
thedevelopment
developmentbox,
box,so
soany
anyissues
issuesshould
shouldbe
bewell
wellknown.
known.
46
 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 been completed and all the 2 3 pl
e
1 am
objects have been transported to the production system Ex
An

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 the new Sandbox and QA systems

BENEFITS:
BENEFITS:This
Thisapproach
approachturns
turnsthe
theQA
QAupgrade
upgradeinto
intoaareal
real“dress
“dressrehearsal”
rehearsal”for
forthe
theproduction
productionbox
boxupgrade.
upgrade.Also,
Also,since
sincewe
weare
are
switching
switchingthe
thehardware,
hardware,the
therisk
risktotothe
theupgrade
upgradeisisminimal
minimal(BW
(BW7.x
7.xprod
prodisisnot
nottaken
takenoffline
offlineuntil
untilafter
afterthe
theupgrade).
upgrade).
47
 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

The best timing is to start the production box on Thursday 2 ple

1 am 3 4
evening after the BW system has completed data loads. A full Ex
An
backup is taken.
BW 7.5 BW 7.5 BW 7.5 BW 7.5
The system is unavailable on Friday and is completely Sandbox Dev. Box QA Box Prod Box

upgraded by Saturday 6 am

Consider the time it takes for security conversion, unless

already done in the 7.0/7.3/7.4 upgrade

Plan
Planfor
forhaving
havingBasis
Basisand
andtechnical
technicalpeople
peopleworking
workingthe
thenight
nightfrom
fromThursday
ThursdaytotoFriday
Friday
and
andpossibly
possiblytotoSaturday,
Saturday,depending
dependinghow
howlong
longthe
theupgrade
upgradetakes
takes
48
 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
SP-10 before migrating to 7.5 using DMO
49
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) at the SAP Marketplace.
• TheDMO 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) 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
50
 Creating a DMO Migration Run-Book

• 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 support Unicode conversions to BW 7.4
51
 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 steps. 5.1 Check consistency between DB & DD
Create table CLU4 & VER_CLUSTR in the database for the sake of
13

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

5.3
Unicode checks in DMO
Re-check consistency between DB & DD
13
14
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 buff er 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 installed 5.34
5.35
Create the Unicode nametabs
Run UMG_SHOW_UCTABS
31
33
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
52
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%
75% 75% 100% 75%
Raw data size: 2.7 TB Core
BW Basis Support
HANA Basis Support
Company
Consultant 100% 100% 100% 75%
team
Complexity: Medium HANA Optimization developer Consultant 100% 100% 100% 50%
HANA Test & resolution lead Consultant 100% 100% 100% 50%
DataStores: 87 Functional Tester - Finance & COPA Business 25% 50%
Test 25% 50%
Functional Tester - Sales and Distribution Business
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
Environments: 4+1  The test team from the business was comprised of experienced users of the BW
Risk aversion: Medium system and needed minimal training
Other usage: Integrated  HANA Optimization of InfoCubes was done for SD reports only in this migration
Planning

This organization was using BWA 7.0 and retired it as part of the HANA
migration, thereby saving licensing costs for this platform
53
Staffing a HANA Migration Project — Medium Team
System Profile Area Role Staff area Jan Feb Mar
25% 25% 25% 25% 25%
Apr May
Project manager Company
Raw data size: 5.6 TB Core
Technical project manager Consultant 100% 100% 100% 100% 100%
20% 20% 20% 20% 20%
Project Advisor Consultant
team
Complexity: Medium 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 business
Environments: 4
 The data reconciliation and process chain testing were done by dedicated
Risk aversion: HIGH
resources in each team
Other usage: None

The team must be staffed with experienced resources. HANA training for team
members and hardware installs should be in place prior to project start.
54
 Staffing a HANA Migration Project — Very Large Team
System Profile Area Role Staff Mar Apr May June July Aug

Raw data size: 38TB Project manager Company 100% 100% 100% 100% 100% 75%
Technical project manager Consultant 100% 100% 100% 100% 100% 75%

Complexity: High Core

BW Basis Support
HANA Basis Support
Company
Consultant
75%
100%
75%
100%
50%
100%
50%
100%
100% 75%
100% 75%
team
DataStores: 1,300+ Project Advisor
HANA Optimization developer
Consultant
Consultant
20%
100%
20%
100%
20%
100%
20%
100%
20% 20%
100%

InfoCubes: 1,720+ Support team Representative

BW Technical test lead
Company
Company
50%
50%
50%
50%
50%
50%
50%
100%
50% 100%
100%
Test Team:
Queries: 2,600+ Finance and
HANA Test & resolution lead Consultant 100% 100% 100%
25%
100%
25%
100%
50%
Functional Tester - Finance Business
BPC
Functional Tester - BPC Business 25% 25% 50%
BW Technical test lead Company 50% 50% 50% 100% 100%
Duration: 5 mos Test Team:
Sales and
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Consultant Test team lead and Sales Business 25% 25% 50%
Environments: 4 Distribution
Functional Tester - Delivery Business 25% 25% 50%
BW Technical test lead Company 50% 50% 50% 100% 100%
Risk aversion: HIGH Test Team: HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Manufacturing Consultant Test team lead and Sales Business 25% 25% 50%
Other usage: APO, IP, Functional Tester - Delivery Business 25% 25% 50%
BW Technical test lead Company 50% 50% 50% 100% 100%
BPC Test Team:
HANA Test & resolution lead Consultant 100% 100% 100% 100% 100%
Global 25% 25% 50%
Functional Tester - PO and Spend Business
Sourcing
Functional Tester - AP and Performance Business 25% 25% 50%

This assumed minimal additional Test Team:

BW Technical test lead
HANA Test & resolution lead
Company
Consultant
50% 50%
100% 100%
50%
100%
100%
100%
100%
100%
HR and
functional optimization Planning
Functional Tester - HR Business 25%
25%
25%
25%
50%
50%
Functional Tester - IP Business
55
 Last Hint: De-Clustering of Tables for products based on NW 7.5

• Totake of advantage of the

new table structures of HANA,
pooled and cluster tables in
legacy databases are
declusters and depooled as a
default in NW 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
56
What We’ll Cover
• Introductions
• BW 7.5 Edition for HANA Vs. BW 7.5 on HANA
• New Enterprise Data Warehousing Capabilities
• Hardware and Landscape Deployment Options
• The DMO and the Logical Upgrade Approach
• Wrap-up

57
Where to Find More Information
• www.sap-press.com/sap-hana_3687
 Bjarne Berg and Penny Silvia, SAP HANA: An introduction (SAP PRESS, 3rd Ed.)

• http://scn.sap.com/docs/DOC-70034
 SAP SCN SAP BW 7.5 Frequently Asked Questions

• http://scn.sap.com/docs/DOC-68023
 Update to SAP BW 7.5 by Roland Kramer, SAP SE

• http://sapexperts.wispubs.com/BI
 The Future of SAP BW: SAP BW 7.5, Edition for SAP HANA by Ned Falk

• https://help.sap.com/nw75
 SAP NetWeaver 7.5 Help Portal page
58
 7 Key Points to Take Home
• BW 7.5 on 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.

59
Your Turn!

How to contact me:

Dr. Berg
Bjarne.Berg@PwC.com

60
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.

61