Migrating to SAP Hana Database consideration on SAP Netweaver Parameter

Just ome quick tips on parameter to be alert when initiating SAP Netweaver Hana Database Migration  


All Databases: r3load and jload Procedures

While migrating to SAP hana Database consideration requirement for SAP Netweaver Instance parameters

rsdb/prefer_in_itab_opt
rsdb/max_in_blocking_factor
rsdb/min_in_blocking_factor
rsdb/prefer_union_all
rsdb/prefer_join
rsdb/prefer_fix_blocking
rsdb/max_blocking_factor
rsdb/min_blocking_factor
rsdb/max_union_blocking_factor
rsdb/min_union_blocking_factor





SAP Business Objects BI Essential components

 SAP Business Objects BI Essential components

Do you know the most basic essential component of  SAP Business Objects BI is as below. 

  • Reporting.
  • Data Discovery and Visualization.
  • Application and Dashboard Building.
  • Deployment and Administration.
  • You can also call it centralized suite for reporting dashboard and visualization. While being a BI laters in SAP technology front. It's sophistication makes data to be visualized in a more predominant way. 



Of course as I'm writting based on my own experience therefore the below just based on my experience and not from any master guide perhaps it could be a minimum guide from it.

This is just my shortcut of notes performing installation, however you can always google sap public domain sites for more tips and tricks info or guides. 

Installation quite straight forward all you need in a minimum is 
8GB or more RAM
Disk space of 20GB
CPU around 4 Cores
Windows operating system x64
Java 1.6 or more higher version
Microsoft .Net framwrk and Windows installer all 3.5 higher. 








Check your pre-requisite

The press next on welcome screen and accept the license agreement
After which product key required to be entered. 
Choose your language - English

I normally choose full installation type




You can select whether to configure and install Sybase SQL Anywhere 

You also need to choose the CMS database

You must select Tomcat web application in this case normally it would be TOMCAT 7.0

The configure install subversion 

Proceed with SIA - Server intelligence agent

CMS Port info to be entered. 

Password for Administrator

Configure sybase sql anywhere

Configure Tomcat

Configure HTTP listening port

Enter subversion repository port number, user account and password.

configure SMD agent for solution manager connectivity

You may choose introscope enterprise manager

Finally Start the installation - it will take a short while till you reach Finish installation. 

Post steps

Login to CMC to further configure - you may use the configuration wizard.



























How to find out your SAP Enhance package level

 How to find out your SAP Enhance package level

Quick tips

Most of you for sure this would be a perhaps mind blowing tips.


1. How to do you find out your SAP enhance Package level for SAP ECC6

Asnwer : - Login to your SAP -> System Status - > In the list of Support packages Look for module

SAP_APPL - 601  this means 6 is your SAP ECC6 while 01 means Enhance package 1

SAP_APPL - 606 this means 6 is your SAP ECC6 while 01 means Enhance package 6

SAP_APPL - 604 this means 6 is your SAP ECC6 while 01 means Enhance package 4

Hope this helps..



SAP Maintenance Planner, Transaction ID, Push to Download Basket, Download Stack.xml


This maybe the qiuckest, simplified note on how to learn about generating stack.xml and what its about.

In the current SAP technology I'm sure those SAP basis folks would have heard or went through the following ways to get their new system or existing system installed or even would have downloaded simplest pluggin of support pakcages to certain extreme. 

But i know rarely SAP basis folks touched so much on Maintenance optimizer, Maintenance Planner, knowing what is Support Package Stacks and side-effect reports outcomes. 

Well today i would like to share with you simple ways to understand SAP Maintenance Planner


Scenario 1 - If you plan to download a new installation 

In Maintenance Planner choose --> Plan a new system 

Scenario 2- If plan for upgrade example SAP ECC6 EHP5 to SAP ECC6 EHP8

In Maintenance Planner choose -->  Choose Explore system

Scenario 3 - If you plan to download Support Packages only 

In Maintenance Planner choose -->  Choose Explore system


Answer : Goto SAP one lauchpad --> login with S user id, -> in the screen goto Maintenance Planner -> Choose Explore system or Plan a new system tab --> enter relevant details such as sap product, db , os and then next button top left all the way till you get few options 

Push to Download basket , Download Stack.XML

So what happens here is that once you have went through the Plan process, maintenance planner have created a repository requirement of all your components required for installation or upgrade, where you dont have to choose manually during those days before maintenance planner existed.

Then at the screen it gives you option either to download on the spot by choosing download basket  and generate Stack.xml where both are required unless if  want to manually perform installation or upgrade. 

Push to Download basket , Download Stack.XML

Define change -> Select Files --> Download Files -- > Complete


As you can see the Push to download basket option, basically what it does, is that all the selected software component are then linked or pushed to your SAP download manager tagged to your S user id. ( In ur repository server you need to have SAP download manager application downloaded which are available in SAP one launch pad download center. 

At the ame time you need to download stack.xml - this is used for installing any system for example sapinst with xxxxxxxstack.xml file and the rest are taken care by the  installation process.

At the end when you click complete - a PDF file given stating your Stack.xml details of all the software selected, purpose of the software and transaction id. 

All downloaded software , stack.xml and PDF file need to be kept in 1 single location. 

You may have notice Transaction ID. what is this?

Well its basically content of all the stack.xml that you have generated, for example if you have generated 10 stacks.xml either r new system or upgrade, then all these are recorded as transaction in the Transaction tab in Maintenance Planner. Therefore in the future you can always enter the Transaction tab and check your Stack.XML that you have created. 


Well hope this helps and clarifies all relevant information required for you to use Maintenance planner confidently. The understanding is very important.