Monthly Archive: March 2015




Hana appliance is a combination of SAP Hana database software and the Hardware specification.

As you see above A SPA HANA Database has CPU , Main memory (Ram) and then the persistance layer i.e the disk containing the log volumes and Data volumes.

RAM is physical memory – 128GB is minimum needed for SAP HANA, 256GB,512 GB,1TB


Data volumes should be 3-4 times of RAM

Log volumes should be equal to RAM size.

Data is stored in RAM in two types of data store- Row Store and Column Store.

Row Store –as you know traditional databases store data in row store residing in disk, where as in HANA all row store data are stored in RAM.

Cloumn store- this data is stored in columns as in BWA.

What is Persistance Layer: data is memory is volatile, i.e in case of power loss or server crashes, the data in the memory is lost. Hence We need a persistance layer containing the data volumes and log volumes in the disk. SAP HANA has a save point parameter where in every 300 seconds the changes done

In traditional database- only data is fetched from database and all calculation and analysis is done in application server and then sent to frontend.

Where as in SAP HANA the data is fetched and calculated and analyzed and then sent to application  layer making is very fast.



Why should customers/clients switch to SAP HANA

Why should customers/clients switch to SAP HANA


Below are the Reasons:

1)You have massive amount of data and you need to manage it efficiently and quickly

2)Get insights of your massive data both structured and unstructured

3)Develop innovations

4)Perform complex business and forecast  analysis quickly

5)Run next generation application like mobile apps ,web apps

6)Set up advanced cloud platform

7)Simple to manage and use

8)get most of the old obsolete data gives you new insight for your business

9)highly flexible and get immediate results on different platforms


What is SAP HANA

What is SAP HANA

HANA stands for High Performance Analytic Appliance. 90% of The coding is done in C++ and the key feature of SAP HANA is that it is in memory computing

1)In memory computing (RAM) makes it fast

2)Lowers cost of operation

3)users of all levels are empowered to conduct immediate ad hoc data

analyses and transaction with SAP HANA DB

processing using massive amounts of real time data

Traditional databases like oracle sql, had limitation due to bottleneck of disk I/O and SAP HANA has rectified this by a different approach of in Memory computing.

Hardware innovations like the multi core CPU with handling capacity of huge amount of RAM has lead to SAP HANA innovation.parallel processing is possible, 80 cores and 128 cores servers capable of handling more than 1TB of RAM is available making the future of  in memory computing

Available on suse linux and red hat linux platform.can handle OLTP,OLAP.

SAP BUSINESS SUITE – The Steroids for Businesses

SAP BUSINESS SUITE Powered by HANA– The Steroids for Businesses

SAP Business Suite is now powered by  real time technology: SAP HANA. This software brings together transactional and analytical data into a single in-memory-based solution which can deliver analysis in matter of seconds and having the power to process billions of records to provide you meaningful insights of this massive data in real time. You can now drive your entire business to create new business value with smarter business innovations, faster business processes, and simpler business interactions. Massive compression of data helps in keeping the cost low for the infrastructure budget. Also sate of the art front end application helps to manage and scale the SAP Business Suite Powered by SAP HANA easily without much hassle.

SAP Business Suite software powered by HANA helps businesses quickly optimize, execute, and align their business and IT strategies to maximize profits and enhance maximum utilization of resources thus driving more profits. Eg: Auction companies can quickly analyze the sales trend ,price trends, customer reviews and adjust their business processes accordingly to maximize profits and make real time optimization across the organization in a matter of seconds. Another example is a power distribution company can get real time insight on the power consumption and thereby adjust  the power generation and distribution efficiently which was nearly impossible without the real time Sap HANA. The suite gives you the unique ability to perform essential end-to-end business processes with modular applications that are designed to work with other SAP and non-SAP business solutions.

Along with  reporting and analytics functions for your entire organization , SAP Business Suite provides a robust technology environment for designing, composing, and adapting business processes that meet the specific needs of your industry. Core applications within SAP Business Suite support processes for finance, human resources, manufacturing, procurement, product development, marketing, sales, service, supply chain management, and IT management.

Note:This is a personal blog and I do not receive monetary compensation for any of my product/Tech reviews. All reviews represent my opinion . Please consult respective company for professional consultations.-Ramesh Umapathaiah

How to delete an SAP Client

