Jun 7, 2017

What is SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA

What is it?
SAP BW/4HANA – The NEXT GENERATION OF DATA WAREHOUSE – has been announced and released for three quarters.   I think most of you must be very clear about the selling points and strength of BW/4HANA by now, and you may notice that except all the advantages we have on the new platform, there is one important functionality missing – PLANNING (probably CONSOLIDATION as well).
The good NEWS is that a new SAP Business Planning and Consolidation (aka SAP BPC) is now released on the new data warehouse – SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA! (oops, you may think I forget ‘Objects’ after ‘Business’… but it’s on purpose, yes… rename is happening again…)

After years of having two flavors of BPC as BPC NW and BPC MS, now we are having the third! Some important points:
  1. SAP BPC, version for SAP BW/4HANA (will be referred as BPC BW/4 for the rest of this blog) is NOT a legal successor of SAP BPC, version for SAP NetWeaver. Any existing BPC NW customer any need additional license to use BPC BW/4, details will be provided in later in another thread.
  2. By the version number 11.0, you may already figure out that BPC BW/4 is offering with both Planning and Consolidation capability via standard and embedded model. As a starting point, it inherited most of the functionality from BPC NW. Of course, there are new changes/enhancements as well.
  3. Due to the fact that it’s BW/4HANA platform which is always use HANA database, BW-IP and BPC standard on xDB is no longer supported.

Initial release of SAP BPC 11.0, version for SAP BW/4HANA is planned for end of May 2017 and it will be followed by another three support packages until the end of 2017 (as always, it’s subject to change). Incremental changes can be expected within those SPs.
What’s the relation to S/4HANA?
When I was talking to SAP colleagues, partners or customers about SAP BPC supporting BW/4HANA platform, a frequent asked question is, how is it related to S/4HANA and BPC optimized for S/4HANA? Let’s start with below diagram.
  • The left grey box is S/4HANA with an ‘Embedded BW’ which include BPC 10.1 NW as planning and consolidation engine. It’s based on BW 7.5x(BW 7.51 for S/4HANA 1610 and BW 7.52 for S/4HANA 1709) which on SAP NetWeaver platform.
  • The right blue box is SAP BW/4HANA with add-on SAP BPC version for BW/4HANA installed.
  • Both boxes are on separate servers with different platform, so BPC BW/4 is NOT related to S/4HANA at all (at least for now). And don’t ask me when they will be related because I have no idea L.
  • And for positioning, they also different since BW/4HANA is a data warehouse gather all kinds of business data from different sources while S/4HANA is only for financial and operational data (in most cases).
What’s the selling points?
  • ONE product – BPC BW4 – offering on BW/4, unlike NW platform, we have BPS, BW-IP, BCS and BPC.
  • Following the trend of BW/HANA, BPC BW/4 focuses on simplifying the backend core frontend as well as frontend.
  • Simplify the ad-hoc reporting with enhancement in query and Analysis for office
  • New web worksheet concept is introduced to simplify the web reporting/planning objects. Within one worksheet, you can have multiple grids and charts for reporting and data input.
  • Simplified data integration can reduce the effort and time load data from external sources into BPC
Modern Interface
  • Deeper integration with SAP Analytics Cloud (wait… what is it? Bingo, it’s aka SAP BusinessObjects Cloud. Yes, it’s also renamed… sweating…) allows business user to quickly sync data back and forth between BOC and BPC at story level. This also will enable BPC BW/4 customer to leverage BOC web client as an alternative option for both planning and analysis with BPC data.
  • Re-designed Fiori like HTML5 web interface provides a fresh new look and feel. Hamburger menu and bread crumb navigation helps user to jump between different features with fewest clicks.
  • Brand new home page including nicely pinged tiles for charts, quick access to any object and page via ‘Favorites’ and personal activities ordered by time. In additional, user can personalize the home page by re-ordering and re-sizing. (Getting excited, aren’t you?)
  • New concept of web worksheet allows having multiple reports, input forms and charts.
  • Re-signed ‘My Activities’ and BPF workspace design time.

  • Push down query formula operation to HANA
  • Further push down of FOX formulas to HANA
  • Using aDSO for planning

