How to migrate BW on HANA depending on the existing IT Landscape

1. Prepared by Prof.Dr.Mehmet Erdas, SAP HANA Business Process Solution
Architect for KB IT SAP HANA Project Proposal on 24-26 Nov.2012, Berlin:
Current landscape:
 SAP ERP ECC6 EHP5
 SAP PCM 10.0
 SAP BusinessObjects 4.0
 SAP NetWeaver BW 7.3 SP3
Proposed Architecture:
Overall SAP HANA Project Phases Overview :
1.Scoping Estimate: 2-4 Weeks for 4 Systems Landscape
2.Blueprint Estimate: 2-4 Weeks for 4 Systems Landscape
3.System Installation using SAP Inst or SLT Estimate: 2-4 Weeks for 4 Systems
Landscape
4.Realization/Implementation Estimate: 2-4 Weeks for 4 Systems Landscape
5.Customization/DB Migration and Applications API Migration
Estimate: 2-4 Weeks for 4 Systems Landscape
Milestones of the BW to HANA Migration based on SAP Notes:

2. 1.Pre Checks
2. Create ABAP Export SAP Inst
3. Install CI with SAPInst
4. Install DI with SAP Inst based on ABAP Export
5. BDLS on BW and Source System
6. Restore BW and Source Systems
7. Post Migration Checks
8. Migrate ODS/DTP-Objects
9. Follow Up Actions in the Target System
10. Run Other relevant SAP Notes to resolve any OSS-
CSS Error Messages
6. Testing and Quality management: Estimate: 2-4 Weeks for 4 Systems
Landscape
7.Go-Live Preparation Estimated Total of SAP HANA Introduction : 5-6 Months
1.KB IT Generic Client for BW7.3 on HANA Project Scoping, Initial Project
Planning,Goal Setting, Preparation, Resourcing Training Team Members
1. KB IT End Client Overview BW – End Client
System Landscape status Check SM7.1 and Upgrade to BW7.3!
 Intention to Go-live in 6 Months
 Hardware ordered and delivered to start project

3.  A clear layered scalable architecture allows to benefit from BW on HANA
most easily
 No BW-AddOns, pure BW-case (no PI use case, …)
 Focus on SAP BI FE tools and SAP ETL
 Planning scenarios require additional safeguarding
 Already on BW 7.3 and Unicode
 Import Source System metadata
 Physical tables are created dynamically (1:1 schema definition of source system
tables)
 Provision Data
 Physical tables are loaded with content.
 Create Information Models
 Database Views are created
 Attribute Views
 Analytic Views
 Calculation Views
 Deploy
 Column views are created and activated
 Consume
 Consume with choice of client tools
 BICS, SQL, MDX
2. HANA Overview recap Required Human Resources:
 Roadmaps for 4 Systems – PM/HANA Soln Architect/ App.Cons.
 BW & BWA – PM/HANA Soln Architect/ App.Cons.
 (BW on) HANA – PM/HANA Soln Architect/ App.Cons.
 SAP BO BI4.0 – PM/HANA Soln Architect/ App.Cons.
 SAP NetWeaver BW7.3 SP3 – PM/HANA Soln Architect/ App.Cons.

4.  SAP PCM10.0 – PM/HANA Soln Architect/ App.Cons.
 SAP ECC6.0 EHP5 – PM/HANA Soln Architect/ App.Cons.
 Other Performance QA Tasks – PM/HANA Soln Architect/ App.Cons.
3. Identify all Data Sources Info Providers – HANA App. Consultant
DSOs, Cubes, Line Items etc..
Information Modeler
 Data
 Attributes – descriptive data (known as Characteristics SAP BW terminology)
 Measures – data that can be quantified and calculated (known as key figures
in SAP BW)
 Views
 Attribute Views – i.e. dimensions
 Analytic Views – i.e. cubes
 Calculation Views – similar to virtual provider with services concept in BW
 Hierarchies
 Leveled – based on multiple attributes
 Parent-child hierarchy
 Analytic Privilege – security object
Conduct Data Quality Integrity Consistence Redundancy Tests
4. Current HANA BW 7.3 SP03 status – HANA Soln Architect/App.Consultant
5. Review reports for HANA on 4 Systems – HANA Soln Architect/App.Consultant
6. Post Implementation next steps/recommendations– KB IT End Client
KB IT SAP HANA Pilot Proposal
The pilot of the SAP HANA hardware requires the identification of all suitable InfoProviders. The process
should bear in mind the following Check List:
 Source of the data should ideally be the ECC 6 environment
 Existing reporting must be 7.x. This is in order to remove the pre requisite of upgrading the
workbooks/Queries from 3.x
 Selection must contain both InfoCube’s and DSO’s, preferably using Layered Scalable Architecture
(LSA).

5.  Should contain cubes where either data load or query performance has been an issue.
 Where possible solution should be SAP Standard
 Data Quality will be a very important issue for Conversion into HANA In -Memory data
management
 Perform,ance Issues of Cubes and DSOs, Total Records Size
 Identify Line Items and Transaction Data
 Data Loading and Query Performance
 Identify comprehensive list of all InfoProviders
 Whether the data flows entirely conform to the LSA(Layered Scalable Architecture)
