GRC
HR
SCM
CRM
BI


Blog

 

76 Steps in a BW-to-HANA Migration Workplan

by Dr. Berg

June 3, 2013

Many organizations are planning to move BW to to HANA and is looking for information on how to do this. In this blog we take a look at some of the major tasks you should consider when moving BW to HANA. We also include references to notes and transactions so that you can get started on writing your project plan.

Introduction

These are some of the major tasks for a BW to HANA migration. Once you have added all sub-tasks, a typical workplan has 400-600 detailed items, including status reports, team meetings, issues, hardware validation, portal integration and tests of front-end tools. 

However, these first 76 steps should give you enough to get you started on writing your project plan.

Pre-Activity Steps for Each Environment (Dev, QA & Prod)

1. Clean the Persistent Staging Area (PSA) for data already loaded to DSOs

2. Delete the Aggregates aggregates (summary tables). They will not be needed again.

3. Compress the E and F tables in all InfoCubes. This will make InfoCubes much smaller.

4. Remove data from the statistical cubes (they start with the technical name of 0CTC_xxx). These contain performance information for the BW system running on the relational database. You can do this using the transaction RSDDSTAT or the program RSDDSTAT_DATA_DELETE to help you.

5. Look at log files, bookmarks and unused BEx queries and templates (transaction RSZDELETE).

6. Remove as much as possible of the DTP temporary storage, DTP error logs, and temporary database objects. Help and programs to do this are found in SAP Notes 1139396 and 1106393.

7. For write-optimized DSOs that push data to reportable DSOs (LSA approach), remove data in the write-optimized DSOs. It is already available in higher level objects.

8. Migrate old data to Near-Line Storage (NLS) on a small server. This will still provide access to the data for the few users who infrequently need to see this old data.You will also be able to query it when BW is on HANA, but it does not need to be in-memory.

9-10. Remove data in unused DSOs, InfoCubes and files used for staging in the BW system. This includes possible reorganization of masterdata text and attributes using process type in RSP.

11. You may also want to clean up background information stored in the table RSBATCHDATA. This table can get very big if not managed.

12. You should also consider archiving any IDocs and clean the tRFC queues. All of this will reduce size of the HANA system and help you fit the system tables on the master node.

13. Size reduction of Basis Tables. In SAP Note 706478, SAP provides some ideas on how to keep the basis tables from growing too fast too fast in the future.

14. As of Service Pack 23 on BW 7.0, we can also delete unwanted master data directly (see SAP Note: 1370848).

15. Use the program RSDDCVER_DIM_UNUSED to delete any unused dimension entries in your InfoCubes to reduce the overall system size (not a factor if you plan on using the optimized HANA infocubes)

 

Pre-Validation Steps

16. Run BW to HANA Migration Readiness Check (v2.0) in  SAP Note 1729988 and resolve all high priority issues including connectivity checks, service packs, security, basis, db notes and general check in the tool for SB, Dev, QA and Prod.

17. Run ZBW_ABAP_ANALYZER for checks of ETL ABAP code and fix outstanding issues in SB, Dev, QA and Prod. Add HANA hints where required. This is found in  SAP Note 1847431

18-19. Run full delta load and gather benchmark performance statistics for load and activations.

20. Run key queries, reports and dashboards for collection of benchmark statistics and performance, including any BEx broadcaster jobs, pre-calculations and workbooks.

- Other: 

a) Conduct HANA development workshops

b) Complete HANA Admin workshop and training

c) Create an SLA and Support plan for SAP HANA internally

d) Confirm Backup, Disaster recovery and HA plan

 

Environment Staging and Migration (Post-Hardware Install, Validation, and Handover)

21. Run backup of database in SAP BW Sandbox

22. Suspend jobs and SB development activities.

23. Migrate Database to SAP HANA (export and import).

24. Connectivity validations and security checks (roles, authentication, and authorization).

25. External job scheduling checks (openhub and outbound interfaces).

26. Execute key queries identified in step 20 and reconcile data at summary level and detailed as required.

27. Collect new HANA performance statistics for dashboards, BEX broadcaster, reports, workbooks and WAD templates and analyze performance gains.

28. Run full Delta Loads from process chains (create a few records in the source environment if required) and collect benchmark statistics from ETL processing and activation. Analyze these against those collected in step 18.

29. Rerun the HANA Migration Readiness Check  in  SAP Note 1729988 and resolve any issues

30. Go / No-Go decision

31. Run backup of database in SAP BW Development environment

32. Suspend jobs and development activities in the development environment

33. Migrate Database to SAP HANA (technical migration export and import)

34. Connectivity validations and security checks (roles, authentication and authorization)

35. External job scheduling checks (openhub and outbound interfaces)

36. Execute key queries identified in step 20 and reconcile data at summary level and detailed as required.

37. Collect new HANA performance statistics for dashboards, BEX broadcaster, reports, workbooks and WAD templates and analyze performance gains.

38. Run full Delta Loads from process chains (create a few records in the source environment if required) and collect benchmark statistics from ETL processing and activation. Analyze these against those collected in step 18.

39. Rerun the HANA Migration Readiness Check  in  SAP Note 1729988 and resolve any issues