Which Excel client shall I use?
SAP Analysis for Office 2.4 SP04(onwards) is the Excel add-in software shall be used.
  • EPM Plug-in shall be used for BPC Standard
  • AO Plug-in shall be used for BPC Embedded
  • EPM Add-in 10.0 is NOT supported anymore on BPC BW/4

What features are removed from BPC BW/4?
  • EPM Unwired is not supported anymore
  • Virtual Provider in general and for planning special with Writeback Class is NOT supported
  • FIM Integration
  • Custom Branding
That’s almost all I would like to share within this overview, you may already have a question about how to migrate existing BPC NW customer to BPC BW/4. A very good question though, but with initial release BPC BW/4, the conversion tool (it’s now called conversion since BPC BW/4 is not the legal successor of BPC NW) is not ready. We will talk about conversion in detail in following blogs, and please wait as well for other BPC BW/4 relate content!

Additional information:
SAP BPC 11.0, version for SAP BW/4HANA Product Availability Matrix

Apr 7, 2017

The Road to SAP BW/4HANA – Part 2

In the first part, we looked at the different paths to get to SAP BW/4HANA. Now let’s see which path makes the most sense for a given starting point of a customer’s landscape.

One or More Legacy Systems

Unless you are a brand new enterprise, your landscape will most certainly contain some databases or systems that are collecting various kinds of data. Now you realize that you need a way to define common semantics, harmonize data values, establish a ‘single version of truth’, and provide a single, comprehensive source of current and historical information across all these sources. You need a data warehouse… SAP BW/4HANA. The obvious path is to install a new SAP BW/4HANA system, connect all your data sources, and either load the data (traditional ETL) or consume the data remotely (logical data warehousing). Of course you want to put some thought into modeling and structuring your SAP BW/4HANA data warehouse so we recommend defining a layered scalable architecture that suites your requirements best based on the LSA reference framework provided by SAP.
Instead of rebuilding your legacy system or data warehouse completely in SAP BW/4HANA, you could move some or all of it directly into the SAP HANA database that SAP BW/4HANA is running on (separate schema or tenant). You can then leverage the content using mixed models between SAP BW/4HANA and SAP HANA views.
If you have a complex landscape, want to replace legacy data warehouse(s), or simply need help on your way to SAP BW/4HANA, please consider the path of using services offered by the SAP’s Data Management & Landscape Transformation group. We will setup a project that will lead you to a successful implementation of SAP BW/4HANA.

SAP BW powered by SAP HANA with SAP BW/4HANA Starter Add-on (aka SAP BW, edition for SAP HANA)

If you are running this release of SAP BW, are exclusively using objects compatible with SAP BW/4HANA (Advanced DataStore Objects, Open ODS Views, CompositeProviders, etc.) as well as using SAP BusinessObjects (or a supported third party frontend), then your system is mighty close to be ready for transitioning to SAP BW/4HANA. Perform a final system check using program RS_B4HANA_CHECK_ENABLE. If you get all green lights, your system can be converted to SAP BW/4HANA!
As mentioned in Part 1, the conversion tool is not quite ready for this job. You will have to wait for a bit until the required enhancements are completed. There’s no firm timeline available yet.
Although new installation or landscape transformation are technically possible paths, it’s quite unlikely that you would go this way because the system is just one step away from SAP BW/4HANA.

SAP BW powered by SAP HANA