Model your schemas and hierarchies so that you understand them before and after Migration,
keeping things simple
• Your workload will change over time
• The HANA will improve over time, and changes may impact performance, and you may want
to consider redesign BP using your original clear model
Schema optimization can be considered later, such as:
• Indexes
• Aggregates
• Partitioning
• Reporting on in memory optimized Info Providers, InfoCubes,DSOs, Multiproviders
• In more detail, depth and breadth
New authorization concept must be in place
Check and Test Former and new authorization concept
� It is mandatory to setup/migrate to the new concept prior to the upgrade
� The former authorization concept is no longer supported with BW 7.30
� You cannot switch back to the former concept
� New Transaction RSECADMIN, see SAP Notes 942799 and 944929
2.Business Blueprint,Mapping Value Drivers to Implement Scope, Project
Team HR, Requirements definition, Functional Design and Sign-Off
Requirements defn.
Project Roles: Project Manager End Client- Implementation Partner- SAP
HANA Solution Architect
HANA Application Consultant
SAP EC6.0 Consultant

6. SAP BO BI4.0 Consultant
SAP BW 7.3 Consultant
SAP PCM10.0 Consultant
SAP Total Quality Management Consultant
3.Implementation, Build, Migration& Test Concept, Document and Get final
Business Sign Off
HANA 1.0 SP03 Implementation Steps:
ECC6.0 BW on HANA Implementation Steps before Going Live:
 First Upgrade to BW7.3 and apply Solution Manager 7.1 for Going Live
Check Analysis of existing SAP Infrastructure and current landscape of
SAP EMP Products and components,ABAP or JAVA based main Instances,
Databases and related components of SAP HANA DB, SLT Replication,
TREX, Sybase Replication Agent and Sybase Server.
 Separation of ABAP and JAVA Stacks
 Make two system copies before for security purposes of OLTP and OLAP
of EMP
 Analysis of all available BW Objects, InfoObjects, standard write/read
optimized DSOs, standard and real time,remote, Infocubes,
Aggregates(which ones tob e deactivated and deleted, retained),
Multiproviders to create a new strategy, from as is how to transformt o
to be Final System Architecture improving data quality in real time using
in memory optimized(column based) data structures utilizing HANA
Studio with no DIMIDS and no E Table, retaining only F Fact table to be
directly connected to Dimensions leading to save 80% of previous data
processing time.

7.  Analyze Existing SAP and non-SAP Applications considering Hardware
Capacity limitations with worst case data loading and SLA, BW, QoS etc…
 Check System Operation and Availibility with Version Compatibility
 Apply all SAP Notes required for proper sizing, dimensioning etc.. Note
1600929 - SAP BW powered by SAP inMemory DB – Information
 •Note 1600066 - Available DBSL patches for NewDB
 •Note 1639744 - heterogenious systemcopy NetWeaver 7.30 to HANA
target DB
 •Note 1657994 - SAP BW 7.30 powered by HANA - Special SP06
 •Note 1662588 - Download: ABAP only SP06 for SAP BW powered by
HANA DB
 •Note 1514966 - SAP HANA 1.0: Sizing SAP In-Memory Database
 •Note 1637145 - SAP BW on HANA: Sizing SAP In-Memory Database
 •Note 548016 - Conversion to Unicode
 •Note 551344 - Unicode Conversion Documentation
 •Note 1589175 - System Copy: Task Content for Task Manager
 •Note 1589145 - Task Manager for Technical Configuration
 •Installation/Operational Guides: http://help.sap.com/nw73bwhana
 CreateAnalytical Index
 Create Transient and Composite Providers for InfoCube Connections
 Check request IDs using RSLIMO Transaction in EXPERT Mode
 Migrate and Convert into In Memory Cubes, DSOs…
 Create and adjust new Authorization Concept using RSECADMIN
 Activate all structures

8.  Apply all necessary ( Coordinate with SAP Development Angels,
Implementation Partner, Endclient’s IT management) new SAP Notes,
Add-ons and Add-in s for migrating and converting to SAP HANA1.0
 Check different scenarios in making the system copy, refresh the system
copy, before migrating from ERP to BW and HANA
 Use ALE/RFC, ASU Toolbox and/or SLT Replication of Sybase with
different options and alternatives depending on the specific architecture,
data quality, architecture, interface definitions etc…
 Check again, Security concept, authorization concept, before converting
to In Memory real time data structures.
 Do necessary data cleansing before! Migrating to HANA and Speeding up
with dirty data does not add any Business value,
 Check TCO, and Investment Protection preventing and delays avaiding
Version conflicts and Interface conflicts INSTALL SAP EARLY WATCH
ALERTS USING SOLUTION MANAGER 7.1
 Check the existence of relevat APIs by SAP before deciding any
alternative implementation.
Installation of a homogeneous Systemcopy – BW on HANA
Installation of CIA System – BW on HANA (ORANGE) including unified Installer
Prepare the HANA server before starting unified Installer
Prepare the filesystem for the default usage of HANA 1.0 SP03
starting/stopping HANA and sapstartsrv
create the default filesystem manually and reset install directory
start the unified Installer

9. uninstall the unified Installer
Adapt the file .sapenv.csh for the user <sid>adm
Run the unified Installer
Starting the Import of the homogeneous System export of the CIA system
SAPInst GUI on the Windows Frontend
Default location of the SAPInst directory
Check invalid_objects.txt
Setting the correct client DEFAULT.PFL and adapt the Instance Profile – restart
Instance
The Time Problem on CIA (ABAP), shortdump ZDATE_LARGE_TIME_DIFF
Import new License and check secure storage after migration
Check the Import of SP03
Apply the corrections after BW 7.30 SP03
Manual Processing of some SAP Notes
Modifying the SAP Profiles (restart SAP
4.Final Preparation for Production Migration and Test Release Training
Prepare Go Live
5.Go Live Support ; Monitor and Execute Migration for 4 System Landscape
Environment, Build CoE for BW on HANA

10. 6.Run and Optimize new System using new SAP Notes and SAP Best Practices
Guidelines