40. Go / No-Go decision

41. Refresh QA box from Prod if feasible

42. Run backup of database in SAP BW QA environment

43. Suspend jobs and transports in the QA environment

44. Migrate Database to SAP HANA (technical migration export and import)

45. Connectivity validations and security checks (roles, authentication and authorization)

46. External job scheduling checks (openhub and outbound interfaces)

47. Execute key queries identified in step 20 and reconcile data at summary level and detailed as required.

48. Collect new HANA performance statistics for dashboards, BEX broadcaster, reports, workbooks and WAD templates and analyze performance gains.

49. Run full Delta Loads from process chains (create a few records in the source environment if required) and collect benchmark statistics from ETL processing and activation. Analyze these against those collected in step 18.

50. Rerun the HANA Migration Readiness Check  in  SAP Note 1729988 and resolve any issues.

Other:

a) Test backup/restore capabilities

b) Test and collect benchmarks for High Availability and/or Disaster Recovery

51. Go / No-Go decision

----------

52. Develop detailed Production cutover plan with times steps for export and import of files.

53. Develop production validation test plan and assign resources.

54. Run backup of database in SAP BW QA environment.

55. Suspend jobs and transports in the QA environment.

56. Migrate Database to SAP HANA (technical migration export and import).

57. Connectivity validations and security checks (roles, authentication and authorization).

58. External job scheduling checks (openhub and outbound interfaces).

59. Execute key queries identified in step 20 and reconcile data at summary level and detailed as required.

60. Collect new HANA performance statistics for dashboards, BEX broadcaster, reports, workbooks and WAD templates and analyze performance gains.

61. Run full Delta Loads from process chains  and collect benchmark statistics from ETL processing and activation. Analyze these against those collected in step 18.

62. Rerun the HANA Migration Readiness Check in SAP Note 1729988 and resolve any issues.

63. User migration and log-on validation.

64. Setup Alerts in SAP HANA Studio.

65. Assign System roles and privileges in all environments.

66. Setup basepaths for all backups.

67. Validate CPU usage, memory footprint and system load during test run for reports and data loads.

68. Create a standard operating procedure for SAP HANA support staff.

69. Setup update site and process for HANA studio (SUM), license keys, and support.

70. Go/No-Go Decision (restore).

71. Optional: Optimize key DSOs to new HANA optimized DSOs.

72. Optional: Optimize key InfoCubes to new HANA optimized InfoCubes (flattened dimensions)

73. Optional: remove partitions from LSA and simplify data architecture by reducing layers

74. Optional: Create a New capabilities assessment to take advantage of near-time data warehousing using SLA

75. Optional: setup external data movement into new Data Services ETL processing chains

76. Optional: Start removing InfoCubes and build HANA views on DSOs where appropriate, thereby reducing data replication, size and data latency (non-IP, BPC and non-cumulative KFs).

Summary

While not a complete workplan, these tasks can function as the skeleton and starting point for your more detailed workplan, with timelines and assigned resources specific to your organization and scope.

Hope it helps...

Dr. Berg

Did you find this blog helpful? Get access to the latest updates and resources from SAPinsider with a free subscription.

Get the SAPinsider subscription now »»

An email has been sent to:






More from SAPinsider



COMMENTS

Please log in to post a comment.

Kristine Erickson, Editor

2/23/2015 10:53:19 AM

Thanks for your question! Dr. Berg's colleague Rob Frye of Comerit took a break from the final editing of their new book “The SAP BW to HANA Migration Handbook” with this answer:

The project team makeup will vary based on the size of the BW system that you will be migrating. For small projects (less than 5 TB), we recommend a division of labor between a core team and a test team. The core team should have a project manager, a HANA Basis support person, a HANA developer for optimization and modelling, a HANA test lead, and a BW Basis support person. For the test team, each business area included in the migration should have a dedicated functional tester. A small project should take approximately 14 weeks.

For medium projects (less than 10 TB), you will need a core team (as described above) and one test team for each business area. Each test team in this case should consist of a BW/HANA test lead and a functional tester. The core team should also include a project advisor with experience in large-scale migrations to troubleshoot problems during the project. This advisor will usually not be a full-time resource.

For large and extra-large migration projects of more than 10 TB, with high complexity, the project duration should be extended to allow for thorough testing of each business area. The test teams for these migrations should be expanded to consist of two functional testers, a HANA test lead, and a BW test lead for each business area. The core team should remain essentially the same as a medium project core team. The duration of the project should be increased to approximately 6 months (or more if needed).

Please let me know if you have any further questions.
- Rob Frye, Comerit

RSANCHEB

2/17/2015 4:47:08 PM

Great blog Dr Berg!, I have the following question, what would the team must carry out these activities? could be 1 basis, 1 bw consultants? regards & thanks. Ramon S

Rajiv Bahl

9/25/2013 9:06:38 PM

Great blog Dr. Berg as usual thaks for sharing. One comment on Step 71. Optional (which is great advice) As you may already know we will not need HANA Optimized DSO's starting with BW 7.3 SPS 10. Thanks, Rajiv


SAPinsider
FAQ