About 3,600 customers are running this release. Go, BW on HANA! If you started your SAP BW implementation recently or have kept you system up-to-date with release upgrades to 7.5, then you are in a similar situation as customers who already have SAP BW, edition for SAP HANA. Upgrade slightly older systems to release 7.5 and install the “SAP BW/4HANA Starter Add-on”. If necessary, transfer classical to HANA-optimized data models and data flows. This might be the case, especially if you did a straight migration from another database in the past and continue to use InfoCubes and classic DSOs i.e. you haven’t fully transitioned to Advanced DSOs, CompositeProvider and Open ODS Views. We have a Transfer Tool (SAP Note 2238220) available, which will do this job for you.
If your system is still on release 7.3 and you are upgrading to 7.5, then you might have to adjust some of your custom code due to the change that came with 7.4. Please review SAP Note 1823174.
Generally, we recommend the system conversion path but in some cases you might want to consider a new installation approach. SAP BW powered by SAP HANA systems can be over four years old (yes, SAP HANA has been around that long). If you don’t want to go through the steps described above, you could go for a new SAP BW/4HANA instance, maybe transport objects and configuration (as far as possible and supported, see SAP Note 2361350), and reload data from your original system. This will give you a clean start into the SAP BW/4HANA world.

SAP BW on Any Database (other than SAP HANA)

The most challenging scenario can be a SAP BW system still running on other databases than SAP HANA. Here all three paths to SAP BW/4HANA are currently at par. To convert the complete system to SAP BW/4HANA will require a database migration, release upgrade, transfer to HANA-optimized objects, and custom code adjustments. A Unicode conversion will be required as well for non-Unicode systems.
We have done migrations to SAP HANA many times now, so overall the process is well understood and can be executed smoothly. Still, we are working to make this transition as seamless as possible.
The alternative is to go for a new installation of SAP BW/4HANA and build a new, simplified data warehouse environment. Added benefit is that your original system will not be impacted.
If your SAP BW system and data warehouse landscape is more complex, please contact SAP and check the many services that are available to help you. And of course many SAP Partners have similar offerings in their portfolio.

Multiple SAP BW Systems

We certainly see a trend to simplify landscapes and consolidate several SAP BW systems into a global instance running on SAP HANA. If you have multiple SAP BW systems – typically split by region or line of business -, then we recommend to check out the Landscape Transformation path. It’s best suited for customers who want to consolidate their landscape or carve out selected data models and data flows into an existing SAP BW/4HANA system. SAP’s Data Management & Landscape Transformation group is planning to offer a service package in order to setup a customer-specific migration project. This will include re-using standard tools for example to compare the configuration and security of your SAP BW systems.
Alternative is to treat the situation the same way as described in the “One or More Legacy Systems” chapter.
SAP BW/4HANA - Which Path is Right for You?


We understand our customers are starting their journey to a modern data warehouse from different places. That’s why we have created three distinct paths, complete with distinct services and tools, to help you achieve your goals in the most direct fashion, with the least disruption.
For more information about SAP BW/4HANA, please see the SAP Community Network and check out the FAQ document.

Source : https://blogs.saphana.com/2016/09/18/the-road-to-sap-bw4hana-part-2/

Mar 27, 2017

The Road to SAP BW/4HANA – Part 1

One of the most frequently asked questions is how you can get from your current data warehouse landscape to SAP BW/4HANA. At SAP, we realize each of our customers are starting their journey to a modern data warehouse from different places. That’s why we have created distinct paths, complete with distinct services and tools, to help you achieve your goals in the most direct fashion, with the least disruption.
One heads up: We are working on a “Conversion Guide” which will document all options and required steps in detail.
First, let’s look at the different implementation paths. In part two of this blog, we will take your starting point into consideration and show which is the recommended path or a possible alternative. For now, keep in mind that all three paths are applicable for mostly any existing landscape.

Path 1 – New Installation

