Embed Size (px)
Citation preview
BW on HANA - Systemcopy additions for BW 7.30 SP06+
Roland Kramer, Product Management BW/BI/In-Memory, SAP AG
July 2013 (Version 7.0)
© 2011 SAP AG. All rights reserved. 2 Internal
SAP First Guidance and e2e Guide - BW on HANA
http://scn.sap.com/docs/DOC-28504
© 2011 SAP AG. All rights reserved. 3 Internal
BW System Copy Use Cases considering the “Initial System Copy” case
System copy with 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
© 2011 SAP AG. All rights reserved. 4 Internal
database migration option (DMO) and end to end
implementation roadmap
DMO
http://help.sap.com/nw731bwhana#section2
© 2011 SAP AG. All rights reserved. 5 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”
2
Execute Upgrade (until downtime phase)
© 2011 SAP AG. All rights reserved. 6 Internal
Option1: Fresh Installation of BW on HANA
copy only parts of your existing productive system
Transport Transport
Transport Transport
BW
ERP
Consolidation R3Q
Production R3P
Development R3D
Development BWD
Consolidation BWQ
Production BWP
ALE / RFC
ALE / RFC
ALE / RFC
ORANGE BWx
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 releases Note 454321 - Transports between Basis Release 6.* and 7.0 Note 1273566 - Transports between Basis Release 700/701 and >=702
*
*
© 2011 SAP AG. All rights reserved. 7 Internal
Option2: System Copy with BW on HANA
PoC System creation via Production copy (“safe side”)
Transport
Transport
BW
ERP
Production BWP
Production R3P
ALE / RFC
ORANGE BWx
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
© 2011 SAP AG. All rights reserved. 8 Internal
Option3: System Copy with BW on HANA
new System direct creation when BW 7.30 SP6+ is live
Transport Transport
Transport Transport
BW
ERP
Consolidation R3Q
Production R3P
Development R3D
Development BWD
Consolidation BWQ
Production BWP
ALE / RFC
ALE / RFC
ALE / RFC
ORANGE BWx
ALE /
RFC
BW 7.30
SP06+
BW 7.30
SP06+
copy to BW on HANA (7.30)
heterogeneous systemcopy
UC migration included
© 2011 SAP AG. All rights reserved. 9 Internal
Go-Live: System Copy with BW on HANA
complete BW Landscape transformation
Transport Transport
BW
Development BWD
Production BWP
Consolidation BWQ
Transport Transport
Development BHD
Production BHP
Consolidation BHQ
BW
on
HANA
distributed (ABAP/DB)
heterogeneous systemcopy
using existing App Servers
UC migration included
© 2011 SAP AG. All rights reserved. 10 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
© 2011 SAP AG. All rights reserved. 11 Internal
Optimized BW System copy with BW Post copy
Automation (BW-PCA) Note 886102 obsolete!
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
© 2011 SAP AG. All rights reserved. 12 Confidential
Migration Paths: Upgrade and Migrate a Copy
supported by ASU toolbox and Post Copy Automation (PCA)
© 2011 SAP AG. All rights reserved. 13 Internal
Easy Implementation - BW Post Copy Automation (PCA) Note Analyzer with SAP note 1707321 and attached report
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
© 2011 SAP AG. All rights reserved. 14 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
© 2011 SAP AG. All rights reserved. 15 Internal
Check for the biggest Tables before the export creation Report 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
© 2011 SAP AG. All rights reserved. 16 Internal
Check for the biggest Tables before the export creation Transaction DBACOCKPIT/DB02 (for row/column store tables)
■ 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
© 2011 SAP AG. All rights reserved. 17 Internal
Plan the export/import time (w/o UC migration) Report UMG_R3LOAD_RUNTIME_PREDICTION
■ If no detailed information about target ressources is available, defaults are used (see example)
© 2011 SAP AG. All rights reserved. 18 Internal
Report RS_BW_POST_MIGRATION detailed view of the steps (Variant SAP&POSTMGRHDB)
«P_SAVER Step»
© 2011 SAP AG. All rights reserved. 19 Internal
ODS/DTP migration after BW Systemcopy Transaction RSSGPCLA (not BW on HANA related)
© 2011 SAP AG. All rights reserved. 20 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
© 2011 SAP AG. All rights reserved. 21 Internal
Details of the migration process - BW on HANA Transaction RSMIGRHANADB - convert the BW InfoCubes to IMO
Transaction RSMIGRHANADB
Conversion for DSO is obsolete
- HANA 1.0 ≥ Rev. 57
- Note 1849497
© 2011 SAP AG. All rights reserved. 22 Internal
SAP HANA Optimized DataStore Objects BW 7.3x Mapping 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
© 2011 SAP AG. All rights reserved. 23 Internal
SAP HANA Optimized DataStore Objects BW 7.3x Table 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)
© 2011 SAP AG. All rights reserved. 24 Internal
SAP HANA Optimized DataStore Objects BW 7.3x Representation in the Administrator Workbench (RSA1)
© 2011 SAP AG. All rights reserved. 25 Internal
SAP HANA optimized InfoCube Design in BW 7.3x
Physical schema of BW InfoCube
tailored towards traditional RDBMS
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 / New Facts
MD MD
MD MD
F
Facts
D
D
MD MD
MD MD
F E
© 2011 SAP AG. All rights reserved. 26 Internal
Standard InfoCube with Conversion Option in BW 7.3x
Facts
D
D
MD MD
MD MD
F E
© 2011 SAP AG. All rights reserved. 27 Internal
SAP HANA optimized InfoCube in BW 7.3x
Facts
MD MD
MD MD
F
© 2011 SAP AG. All rights reserved. 28 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)
© 2011 SAP AG. All rights reserved. 29 Internal
Query Performance Are 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
This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and
may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, ei ther express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
InfoCube can be removed when
used for query performance only
Thank You!
Contact information:
Roland Kramer
PM BW/In-Memory
© 2013 SAP AG. All rights reserved.
© 2013 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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.