How to delete an SAP Client


    • Log on to the client to be deleted.
    • Use the menu option use Transaction code SCC5 or from the SAP System initial screen choose Tools _ Administration _ Administration _ Client admin _ Special functions _Delete client.
    • Start the deletion of the client, preferably using background processing.
    • When you delete a client entry from table T000 with client maintenance (TransactionSCC4), you can no longer log on to the client or update it using change requests. The deletion process, however, does not eliminate the data belong to the client. This means the client-dependent data remains in your SAP System, occupying space in the database. Therefore, to eliminate an SAP client entirely, that is, to delete both the client and the client-dependent data, use the client delete functionality (Transaction SCC5).
    • Deleting a client entry with client maintenance (Transaction SCC4) allows you to temporarily lock the client. The deletion procedure preserves the data for the client but prevents users from logging on to the client or accessing the data belonging to the client. To restore the client and allow logon, recreate the client entry using client maintenance.
    • The amount of time required for the deletion of a client can be reduced by performing the deletion using parallel processes.

Share this article :


What are the different types of Transports requests?

There are 3 types of requests:
K type:
The transport K type implements transports of DE objects from the integration system into the consolidation system. When you create a transport request using the workbench organizer, it always uses this transport type by default meaning that all the transportable change requests stored in the workbench organizer are allocate this transport type. For this transport type, the objects are transported to the consolidated systems without changing the object’s system owner which means that the transported objects in the consolidated system become repair objects and no corrections are allowed for the imported objects.
C type:
With this transport type the objects change the system owner after they are transported which means that the source system of the object loses its ownership after the object is transported. So the target system in which the objects are transported becomes the original system. In other words objects are transported as original objects. So they can be corrected or modified in the target system too. That means that change authorization is also transported. In SAP terms, objects that are transported with C types are checked out of a system and checked into another system.
T type:
This transport type is useful when you have to copy object between two systems in a group ie when a system(other than consolidation system) receives a copy of objects, the corresponding transport takes place with transport type T. Object including the object of transport type T do not change their system owner. So the original system remains same.

How to unlock SAP* user id.

Use the below commands

update sapsr3.usr02 set flag=0 where bname=”ddic” and mandt=’100′;


update sapsd1.usr02 set uflag=0 where bname=’SAP*’ and mandt=’120′;

To check the status of SAP* user id
select status from sapr3e.usr02 where bname=’SAP*’ and mandt=’120′

Delete SAP* user id.

delete from sapsr3.usr02 where bname=’SAP*’ and mandt=’120′;

Setup Single sign on (SSO) setup for Netweaver 7.0

Verify the following profile parameters are set correctly in the backend using rz11
login/accept_sso2_ticket = 1
login/create_sso2_ticket = 0
Make sure that in the portal the connector to back end is defined with following setting and permission is set correct.
Authentication Ticket Type – SAP Logon Ticket
User Mapping Type – useradmin,user
Fix certificate
Login in to Visual Administrator
1. Select the Key Storage Service.
2. Select the TicketKeystore view.
3. Delete the SAPLogonTicketKeypair and SAPLogonTicketKeypair-cert entries.
4. Under Entry, choose Create . The Key and Certificate Generation dialog appears.
5. Enter the Subject Properties in the corresponding fields.
The entries in these fields build a Distinguished Name in the form:
CN= , OU= , O=, L=, ST= , C=
Use capital letters for the Country Name.
6. Enter SAPLogonTicketKeypair as the Entry Name.
Do not enter a different name. This J2EE Engine uses the entry with this name to sign logon tickets.
7. Select the Store certificate option and choose DSA as the algorithm to use.
8. Choose Generate .


System Monitoring has to be done regularly in order to track the efficiency and the utilization of the systems. Monitoring the systems for system logs, successful backups, runtime errors, locks, updates, buffer quality, CPU performance etc achieve this.

Transactions to be executed daily by any Basis consulatnt  to ensure sustained availability and view overall performance are as below. This list of Tcode  is the most important  and used almost daily

SM21              System Log

SM37              Simple Job Selection

ST22               ABAP Runtime Errors

SM12              Lock Entries

SM13              Update Requests

SM51              SAP Servers

SP01               Spool Requests

ST02               Tune Summary

ST03/ST03N  Workload Analysis

ST04               Database Performance Analysis

ST06               Operating System Monitor

DB12              Database Backup

DB13              DBA Calendar

DB02              Tablespace Overview

RZ20               CCMS

SMQ1            Outbound Queue

SMQ2             Inbound Queue

SPAD             Spool Administration


GRMG           Generic Request Message Generator

ST01               System Trace