Also referred to as “greenfield approach”, this path start by installing a brand new SAP BW/4HANA system. Get the SAP BW/4HANA master guide and follow the steps to check prerequisites, plan and prepare your landscape and installation. Then start the installation using the SAP Software Provisioning Manager. There is a new automated task list available to simplify the basic system setup tasks, like creating and configuring the SAP BW/4HANA background user, setting the SAP BW/4HANA client and installing the essential technical content.
Now there are two basic options for configuring your new SAP BW/4HANA system. Either you begin from scratch, connect any data sources – that could be a legacy data warehouse or any other data source available in your enterprise – and start modeling you data warehouse. We highly recommend following our layer scalable architecture framework (LSA++). Within minutes you can create your first queries and show data in a dashboard. Yes, it’s that simple now thanks to so called “HANA source systems”, field-based modeling, and a modern user experience for designers in Eclipse.
If you run already a SAP Business Warehouse (BW) system today and want a fresh start, you can get a head start by transporting certain configuration and data models from your existing landscape to SAP BW/4HANA. Please note that this is only supported for the initial system setup, not for continuously updating the new landscape. And, of course, it’s only supported for objects that are fully compatible with SAP BW/4HANA. If you are, for example, running already SAP BW powered by SAP HANA 7.4 and have used Advanced DataStore Objects and CompositeProviders, you could transport these to your new SAP BW/4HANA system.

Path 2 – System Conversion

Before we get ahead of ourselves, the option to convert an existing SAP BW system to SAP BW/4HANA isn’t available yet. Stay tuned… this isn’t the end of the world since there are some prerequisites that you can work on in the meantime. Following very much the strategy for data warehousing and recommendations we laid out for SAP BW customers in the past years, your intermediate target is to get to SAP BW powered by SAP HANA and transition to data models that are fully optimized for SAP HANA. That means, for example, no more InfoCubes and MultiProviders but using Advanced DataStore Objects for persistency and CompositeProviders for modeling joins and unions of your persisted or maybe even remote data.
Side note: The time of logical data warehousing is here and thanks for SAP HANA smart data integration it’s easier than ever to integrate many data sources without having the load the data. This approach can get you started quickly but does not overcome limitations in terms of performance of the source system or network capacity or latency connecting to the source. If your source is however on SAP HANA and in the same data center (or maybe just in another tenant in the same SAP HANA database that SAP BW/4HANA is running on), then please give it a go. Create an Open ODS View on top of the source data and use it in your data warehouse models. For maximum performance, you can always generate a Data Flow and Advanced DataStore Object to persistent the data in SAP BW/4HANA. Piece of cake!
As stated at the beginning, we want to make the transition as seamless as possible. For that reason, we developed a so called “Transfer Tool”. The tool is currently available as part of the SAP BW, edition for SAP HANA add-on (which installs in on your SAP BW 7.5 powered by SAP HANA system). This transfer tool allows you to create SAP HANA-optimized objects for all your standard SAP BW data models. Pick a data target, like a MultiProvider and the tool will determine all dependent object like InfoCubes, classic DataStore Objects, transformations, and DTPs and allow you to quickly create equivalent CompositeProviders and Advanced DataStore Objects including matching transformations and DTPs. We are working hard to make this tool work on a system-wide level to make the transition as seamless as possible.
The result is that you are running your SAP BW system as SAP BW, edition for SAP HANA which will take you directly to SAP BW/4HANA using a System Conversion process.
If you paid close attention, there are two main prerequisites here: First, you have to run SAP BW on the SAP HANA database and secondly, your system must be on the current SAP BW 7.5 release. If your system isn’t quite there yet, then as part of the project you will do a database migration and release upgraded. These can be combined – as we have done for several years now – using the Database Migration Option (DMO) for the Software Update Manager.

Path 3 – Landscape Transformation

The third and final option is to optimize more complex data warehousing landscapes resulting in a single, global SAP BW/4HANA system. One reason could be that you are running multiple legacy or SAP BW systems which you want to consolidate on the mighty SAP HANA platform. Another could be to carve out selected data models or flows into an existing SAP BW/4HANA system. In any case, the Data Management & Landscape Transformation team at SAP can help with a customer-specific migration project built around well-defined methodology and re-using standard tools.
One of the innovative tools is the “System Comparison Workbench” which can show you, for example, differences between several regional SAP BW systems and help define a strategy to integrating these into a global data model.
For a presentation style version of this blog (“The Road to SAP BW/4HANA”) and many more details on SAP BW/4HANA, 
please visit the SAP Community Network.

