This series of publication intends to provide an overview and explanation of major steps and considerations for BW on HANA migrations from anyDB (any database). The complex procedure involves:
1) Preparatory work in the BW system
2) SUM DMO Upgrade and Actual migration
3) Post processing on the migrated systems
This part focuses on post-processing, which includes standard tasks after upgrade and HANA-specific post-tasks.
BW Migration to HANA Part 3 - Post-processing on the Migrated System
1. BW Migration
to HANA
Part 3 of 3
Post-processing on the Migrated System
By OZSoft Consulting for ITConductor.com
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 1
Any DB
Migrate
Upgrade
Preparation Post-processing
2. Introduction
• This is Part 3 of the series of publication which provides an
overview and explanation of major steps and considerations
for BW on HANA migrations
• Migrating a BW system from anyDB (any database) to HANA
involves
1. Preparatory work in the BW system
2. SUM DMO Tool for SAP Upgrade and Migration
3. Post processing on the migrated system
• This part focuses on post-processing, which
includes standard tasks after upgrade and HANA-
specific post-tasks.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 2
3. Post-processing - general
After migrating a BW system to HANA, there are two general groups of
post-tasks
1. Standard tasks after a release upgrade or Unicode conversion
2. HANA-specific tasks
After the downtime processing AND before doing anything:
1. Create a backup of the database
2. Configure HANA parameter log_mode to ‘normal’
3. Configure HANA parameter enable_auto_log_backup to ‘YES’
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 3
4. Standard post tasks
Below are some post tasks after a release upgrade/or Unicode conversion.
The list is not exhaustive, not necessarily in sequence, and does not
include site-specific process.
Note that the DMO tool, automatically run RS_BW_POST_MIGRATION
during its post-processing phase, but there maybe a case of running some
steps.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 4
Adapt dialog instances to the new release/kernel Run SECSTORE (OSS note 816861)
Run SICK Configure SAINT parallelism (OSS note 1309506)
For each instances, run SM51 and SM21 RZ12 – configure number of free WPs
Run SGEN (SAP_BASIS first, then the rest) DB13 – maintain standard jobs
Reconfigure/adapt 3rd party products RSA1 – check source systems - activate
Import profile parameters Solution Manager configuration
5. HANA-specific post-tasks
• The cookbook, SAP First Guidance – DMO – BW on HANA
lists down the tasks and steps in detail.
• OSS notes, blogs that were referenced while doing the
steps, (i.e. to get more background information), are added
in this document.
• Some of the tasks need to be a collaborative work with the
BW Administrators and Security team.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 5
6. HANA-specific post-tasks - 1
Task – Activate new HANA server functions (scriptserver)
• Login to the system database container to adjust the scripserver section
of the daemon.ini and nameserver.ini
Task – Enable ‘Dynamic Range Partitioning’ feature of DataStore objects
• Refer to OSS note 2081135 for background on this Dynamic Range
Partitioning
Task – Install Application Function Library (AFL)
• For the brief on AFL, refer to SAP help page - AFL
• For HANA Analysis Process (HAP) background, refer to First Guidance –
SAP BW 7.40 powever by HANA - HANA Analysis Process
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 6
7. HANA-specific post-tasks - 2
Task – Configuring DBMS User Management for SAP HANA
• This task need to be done in collaboration with the security team
• For more detail/additional document, refer to DBMS Users in SAP NW ABAP
7.40
• Additional information – Configuring DBMS User Management for SAP HANA
• SQL syntax to get the SQL_port for the connection information in DBCO
select sql_port from sys.m.services where service_name = ‘indexserver’
• SQL syntax to list DBMS user’s assigned roles
select * from effective_roles where user_name = ‘<DBMS_USER>’
• If you remove the assigned DBMS user through SU91, the DBMS user will notbe
deleted from the HANA side. Remove it through program RSUSR_DBMS_USERS
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 7
8. HANA-specific post-tasks - 3
• DBMS roles that are available for DBMS users
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 8
9. HANA-specific post-tasks - 4
Task – Install Smart Data Access (SDA) Drivers
• Reference: SAP help page – SDA
Task – Transaction RS3HANA_CHECK/ADMIN
• This is for SAP HANA view. For background, refer to SAP First Guidance -
SAP BW 7.40 on HANA - View Generation
Task – Create CDS views after migration
• CDS stands for ‘Core Data services’
• For brief on CDS, see Enhanced ABAP development with CDS
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 9
10. HANA-specific post-tasks - 5
Task – RowStore to Column conversion
• In our migration, only empty, temporary
tables were listed during the check
Task – Check HANA with DBACOCKPIT
• No issue found
Task – RS_BW_POST_MIGRATION
• As the source system was already on 750/02, all mentioned OSS notes
were already in place and no issue found.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 10
11. HANA-specific post-tasks - 6
Task – ASU Tool box
• There are some follow-up post-tasks
Task – RSDU_TABLE_CONSISTENCY
• For more information, refer to Table Consistency Check for BW Tables on
HANA
Task – RSDDB_INDEX_CREATE_MASS
• For more information, refer to BWonHANA: InfoProvider column views
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 11
12. HANA-specific post-tasks – 7
Task - Migration Check – SHDB_MIGRATION_CHECK
Task - RS_BW_POST_MIGRATION
• If OSS note 2060342 has been implemented, then run step 12 ‘Create
views for InfoProvider’. This was not performed since the system is
already 7.50
Task - Repair inconsistent PSA tables
No issue found
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 12
• Note 1785060 - Recommendations for
performing the migration to SAP HANA
13. HANA-specific post-tasks - 8
Task - Regenerate all Transformations
• For reference, see Transformation – Consistency check programs
• Refer to OSS note 1408161 – Program for transformation activation
The note refers to required input parameters
• Transformation ID can be derived from table RSTRAN
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 13
14. HANA-specific post-tasks - 9
Task - Convert InfoCubes into in-memory optimized
• It is highly recommended to convert existing InfoCubes to SAP HANA-
optimized Infocubes to reduce the data load. Note that after the migration to
HANA, all newly created InfoCubes will be automatically be SAP HANA-
optimized Infocubes.
• References:
Converting Standard InfoCubes to SAP HANA-Optimized InfoCubes
Aspects of the HANA-optimized InfoCube
• To check if an infocube is optimized, go to RSA1, under Settings Subtype =
‘SAP HANA optimized Infocube’.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 14
15. HANA-specific post-tasks - 10
Task – Migrate BW Workspaces
• Report RS_BW_POST_MIGRATION – steps 12 - 15
For explanation on ‘Unload Priority’, refer to SAP BW on HANA: Data
Classification
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 15
16. HANA-specific post-tasks - 11
The following tasks were not performed in our migration, some of them
maybe required to take advantage of simpler data models on BW, and
especially with the new BW/4HANA, just announced by SAP in Sep-2016:
• Converting DataStore Objects and Infocubes into advanced DSO
• Convert MultiProvider to CompositeProvider
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 16
17. Summary
The SAP BW upgrade and migration to SAP HANA has over
100 steps, and each environment maybe a little different
based on the usage scenario and customer specific data
encountered. However, these publication seek to provide an
overview of the processes for planning and guidance so that
you can confidently create a roadmap for BW on HANA and
even next generation BW/4HANA migration involving:
• Preparation of the source BW system
• Carrying out the SAP SUM (Software Update Manager)
upgrade & migration using DMO (Database Migration
Option) for the BW system from anyDB to BW on HANA.
• Finally, post-processing on the Upgraded/Migrated System.
GOOD LUCK!
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 17
18. • Any Questions?
• Contact Info:
Linh Nguyen linh.nguyen@itconductor.com
Terry Kempis terry.kempis@itconductor.com
Let
itconductor.com
@itconductor
18