Login

Bookmarks

BW on SAP HANA Cookbook

This cookbook provides recipes for success when migrating your business warehouse (BW) to the SAP HANA® database. It contains an overview of the SAP HANA platform, how it can impact your business information, hands-on step-by-step guidance through the data migration process, a guide to day-to-day system operations, and an introduction to the tools and techniques needed to get the most from your data models.

BW on SAP HANA Overview

An introduction to core concepts of SAP HANA in-memory computing, and how these concepts can help your SAP NetWeaver 7.3 Business Warehouse (BW) run better. We also consider some of the technical implications of upgrading your current data warehouse to version 7.3, and of migrating it to the SAP HANA database. Lastly, we cover what you might expect during the process of transitioning to this new technology.

Deploying BW on HANA Step-by-step migration

Starting with SAP NetWeaver 7.3 SPS05 and SAP HANA SPS03, you can replace the relational database underlying your SAP Business Warehouse (BW) system with the SAP HANA database.
This procedure involves migration of your existing SAP NetWeaver Business Warehouse data to the SAP HANA database, with no disruption to existing Business Warehouse content or processes. After data migration, BW simply uses HANA as the underlying database.

Operating HANA HANA administration and BW

Once you have the SAP HANA appliance software up and running, you will have to perform the same kinds of system administration tasks required of any system. SAP offers tools designed and developed especially for the HANA platform. You will need to download, install, learn and use these to support this addition to your system landscape.
Here we review how you license, configure, monitor and troubleshoot the SAP HANA appliance. We also cover updating and patching software, backup and restore, and user authentication, as well as system expansion and availability.

Modeling BW Data Optimizing your data models

Your current SAP Business Warehouse data models need not change to run on SAP HANA. But, to bring out the best in BW on SAP HANA, you will want to work with your data models to take full advantage of the HANA appliance software.
This section covers two important aspects of migrating your data to BW on SAP HANA:

• Changes to your current BW models that will get the most out of the SAP HANA database
• Basic principles and guidance for the creation of new HANA data models 

1540608 - SAP system does not start after applying SAP kernel

Symptom

• Can't start after kernel upgrade kernel
• Effected kernels 46DEX2; 640EX2; 701; 710 and 720
• Cant start SAP after reboot
• In Windows event viewer Microsoft.VC80.CRT and SideBySide errors

Reproducing the Issue

If you are running an SAP system with kernel 7.01 and higher and you downloaded and applied a new kernel patch from SAP Service Marketplace, you cannot start your SAP system without the Microsoft security patch.
The same applies for SAP systems older than 7.01 that run with an EX2 kernel.

Cause

Cause is missing C runtime Microsoft Dll's needed by SAP kernel.

Resolution

Check if the MS C-runtime with the so called "ATL" patch is installed on your system:

• Open a command-prompt:
• Go to the c:\windows\winsxs folder.
• Type   dir  *4053*
• You should get an output like this:

 Directory of C:\Windows\winsxs x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c7
4053 is the patchlevel of the ATL patch from Microsoft.
If you don't get this output you can find the ATL package here: ATL Link. Download and install the correct patch for your platform.

Keywords

• Can't start system
• The system cannot execute the specified program.
• Microsoft.VC80.CRT errors
• Windows event viewer error SideBySide.

Header Data

Released On	16.02.2011 20:39:53
Release Status	Released to Customer
Component	BC-OP-NT Windows
Other Components	BC-OP-NT-CLU Please use BC-OP-NT
Priority	Normal
Category	Problem

Product

Product Product Version SAP NetWeaver All versions

References

This document refers to:

CSS SAP Notes

684106

Microsoft runtime DLLs

Execute OS Commands from SAP GUI

The report RSBDCOS0 enable you to execute operating system commands from the SAP level. You can directly execute the command without log in to the operating system.

1. Execute SE38 and put RSBDCOS0 in the program field. Click on execute.

2. In this example, i run command to ping www.google.com. As you can see, the result is the same like when you are running on operating system level. You can try to run other commands. Just make sure to check current operating system running so that you are executing the right command.

Tags: execute os commands from sap, RSBDCOS0

Creating New Data Classes in SAP

DATA CLASSES IN SAP

Step 1: Checking Existing Data Classes

When I needed to create a new data class, the first place I looked was the DDART table. This table lists all active and created data classes in the SAP system. Running a simple query in SQL*Plus gave me visibility into what was already defined:

sql

SQL> select * from SAPSR3.DDART;
SQL> desc SAPSR3.DDART;

The structure showed two key fields:

• TABART (VARCHAR2(15), not null) → represents the data class name

• DDCLASS (VARCHAR2(9), not null) → represents the category

Step 2: Ensuring Tablespaces Are Known

Before adding anything new, I confirmed that the relevant tablespaces were already recognized by the SAP system. This is critical because each data class must be mapped to a physical memory area (tablespace). If the tablespace isn’t registered, the new data class won’t function properly.

Step 3: Inserting a New Data Class

Using SQL*Plus, I inserted a new entry into DDART to define the data class:

sql

SQL> insert into SAPSR3.DDART (TABART, DDCLASS) 
     values ('MY_DATA_CLASS', 'CATEGORY');
SQL> commit;

This step effectively registered the new data class in the SAP dictionary.

Step 4: Linking to Tablespaces

Creating the entry alone isn’t enough. The new data class must be connected to the memory area. For this, I updated the TAORA and IAORA tables. These tables define the mapping between data classes and tablespaces.

• TAORA → holds assignments for standard tables

• IAORA → holds assignments for index tables

I used SQL*Plus again to insert or update the mappings so the new data class pointed to the correct tablespace.

Additional Notes from My Experience

• Validation: After committing changes, I always validated by checking if the new data class appeared in DDART and was correctly linked in TAORA/IAORA.

• Transport Requests: In real SAP environments, changes to DDART, TAORA, and IAORA should be captured in transport requests to move them safely across DEV → QA → PROD systems.

• Consistency: It’s important to ensure that the data class naming convention aligns with SAP standards, otherwise inconsistencies can cause confusion in administration.

• Performance Impact: Assigning data classes to the right tablespaces can improve performance, especially in large systems where table distribution across disks matters.

• Security: Only DBAs or SAP Basis administrators should perform these changes, since incorrect mappings can lead to data persistence issues.