Feb 12, 2015

Share the Knowledge - Optimizing SAP BW on SAP HANA Part 2

Via Content in SCN

Hi Everyone,

Best Practice # 7: Avoid Issues During Migration by  Using Automated Task Lists

We were told about optimizing System Migration
1.) Use the Checklist tool:It is recommended to run it before, during, and after migration for optimal insights
2.) Setup Task lists: use task lists for system preparation and system copy
3.) Run Post Migration Program

Go to Migration tab

After that a little bit intro about DMO was given
DMO(Data Migration Option) is an option of SUM (Software Update Manager) for a combined update and migration: update an existing SAP system to a higher Software Release and migrate to SAP HANA database.
To learn more about DMO check the below documents:
Also check SAP Note 1799545 - Using DMO of SUM for SAP BW systems

Best Practice # 8: Validate SAP HANA Configuration,  Check Table Consistency and  Monitor Delta Merge

Use the Checking Tab of BW Migration Cockpit:
Rerun the checklist tool
Run Table Consistency check
Run Delta Merge Check
To learn more about Delta Merge process, check the below document:
Also check SAP Note 1663501 - Log for BW merge trigger

Check if Secondary indexes are required to be created
Also check SAP Note 1740373 - DSO: Maintenance of database indexes in SAP HANA

Best Practice # 9: Improve Performance and  Simplify Administration and Infrastructure by  Converting Data Flows and InfoProviders

Go to Conversion tab
Optimize Data Flows: Convert 3.x Data Flows to 7.x Data Flows
For migration, also check the below link:

Optimize InfoProviders: Conver Infocubes to HANA Optimized Infocubes

Learn more about InfoProviders in BW on HANA:
Also check SAP Note 1849497 - SAP HANA: Optimizing standard DataStore objects

Optimize Data Layers:
To learn more about LSA++, check the below documents:

Use BW Transform Finder to quickly find transformations in SAP NetWeaver BW systems - for example to identify InfoProviders that can potentially be retired when using SAP HANA.
Check SAP Note 1908367 - SAP NetWeaver BW Transformation Finder

Best Practice # 10: Tune Custom Code According to  Best Practices for ABAP on SAP HANA

Go to Optimization tab
Use ABAP Routine Analyzer that automates the check of best practice guidelines for ABAP routines in SAP NetWeaver BW systems focused on statements that can potentially be optimized for SAP HANA
To learn more about ABAP Code optimizzation for SAP HANA, check the below documents:

The tools mentioned above do most of the tasks but still there can be few activities that we might have to perform manually.
For knowing more about BW on HANA migration and steps involved in it, we should also check SAP BW on HANA Cookbook

Additionally, we can learn more about BW on HANA from the below documents:

Jan 12, 2015

Optimizing SAP BW on SAP HANA Part 1

Optimizing SAP BW on SAP HANA Part 1

Hi Everyone,

During the TechEd I attended lecture RDP303 - "Master Class for Optimizing SAP Netweaver Business Warehouse on SAP HANA"
It was only a 1 hour session but there were many things to learn.
The session was aimed at Optimizing SAP BW on SAP HANA and best practices to be followed
I would like to share learning from the session.

Also check Part 2: Share the Knowledge - Optimizing SAP BW on SAP HANA Part 2

Best Practice #1: Master The Basics and Understand the Path to BW on HANA

The session started with migration options for implementing BW on HANA
There are three options available for implementing BW on SAP HANA and they have their own advantages and disadvantages as shown below:
To learn more about migration, check the below document:

Best Practice #2: Know the Tools That Do the Work For You

