BW on HANA - Systemcopy additions for BW 7.30 SP06+ - SAP

Roland Kramer, SAP BW Product Expert, SAP AG

January 2020 (Version 7.0)

BW on HANA - Systemcopyadditions for BW 7.30 SP06+

2INTERNAL© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Internal

SAP First Guidance and e2e Guide - BW on HANA

https://blogs.sap.com/2016/10/11/sap-first-guidance-collection-sap-bw-hana/

https://blogs.sap.com/2016/10/11/sap-first-guidance-collection-sap-bw-hana/


Internal

BW System Copy Use Casesconsidering the “Initial System Copy” case

System copywith SAPInst / DB-Tools

SAP NetWeaver ABAP 7.0

or higher

Execution of post copy activities

with Post Copy Automation

Execution of post copy activities

SAP NetWeaver ABAP 7.0 or

higher

Export und Import of tables

with Post Copy Automation

Export

System Copy with SAPinst / DB-Tools

Import

System Copy Refresh

Initial System Copy


Internal

database migration option (DMO) and end to end implementation roadmap

DMO

http://help.sap.com/nw731bwhana#section2

http://help.sap.com/nw731bwhana


Internal

functionality of the database migration option

(DMO for SUM) ➔ replacing all other current options

Setup SAP HANA

specifics (client, schema …)

Downtime

Traditional

DB

SAP

System

SAP HANA database

migration option will be a

SUM-based tool simplifying

the migration process

Pilot (planned until end of Q2/2013)

Upgrade and Migration of

BW system in one Step

First shipment (planned for

H1/2013) Unicode

Conversion, Upgrade and

Migration for SAP

NetWeaver BW Systems

GA Version available

Q3/2013

Future direction

Cover additional products

Further downtime reduction

Tim

e

Uptime

Note

Traditional

database

continues to

run

3

6 Start SAP HANA-based system

4 Migrate application data(incl. data conversion)

5 Finalize Upgrade

1 Upgrade “Prepare”

2Execute Upgrade(until downtime phase)


Internal

Option1: Fresh Installation of BW on HANA

➔ copy only parts of your existing productive system

TransportTransport

TransportTransport

BW

ERP

ConsolidationR3Q

ProductionR3P

DevelopmentR3D

DevelopmentBWD

ConsolidationBWQ

ProductionBWP

ALE / RFCALE / RFC ALE / RFC

ORANGEBWx

ALE / RFC

BW 7.0/7.0x

7.30

BW 7.30

SP06+

Fresh Install BW on HANA (7.30)

UC enabled

transport only parts of the system

Note 1090842 - Composite note: Transport across several releasesNote 454321 - Transports between Basis Release 6.* and 7.0Note 1273566 - Transports between Basis Release 700/701 and >=702

*

*

https://service.sap.com/sap/support/notes/1090842


http://www.myopenbee.org/images/screenshots/serveur%20Open%20Bee%201.jpg







Internal

Option2: System Copy with BW on HANA

➔ PoC System creation via Production copy (“safe side”)

Transport

Transport

BW

ERP

ProductionBWP

ProductionR3P

ALE / RFC

ORANGEBWx

ALE / RFC

Production

BWC

copy of Production (7.x)

homogeneous systemcopy

Upgrade NetWeaver 7.30

BW 7.30

SP06+

BW 7.30

SP06+

BW 3.5

7.0/7.0x

7.30

copy to BW on HANA (7.30)

heterogeneous systemcopy

UC migration included

add. preparation

data cleansing

ALE / RFC





Internal

Option3: System Copy with BW on HANA

➔ new System direct creation when BW 7.30 SP6+ is live

TransportTransport

TransportTransport

BW

ERP

ConsolidationR3Q

ProductionR3P

DevelopmentR3D

DevelopmentBWD

ConsolidationBWQ

ProductionBWP

ALE / RFCALE / RFC ALE / RFC

ORANGEBWx

ALE /

RFC

BW 7.30

SP06+

BW 7.30

SP06+

copy to BW on HANA (7.30)










Internal

Go-Live: System Copy with BW on HANA

complete BW Landscape transformation

TransportTransport

BW

DevelopmentBWD

ProductionBWP

ConsolidationBWQ

