Two Scenarios: 1. SAP BW is a layer that sits on top of HANA. Traditionally, the SAP BW used to sit on top of the Oracle database and now it was replaced with the HANA. 2. HANA Enterprise - Where you partition and dedicate majority of the capacity to SAP BW and the remaining is dedicated to Hana Enterprise. Hana studio is the software that runs on Hana Enterprise. The difference between BW sitting on top of Oracle database and BW sitting on HANA is: • When BW is sitting on top of HANA, you do not need an aggregate layer, but when SAP BW sits on top of an oracle database, you will need an aggregate layer. • What the aggregate layer does is that it condenses the Data. With an aggregated layer on top of the BW, the report will take a long time to run.

Column Storage1. Better I/O bandwidth utilization2. Higher cache efficiency3. Faster data aggregation4. High compression rates5. Column-based parallel processing6. Parallelization

Three basic types of views: Attribute view - This is same as your master data/dimensions, attribute views are like Dimension, but with difference is that attribute views are fully reusable throughout the system and not stuck up to a single model. Simplifying, these are views on one or more table that can be reused for different purpose. (What this means is that we can use the attribute views in different models. Analytical View - This is basically your star schema. It creates a multi dimensional cube. Calculation Views - This is all the other forms. All the other views.. Calculation views can be referred as combination of tables, attributes views and analytical views to deliver a complex business requirement. Unlike the Analytical view, there is one fact table and multiple dimension table.) Which view we will create will depend on the scenario or the schema or the model.

Data Validation: When you make sure your view has the correct Data. Errors in validation and activation can be analyzed in the Job LogCalculated columns - Lets you perform any arithmetic functions.

Tables: • Master tables are the dimensional table with descriptive objects. These tables define the attributes • Transactional and Fact tables are tables with measure objects.

Primary Folders On Hana Studio Catalog - This is where you have all the tables. (this is where all the logical theories, schemas). The catalog saves your tables. Catalog has your schemas. Database objects are organized in schemas; schemas can be used to group objects and to restrict authorizations, each student works with an own schema. Schemas generated by the system start with _SYS.Content - There is where you do the modeling. This is where your packages and make the joins.

When you do modeling in Hana, you do not do the joins again in the IDT. Universe is used as a pass-through, an interface between HANA and BI.

SAP SQL Script procedures- stored procedures, push application calculations/logic into database, reusable. Define I/O parameters and set language or use default. Scripted calculation views is simpler: set parameters, write SQL statement, execute the script to validate it, and assign attributes and measures to output. Then save, activate and preview. y It is not necessary to build calculated columns for scripted views because the calculations can be handled by the script.

CE Operators-calculation engine operators are processed directly in the CE. Preferred over SQL. Improved performance can be optimized by the engine.

Calculation View - there are two types of calculation views we can have: 1. Graphical- The process flow for graphical calculation views is to set parameters, define nodes, choose tables/views, define mappings, create any calculated measures and define output. Then save, activate and preview the data.2. SQL The 4 different scenarios or layers of a calculation view are:

1. Aggregation 2. Union - This where you put two tables together. Example, combining two dimension tables. Example, Car table and a Bike table: Union takes those two tables and combine them. 3. Join 4. Projection When creating a view in Hana: Always create the view by right clicking on the “Package”

Schemas: Two standards schemas are: 1. Star Schema 2. Snow Flake schema

Three ways to do Data loading on Hana: 1. SLT - Servicer Landscape transformation. It’s separate server, an application tier. Trigger based concept that only considers the tables relevant for data. Allows real-time and scheduled data replication from SAP ERP systems and non-SAP systems into HANA2. BODS - Business Objects Data service (It is an ETL process from heterogeneous sources into a target database). Solution for data integration, data quality, data profiling, and text data processing. Data Services Designer to create, test, and manually execute jobs that transform and populate a data warehouse. Set data flows and workflows.3. DXC - Direct Extractor Connection

Solutions powered by HANA-SAP Netweaver BW, SAP ERP RDS for Operational Reporting, SAP CO-PA Accelerator, SAP Finance and Controlling Accelerator, SAP Customer Segmentation Accelerator, SAP Sales Pipeline Analysis, SAP Smart Meter Analytics, Charity Transformation

Business Objects BI Solutions

SAP HANA Live- is solution for real-time reporting on HANA. It is a separate package that comes with predefined SAP HANA content across SAP Business Suite. Provides SAP-delivered content in form of HANA calculation views, span across majority of ECC modules. The content is represented as a VDM, based on the transactional and master data tables. More than 2,000 views are delivered.

1. query views-views which are exposed for consumption by end user for reporting needs

2. reusable views- customers can build upon reusable views to create their own custom query views

3. private views- views that are built on top of the tables and not intended to be changed.