Big Data SAP

SAP HANA Data Migration Essentials

Publish Date: December 15, 2017

SAP HANA is an in-memory data platform that lets you speed up business processes, simplifies your IT environment and delivers more business intelligence. SAP HANA removes the dire need to maintain your legacy systems as well as stored data to run your business more efficiently. This data can be either moved to be stored in cloud or on-premise, as the business finds comfortable. This, in turn, enables analysts and developers to avoid having to write back or load data.
SAP HANA enables real-time delivery of analysis and transactions. Its major advantage is that it increases information processing efficiency because of its columnar format rather than traditional data processing in row-based memory. The high level of data compression makes SAP HANA architecture much smaller than traditional ones; however, it does require more server memory.

Steps for successful Data Migration to SAP HANA
SAP HANA is probably the most crucial technology invention from SAP in the past decade or so. All SAP products released post-HANA are capable and have the innate ability to adapt and integrate seamlessly to this platform. SAP HANA is one of the most powerful tools that SAP has to offer, out of its suite of products as it enables quicker integration, more data procession, improved ROI for every organization, etc. This is achievable, only if you know how to migrate organizational data appropriately onto SAP HANA.

Let us understand a few steps for successful data migration onto SAP HANA-

  1. The scope of HANA Landscape: Sizing the scope of SAP HANA is extremely crucial while creating your technical project plan. It helps you to understand maximum benefit from your investment while decreasing the long-standing total cost of ownership. Since the data is effectively compressed in HANA, it is not very easy to guess the amount of memory that would be required. It is best to check the size of the memory by using SAP Quick Sizer tool as well as reports and notes to ascertain the amount of memory that will be used in migration.
  2. Migration Approach: The platform where SAP HANA needs to be migrated needs to be ascertained before beginning with the process. You can easily deploy HANA on-premise to gain maximum control and low risk or in Cloud to increase flexibility and scalability. All this, at the core, depends on your budget allocation, resources, time and business needs. SAP has its cloud offering called SAP HANA Enterprise cloud, and it includes SAP HANA license, original cloud infrastructure as well as SAP managed services.
  3. Data purging: Data cleansing is crucial for effective migration to SAP HANA. It will lower your risk and reduce your cost drastically as the memory that is required is not certain. This will help in reduction of data footprint, HANA licensing costs, downtime, etc.
  4. Implementation standards: It is advisable to have a lot of time on hand to migrate technical projects as there is a higher risk of codes and backup getting deleted or duplicated. Successful migration of SAP HANA is possible if you follow standard set procedures rather than cutting corners to avoid the time lag.
  5. Trial Run: For any technical migration to be successful on SAP HANA is it best to do a trial run by validating your process in a sandpit environment first. Isolate your untested code and mimic the production without actually doing one. This will ensure that your SAP HANA migration is a success and can support the technical projects in its entirety. This will help you ascertain crucial points like time to migrate, realize the actual prowess of SAP HANA, understand issues in the sandpit environment to avoid time lags later and it gives you a great point of validation of running it in a non-productive environment.
When we talk about data migration from ECC to S/4HANA, we must keep in mind whether-

  • It is a New system
  • We are adopting a System Conversion or
  • Purging of data called Landscape transformation

All ECC to S/4HANA conversions take place on-premise and cannot happen on the cloud. Hence the above scenarios are for businesses that are already using classic SAP business suite. Few prerequisites for a successful data migration from ECC to SAP S/4HANA are installing an SAP Maintenance Planner, update the software using Software Upgrade Manager (SUM), Migrating data, Customizing, etc.


All these are key factors you need to keep in purview about successful SAP HANA data migration.

Vamsi krishna Solution Architect @ YASH Technologies

Related Posts.

Cloud , SAP , SAP HANA
Bringing value enrichment while being cost-effective in managing your AMS
AMS , Application Management Services , SAP , Service Level Agreements , Shared Services
RISE With SAP , SAP , Supply Chain
SAP , SAP Solution , Tricentis Test Automation

Tricentis Test Automation for SAP

Mallavarapu Lakshmi Prasanna

ChaRM. SAP , SAP Solution , SAP Solutions , Solution Documentation , Solution Documentation Integration
Analytics , Fiori Applications In SAP S/4HANA , SAP , UX
Why Shared Services are going Digital
Digital , SAP , SAP AMS , SAP Application Landscape , SAP Shared Services
Cloud , Microsoft Azure , S/4 HANA , SAP , SAP On Azure

Add Comments

Comments (02)

No Image
Mar , 2018

Hi There, This is the most brilliant article ever! Please put the permalink part in the post. If someone didn’t comment on it I’d have no idea! Seems we've hit the HANA '2 billion records' issue! During the "Preparation of Tables for Data Transfer" step of a TDMS time slice transfer, we get a short dump in the HANA Sender system: DBSQL_SQL_ERROR - CX_SY_OPEN_SQL_DB SQL error "SQL code: 129" occurred while accessing table "BSEG". Database error text: "SQL message: transaction rolled back by an internal error: Search result size limit exceeded: 4776242334" I've read OSS "2154870 - How-To: Understanding and defining SAP HANA Limitations" and a few related forums. However, the table it is occurring on in the sender system (a HANA system) is BSEG, which is already partitioned (6 partitions of approx. 680 million rows each, totalling 4.7 billion rows). How come we get the limit issue - is the TDMS code somehow not taking partitions into account? The TDMS system itself is a Sybase ASE one but that shouldn't matter. Cheers, Abhi

No Image
Feb , 2018

Hi there I just wanted to say thank you for the tutorial, I really liked it. It's very useful to understand the Data Migration to SAP HANA. I've also used other blog for reference which were quite useful. SAP HANA Thanks!