TransportTransport

DevelopmentBHD

ProductionBHP

ConsolidationBHQ

BW

on

HANA

distributed (ABAP/DB)


using existing App Servers









Internal

Milestones of the System copy/UC Migration (886102) “the old way”

Restore BW and Source Systems (RSA1)

Install DI with SAPInst based on Abap Export

Install CI with SAPInst

Create Abap Export with SAPInst

BDLS on BW and Source System

Post checks (RS_BW_POST_MIGRATION)

Migrate ODS/DTP-Objects (RSSGPCLA)

Pre checks (SMIGR_CREATE_DDL)

Follow up Actions in the Target System

UC Migration

SPUMG

UC Migration

Converting InfoCubes

In-Memory optimized


Internal

Optimized BW System copy with BW Post copy Automation (BW-PCA)

Restore BW and Source Systems (RSA1)

Install DI with SWPM based on Abap Export

Install CI with SWPM

Create Abap Export with SWPM

BDLS on BW and Source System

Post checks (RS_BW_POST_MIGRATION)

Migrate ODS/DTP-Objects (RSSGPCLA)

Pre checks (SMIGR_CREATE_DDL)

Follow up Actions in the Target System

UC Migration

SPUMG

UC Migration

Converting InfoCubes

In-Memory optimized

BW-PCA

Post Copy Automation –

BW Basis Tasklist

BW-PCA

BW-PCA

➔ Note 886102 obsolete!


Internal

Migration Paths: Upgrade and Migrate a Copy

supported by ASU toolbox and Post Copy Automation (PCA)


Internal

Features of note analyzer:

• A list of (different) notes will be listed depending on release state and system role

• Dependent notes will be listed as well

• Update of notes will be listed for re-implementation after each analysis

• Notes with manual works will be listed

• Parallel download of notes is possible for speeding-up the download process

Easy Implementation - BW Post Copy Automation (PCA)Note Analyzer with SAP note 1707321 and attached report


Internal

BW Post Copy Automation (BW-PCA)Note 1632574 - BW tasks for System Copy Automation

The overall guidance can be found here:

http://service.sap.com/instvlm


http://service.sap.com/instvlm


Internal

Check for the biggest Tables before the export creationReport SMIGR_BIG_ROW_STORE_TABS (for row store tables)

<export-dir>/ABAP/DB/HDB/rowstorelist.txt

■ Note 1659383 - RowStore List for SAP Netweaver on SAP HANA Database



Internal

■ consider table splitting for export/import for the „top50“ largest tables

■ house keeping jobs, cleaning, reduction of data in the largest tables to consider prior to th export

Check for the biggest Tables before the export creationTransaction DBACOCKPIT/DB02 (for row/column store tables)


Internal

■ If no detailed information about target ressources is available, defaults are used (see example)

Plan the export/import time (w/o UC migration)Report UMG_R3LOAD_RUNTIME_PREDICTION


Internal

Report RS_BW_POST_MIGRATION detailed view of the steps (Variant SAP&POSTMGRHDB)

«P_SAVER Step»


Internal

ODS/DTP migration after BW SystemcopyTransaction RSSGPCLA (not BW on HANA related)


Internal

Optional: Program RSDU_TABLE_CONSISTENCY to check additional correctness of tables in row/column store

Additional Notes to consider: 1660125 and 1674377 (available with SP07)

/usr/sap/<SID>/SYS/global/rowstorelist.txt

■ Note 1659383 - RowStore List for SAP Netweaver on SAP HANA Database

■ Note 1695778 - Partitioning BW tables in SAP HANA database

http://service.sap.com/sap/support/notes/1660125

http://service.sap.com/sap/support/notes/1674377




Internal

Details of the migration process - BW on HANATransaction RSMIGRHANADB - convert the BW InfoCubes to IMO

Transaction RSMIGRHANADB

Conversion for DSO is obsolete

- HANA 1.0 ≥ Rev. 57

- Note 1849497



Internal

SAP HANA Optimized DataStore Objects BW 7.3xMapping Between Application Server and HANA DB

History Index

(column based)Main Index

(column based)Delta Index

Column based table Calculation View

Standard column based table

Type „Insert Only“ (no primary

key)

Uniqueness checked by SQL