After that we were told about BW Migration Cockpit for SAP HANA tool that can  be used for migration and a demo was shown for it
Check SAP Note 1909597 - SAP NetWeaver BW Migration Cockpit for SAP HANA for this and install attached ABAP program - "ZBW_HANA_MIGRATION_COCKPIT"
Once you have installed the program and you execute it, you get the below screen
Best Practice # 3: Ch eck Your BW System : Before and After Migrating to SAP HANA

The first tab is checking
It has three main tools "Checklist Tool", "Consistency Checks" and "Planning Function Check"
Checklist Tool automates the check of best practice guidelines for operations and pre-requisites for migration of an existing SAP NetWeaver
BW deployment to the SAP HANA platform.
Once you click on checklist tool, the below screen appears and you can select which all checks you want to perfo rm
Once the checklist is completed you get the below screen:
To learn more about the checklist tool, check th e SAP Note 1729988 - SAP NetWeaver BW powered by SAP HANA - Checklist Tool
Planning Function Check tool determines whether planning functions are executed in ABAP or in SAP HANA
It uses program RSPLS_PLANNING_ON_HDB_ANALYSIS and it should be installed in your system otherwise you will see the below screen stating "Program RSPLS_PLANNING_ON_HDB_ANALYSIS does not exist"
Check the below blog to learn more about it:

Best Practice # 4: Size Your BW System  Using a Fully Automated Sizing Tool

Go to Sizing tab
In this tab, we can determine memory requirements for SAP HANA using the Sizing tool, can configure NLS, set up Data Archive Process and execute Data Archiving process
To learn more about sizing, check SAP Note 1736976 - Sizing Report for BW on HANA
Also check the below blog on Sizing BW on HANA:

Best Practice # 5: Lower TCO by Leveraging  Non-active Data Concept and Off-loading Data to  Near-line Storage (or Archive)

As we all know that non-active data concept was introduced for BW on HANA last year

Non active tables are loaded into RAM only when they are accessed and are displaced from the RAM with highest priority in case of RAM shortage
In BW on HANA, PSA tables and Write Optimized DSO tables are automatically marked as "Non-Active"

To learn more, check the SAP Note 1767880 - Non-active data concept for BW on SAP HANA DB
After that we were told a bit about Near Line Storage with Sybase IQ
To learn more about it, check the below documents
Also check SAP Note 1796393 - SAP BW near-line solution with Sybase IQ

Best Practice # 6: Keep Your System Lean and Fast by Performing Housekeeping Task Regularly

Go to Housekeeping tab
As we all know Housekeeping activities are an integral part of BW as they ensure optimum utilization of system resources and increase system performance
Some of t he most common activities are:
To learn more about Housekeeping activities, check the below document:
We can set automated Housekeeping using Task Manager and use "Housekeeping Tasks"
Check SAP Note 1829728 - BW Housekeeping Task List to generate a a task list with several common tasks associated with housekeeping/upkeeping an BW system
We can also extend this task list
Check the below document on how to install Housekeeping task list:
Also check the below document:
For Task Manager Configuration, check SAP Note 1589145 - Task Manager for Technical Configuration

We can also perform few housekeeping tasks manually present in the cockpit as shown above, such as
IDoc Archiving
OLAP Statistic Deletion
For cleaning Large tables, check SAP Note 706478 - Preventing Basis tables from in creasing considerably

Jan 7, 2015

How to optimize Reporting Performance in SAP BI

Via Content in SCN

We face many challenges in our BI projects in terms of Reporting Performance. Users always expect outstanding performance of our BI reports. No matter what ever we do in the backend (Modeling and Query Designer). I am going to share very important tips & techniques which I have learned through out my experience which consists of some standard thumb rules too.