statement (DBMS exit)

Temporal table

Additional field „IMO__INT_KEY“

Auto merge off

„Old“ external key

Table replaced by calc

view (uses history index to

create a change log view of

the data)

View calculates technical

key on the fly

Multiple updates for a

particular key are

consolidated into one


Internal

SAP HANA Optimized DataStore Objects BW 7.3xTable Structures for HANA Optimized DataStore Objects

Maps activation request

SID to commit ID used in

history index (NewDB

internal usage)

DataStore

SID

Module

uses

Status of SID creation

Source dependent check

Activation Queue

/[Namespace]/A[DataStore]40

Standard column based table

Type „Insert Only“ (no primary key)

Uniqueness checked by SQL

statement (DBMS exit)

Active Data Table

/[Namespace]/A[DataStore]00

Temporal table (History table)

Additional field „IMO__INT_KEY“

Automerge ‘off’ as application

triggers smartmerge

„Old“ external key

Change Log

/BI0/B*

Table is replaced by calculation view

(Extraction process uses history

index to create a ‚change log view‘

of the data)


Internal

SAP HANA Optimized DataStore Objects BW 7.3xRepresentation in the Administrator Workbench (RSA1)


Internal

Physical schema of BW InfoCube tailored

towards traditional RDBMS

SAP HANA optimized InfoCube Design in BW 7.3x

Benefits:

Fast data loads (no DIMIDs) ➔ up to 80% time reduction

Dimensions not physically present ➔ simpler modeling and faster structural changes

All processes, all Queries and MultiProviders can remain unchanged

HANA can work with “flat” structures and

doesn’t need E- and F-fact tables!

Conversion / NewFacts

MD MD

MD MD

F

Facts

D

D

MD MD

MD MD

FE


Internal

Standard InfoCube with Conversion Option in BW 7.3x

Facts

D

D

MD MD

MD MD

FE


Internal

SAP HANA optimized InfoCube in BW 7.3x

Facts

MD MD

MD MD

F


Internal

Conversion Steps and Log Overview

– Create temporary fact table with “flat” structure Z0<InfoCube>

– Read data out of the original fact tables dissolving the

starschema and save data in temporary fact table

– Rename package dimension database table TP<InfoCube>

Rename validity table (in case inventory mgmt InfoCube)

TL<InfoCube>

– Empty the InfoCube tables

– Set InfoCube subtype to “flat”

– Activate the InfoCube - As it is empty the structures and their

DDIC description can be adjusted

– Delete Fact DB-table and rename the temporary one

– Delete PDIM and rename the temporary one

– Delete validity table and rename the temporary one

– Delete temporary DDIC objects

– Create logical index

(This can be done with transaction RSMIGRHANADB)


Internal

Query PerformanceAre InfoCubes Still Required?

Info Cubes required for

Non-disruptive approach when migrating to

BW on HANA

Non-cumulative Key Figures

Complex business logic(report specific)

BW Integrated Planning

External write-interface(RSDRI)

Conclusion

There are scenarios where the InfoCube

layer becomes obsolete

Less materialized data and simplification

Decision to be made scenario by scenario:

Business and Performance needs

InfoCube can be removed when

used for query performance only

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE

and its distributors contain proprietary software components of other software vendors. National product specifications

may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without

representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those

that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein

should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this

document or any related presentation, or to develop or release any functionality mentioned therein. This document, or

any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments,

products, and/or platforms, directions, and functionality are all subject to change and may be changed by SAP SE or its

affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to

various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are

cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in

making purchasing decisions.

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.

See www.sap.com/copyright for additional trademark information and notices.

www.sap.com/contactsap

Follow us

© 2020 SAP AG. All rights reserved.

SAP, ERP, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,

and other SAP products and services mentioned herein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web

Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business

Objects is an

SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and

services mentioned herein as well as their respective logos are trademarks or registered trademarks of

Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data

contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied,

or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

https://www.sap.com/copyright

https://www.sap.com/registration/contact.html

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP

Date post:	19-Nov-2023
Category:	Documents
Upload:	khangminh22
View:	0 times
Download:	0 times

BW on HANA - Systemcopy additions for BW 7.30 SP06+ - SAP

Documents