It is recommended to use Inclusions Instead of Exclusions wherever possible as Exclusions cant access DB indices and will impact performance. Because, when huge no. of RKFs & CKFs are Included in a Query, Restricting, Conditioning and Computations are done for each of them during query execution. This is very time consuming and a high number of RKFs & CKFs can seriously hurt Query Performance that means, please open your query definition and pick up the fields which are used in the query while defining Aggregates. Delete the unused Aggregates 

If the aggregates are too Large, those not only degrades the Query performance but also loading performance by longer times to roll up and Attribute Change runs also takes longer times. 
Make sure you get good valuation indicators for your Aggregates, but not like below 

It is recommended to to Suppress Result rows Wherever possible. 

It is recommended to use SAP Exits whe re ever possible and bring down the Customer Exits
SAP Suggests free characteristics in reports should be limited to 8-10. 

In RSRV checks, free characteristics usage is marked in red which has very high impact on reports

It is recommended to reduce RKFs & CKFs in the Query to as few as possible.
It is recommended to redefine your Aggregates in an optimized way by taking Statistics(BI Admin Cockpit should be in place) & Query definitions into Consideration.

Archiving (NLS) is recommended to archive unused data.

a. Reduction of online disk storage

b. Improvement in BW query performance

c. Increased data availability as rollup, change runs and backup times will be shorter

d. Reduced hardware consumption during loading and querying

Reports should be designed on Multiproviders wherever possible.

Logical and physical partitioning is recommended for bet ter performance.

Extensive use of Filters at Query level is recommended.

Select appropriate Read mode settings for Multiproviders with "H" and Infosets with "X" in RSDIPROP t-code

Reporting on Infosets should be considered below tips :

a. Do not select all the fields which are part of Infoset definition like below. You can select the fields which we want to use in query only.

b. You should select "Use Selection of Structure Elements" in RSRT-->Properties

c. Do not make too many joins as it cause high runtimes to fetch data after the joins

Statistical Reports performance can be improved by broadcasting query result to cache and prefilling cache.
Deletion of unused Queries is recommended
Delete temporary Query Views is recommended.

It is recommended to be careful while creating Cell Structures as they require high query run times and will lead to performance degradation.

Program RSR_CACHE_RSRV_CHECK_ENTRIES can be scheduled to run on regular basis to remove the unused Cache entries .< /p>

Make proper Query read mode and Cache mode settings in RSRT-->Properties. The recommended Cache mode could be 1 or 5.
Conclusion :
It is always better to keep an eye on above points while developing our Business models and Queries. This blog will help us to satisfy our users with good reporting performance.

Oct 18, 2014

SAP Hana Series - 5

HANA Overview - 5

How is HANA licensed?

SAP tried to keep licensing simple with HANA.

HANA is available in the Cloud as Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and as an application platform (AaaS), and it is possible to buy all those options now, on a monthly basis, from the SAP Website.

For on-premise customers, HANA is licensed in one of two major ways:

First, is as a proportion of your Software Application value (SAV), just like you can license other databases from SAP. This could be for your whole estate, or for a specific product like BPC.

Second, is by the unit, which is 64GB of RAM. There are a few editions of HANA, depending on your need, that bundle other software and allow more, or less, restrictive usage. The pricing is tiered, depending on the number of units you buy, and accretive.

In all cases, HANA licensing includes a lot of functionality that you would pay extra for in other databases. For example, Dev, Test, HA, DR licensing are always included. And if you buy HANA Enterprise, you have access to all functionality at no additional cost – including Predictive Libraries, Spatial, Graph, OLAP, Integration and Web. HANA contains a huge amount of functionality that would require 20-30 different SKUs from Oracle.

For those customers who need the base functionality of HANA but not the bells and whistles, there is now a HANA Base Edition, on which you can add other functionality as required, at a lower cost point.

FeatureHANA BaseHANA PlatformHANA Enterprise
Partitioning, Compression, Security
Calculation Engine, Aggregation Engine
XS Engine, River, SQLScript, HANA Studio
Smart Data Access
Predictive Analytics Library
Search, Text Analysis
System Landscape Transformation, Data Services