Dimensional Modeling on SAP Hana

Hello,
I am a newbie on SAP hana, so need help from experts / gurus.
Imagine the following Scenario ---> Oracle ERP is the source System and we want to build a Analytic Solution on Hana. Also assume that tables can be replicated into SAP Hana
Questions
1)For any kind of reporting / Analytics? Should we build a traditional Datawarehouse on Hana with all the features found in a star schema like surrogate keys, conformed facts and dimensions etc? or use only attribute views / analytical views provided as default and build datawarehouse model on top of this? In the second case, do we still need surrogate keys or how can we merge slowly changing dimensions?
2)Where can be push the transformation logic? Into ETL tool or use Hana provided sql script? and also where do we do this transformation, outiside hana where we do all transformations and load only data into normolized format? or within hana using scripts?
3) In any case is dimensional modeling really required on Hana? if not how can we map business process and do analysis on them? is it by means of only the views provided by Hana?
Your help is much appreciated.
Thanks!

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Similar Messages

Transporting Data models in SAP HANA

Hi All,
I was trying to understand how data models can be transported in SAP HANA and came across the different options in the Export option of hana Studio like exporting with Delivery unit, Developer mode, etc.. Can someone please elaborate on the differences between each and the scenrio when each should be used?
Thanks,
Sam

No Justin, haven't used in any "production" environments till now since the client am working for is still to be upgraded to SP7. At internal system we are doing some R&D in those lines and developing artifacts from "Development" perspective.
Here i shared this link for reference itself.
Also i think using Development perspective for modelling is what is being suggested going forward in blogs like this
6 Golden Rules for New SAP HANA Developers
May be John Appleby and his team are already using "Development" perspective consistently
Regards,
Krishna Tangudu

Regarding Modeler in SAP Hana Studio

Hello Experts,
I am trying to connect to SAP HANA Trial System with my in house NSP System through Business Object Data Servicies.
I have completed the steps till configuring the import server in HANA studio now when click on "Import Link" Under Content, i am not getting "information modeler" option to get table structure.
Please help on this.
Please find the screenshot attached here.
Regards
Bhasin

Bhasin,
To import table structure, Click on SAP HANA Content --------> Selective Import of Metadata.
Once you click on above, it will ask you to mention Source connection details and type of import objects like tables & extractors.
Regards,
Kulwinder

SAP HANA modelling Standalone

Hello Experts,
We are in the process of HANA Standalone implementation and design studio as reporting tool. When I am modeling, I did not figure out answers to some of the below questions .Below are the questions. Experts, please help.
Best way of modeling: The SAP HANA LIVE is completely built on calculation view; there are no Attribute and Analytical views. I have got different answer why there is only Calculation view and there are no Alaytic view and Attribute views. We are in SP7 latest version. This is a brand new HANA in top of non-SAP (DB2 source). What is the best way to model this scenario, meaning, can we model everything in the Calculation view’s like SAP HANA live or do you suggest using the standard attribute, analytical and calculation views to do the data model. Is SAP moving away from AV & AT to only calculation Views to simply the modeling approach?
Reporting: We are using the design studio as front end tool. Just for example, if we assume that we are
Using the BW, we bring all the data in to BW from different sources, build the cubes and use the bex query. Here in bex query we will be using the restricted key figures, calculated key figures calculations etc. From the reporting wise, we have the same requirements, calculations, RKF, CKF,Sum, Avg etc. if we are Using the design studio on top of standalone HANA, where do I need to implement all these calculations? Is it in different views? (From reporting perspective, if it’s BW system, I would have done all the calculations in BEx.)
Universe: If we are doing all the calculations in SAP HANA like RKF. CKF and other calculations , what is the point in having additional layer of universe , because the reporting compnets cam access the queries directly on views .In one of our POC , we found that the using universe affect performance.
Real time reporting: Our overall objective is to give a real time or close to real time reporting requirements, how data services can help, meaning I can schedule the data loads every 3 or 5 min to pull the data from source. If I am using the Data services, how soon I can get the data in HANA, I know it depends on the no of records and the transformations in between the systems & network speed. Assuming that I will schele the job every 2 min and it will take another 5 min to process the Data services job , is it fair to say the my information will be available on the BOBJ tools with in 10 min from the creation of the records.
Are there any new ETL capabilities included in SP7, I see some additional features included in SP7. Is some of the concepts discussed are still valid, because in SP7 we have star join concept.
Thanks
Magge

magge kris wrote:
Hello Experts,
We are in the process of HANA Standalone implementation and design studio as reporting tool. When I am modeling, I did not figure out answers to some of the below questions .Below are the questions. Experts, please help.
Best way of modeling: The SAP HANA LIVE is completely built on calculation view; there are no Attribute and Analytical views. I have got different answer why there is only Calculation view and there are no Alaytic view and Attribute views. We are in SP7 latest version. This is a brand new HANA in top of non-SAP (DB2 source). What is the best way to model this scenario, meaning, can we model everything in the Calculation view’s like SAP HANA live or do you suggest using the standard attribute, analytical and calculation views to do the data model. Is SAP moving away from AV & AT to only calculation Views to simply the modeling approach?
>> I haven't read any "official" guidance to move away from typical modeling approach, so I'd say stick with the usual approach- AT, then AV, then CA views. I was told that the reason for different approach with HANA Live was to simplify development for mass production of solutions.
Reporting: We are using the design studio as front end tool. Just for example, if we assume that we are
Using the BW, we bring all the data in to BW from different sources, build the cubes and use the bex query. Here in bex query we will be using the restricted key figures, calculated key figures calculations etc. From the reporting wise, we have the same requirements, calculations, RKF, CKF,Sum, Avg etc. if we are Using the design studio on top of standalone HANA, where do I need to implement all these calculations? Is it in different views? (From reporting perspective, if it’s BW system, I would have done all the calculations in BEx.)
>> I'm not a BW guy, but from a HANA perspective - implement them where they make the most sense. In some cases, this is obvious - restricted columns are only available in Analytic Views. Hard to provide more complex advice here - it depends on your scenario(s). Review your training materials, review SCN posts and you should start to develop a better idea of where to model particular requirements. (Most of the time in typical BI scenarios, requirements map nicely to straightforward modeling approaches such as Attribute/Analytic/Calculations Views. However, some situations such as slowly-changing dimensions, certain kinds of calculations (i.e. calc before aggregation with BODS as source - where calculation should be done in ETL logic) etc can be more complex. If you have specific scenarios that you're unsure about, post them here on SCN.
Universe: If we are doing all the calculations in SAP HANA like RKF. CKF and other calculations , what is the point in having additional layer of universe , because the reporting compnets cam access the queries directly on views .In one of our POC , we found that the using universe affect performance.
>>> Depends on what you're doing. Universe generates SQL just like front-end tools, so bad performance implies bad modeling. Generally speaking - universes *can* create more autonomous reporting architecture. But if your scenario doesn't require it - then by all means, avoid the additional layer if there's no added value.
Real time reporting: Our overall objective is to give a real time or close to real time reporting requirements, how data services can help, meaning I can schedule the data loads every 3 or 5 min to pull the data from source. If I am using the Data services, how soon I can get the data in HANA, I know it depends on the no of records and the transformations in between the systems & network speed. Assuming that I will schele the job every 2 min and it will take another 5 min to process the Data services job , is it fair to say the my information will be available on the BOBJ tools with in 10 min from the creation of the records.
Are there any new ETL capabilities included in SP7, I see some additional features included in SP7. Is some of the concepts discussed are still valid, because in SP7 we have star join concept.
>>> Not exactly sure what your question here is. Your limits on BODS are the same as with any other target system - doesn't depend on HANA. The second the record(s) are committed to HANA, they are available. They may be in delta storage, but they're available. You just need to work out how often to schedule BODS - and if your jobs are taking 5 minutes to run, but you're scheduling executions every 2 minutes, you're going to run into problems...
Thanks
Magge

Creating Logic and modeling for SAP BW datasource in SAP HANA views and SLT

Hi to all,
I have small question.
We have BW system and SAP ECC as source system and to get data from SAP ECC source system we are using SAP ECC Standard data source.
Now we required to, create modeling in SAP HANA by use of HANA View and get data from SAP ECC source table via SLT.
So we can replicate same modeling,as we done in SAP BW system.
But my question is that, as SAP ECC standard data source hit multiple table and do run-time calculation, before sending to SAP BI.
How we can derives such calculation and logic, in our HANA studio, because as we know in SLT data transformation can be done in limited way also
in view we can not drive such logic via SQL script ?.
Is there any way we can do such modeling and logic in SAP HANA ?
or
is there any standard document for this type of case, which we can use ?
Note: We don't want to use SAP DS or DXC for data loading to HANA, as we want it in more real time.
Regards
Pavneet Rana

Thanks for reply,
As SLT is based on ABAP, so we can write complex logic in it.
But if we talk about SAP ECC standard data source, they have complex logic, based on multiple table.
So we need to write code from scratch in SLT to derive same result. but it will be huge time consuming , and required good ABAP skills, also it will lead to bug in code.
Also it will reduce the real time performance of SLT, due to complex logic.
Second option is procedure via SQL script, which is again huge effort in term if logic and can lead to error/bug in logic.
Does we have any other way or architecture to do this is very simple way, with high performance and less error issue.
Regards
Pavneet Rana

How to use Variable in SAP HANA Information Modeller?

Hello Folks,
I have created a variable in Information modeller of SAP HANA Studio on top of an Analytical view (Regional Sales). This variable is SingleValue (Multiple Value Selections). This variable should prompt me the name of Country/Regions but somehow this is not working when I am using data preview and Analysis tab of data preview.
Could you please enlight me where I am going wrong? or Let me know if is there any other forum for this.
P.S : I am using SAP HANA studio on Cloud.
Regards
Muffazzal Fani

Hi,
After you created that variable as mentioned above, did you apply this variable on your LAND1 attribute.
How: Open Analytic View --> on right-side you see the attributes,measures etc. >right click on 'LAND1' and select>
'Apply Filter'--> In the drop-down select your created variable and activate.
I assume the above should resolve your issue. Please let me know if it helps.
Revision: I mean the HANA version you are using.
Regards, Rahul

What is SAP HANA DXC ???

Hi SAP HANA Experts,
Can anyone you tell me what is SAP HANA DXC ???
Is it a Add-On Or inbuilt software component available with SAP HANA DB Package Itself
Do we need to download the SAP HANA DXC individually ???
What is the path of the DXC Software component in SMP to view it

Hello guy,
The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. (No add-on need to be installed). DXC is also a data acquisition method for SAP HANA. With DXC, SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA
Refer to:
http://help.sap.com/hana/sap_hana_direct_extractor_connection_implementation_guide_en.pdf
1665602 - Setup & Config: SAP HANA Direct Extractor Connection (DXC)
Regards,
Ning Tong

New SAP HANA course released

Course: TZH300 u2013 SAP HANA Implementation and Modeling course released on SAP HANA 1.0, SP03 (https://training.sap.com/us/en/course/tzh300-sap-hana-implementation-and-modeling-classroom-096-us-en/)
Schedule:
February 20-21: North America virtual but more events are planned based on demand
Registration:   Contact SAP Education North America Customer Interaction Center at 1-888-777-1727
Course Goals: (1) Replicate data using SAP Landscape Transformation (SLT) and (2) Implement information models in SAP HANA
Target Audience: Data Modeling Consultants
Release: SAP HANA 1.0, SP03
Content:
Trigger-based replication with SAP Landscape Transformation (SLT)
Approaching SAP HANA Modeling
Connecting tables
Advanced Modeling features
     Hierarchies
     Restricted & Calculated Measures
     Filter Operations and Variables
     Currency conversion
Introduction to SQL script and Script based Calculation Views
Processing Information Models
Managing Modeling Content
SAP HANA User Management and Privileges.
IMPORTANT NOTE: Soon, weu2019ll have two more HANA courses, TZBWHA for customers running BW on HANA and TZH200 for consultants who are responsible for installation and administration of HANA. More on those as we get closer.

Hi and thanks for your answer.
I'm not looking for specifics BAPI but for all...I search a technical document of HANA with all the changements in BAPI.
I've to write a document about that for my boss and I found nothing on the web...
Thanks again,
Regards,
Lionel
(I'm french and I don't speak english very well so scuse me )

SAP HANA Performance Optimization

Hi Experts.
Is there any documentation out there that relates to optimizing SAP HANA components such as optimizing the SAP Hana models, data loading using SAP LT, etc. I would like to fine-tune what I have already built.
Thanks,
Regards,
Thatoyame
Email: [email protected]

Hello Thatoyame,
since HANA is pretty fast in so many cases, there isn't much available about general performance tuning. In cases where performance isn't great, a detailed root cause analysis (i.e. trace) is the way to go. See SAP HANA Appliance Software – SAP Help Portal Page (Admin section) for some details on tracing.
For data modeling, check Werner Steyn's webinar at Building Advanced Data Models with SAP HANA - Webinar Details.
Regards,
Marc
SAP Customer Solution Adoption (CSA)

Issue while creating Virtual provider based on HANA Model in SAP BI

Dear Experts,
I try to create a Virtual Provider based on HANA Model. However receive below error "Unable to find SAP HANA information model".
I tried to assign the appropriate package and HANA model while creation of Virtual provider in SAP BI using RSA1 Transaction.
Do I need to enable any services/ settings, so that I can able to use HANA Models in SAP BI?
Do I required any specific authorizations either from BI or HANA side?
Could some one kindly help to resolve this issue.
Thanks,
Khader

Hi Srinivasan,
Thank you for your response.
I have already gone through the content provided via above links.
However I face issue while activating the virutual provider with warning message"Unable to find SAP HANA information model". Due to which I am not able to see any data from Virtual Provider in BW.
Do we need to have any special access/ role in BW or HANA system in order to consume HANA models in BW (Vitual Provider in this case)?
I am trying to consume HANA Models in BW for the first time.
So any more clues can be helpful.
Thanks,
Khader

Error when Hana cube are imported in SAP Hana models management

Hello
I trying to import 2 or more cubes in the module SAP Hana models management and i cannot do it, the message error says that a model exists with the same name but the name of my model is different. I checked my Info.xml and the tag of name is different. How can i import more than one model in this module?
Thank you.

Hi San Xu,
I am working with SAP 9.0 PL:10 hot fix1 and i can´t see which is the IA tag or you refered B1AVersions tag, this is the code for my info.xml
<?xml version="1.0" encoding="utf-8" ?>
- <HANAModelPackageForB1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" defaultLanguage="English">
<Name>Cubo circulo bizarro</Name>
<Author>Agasys S.A. de C.V.</Author>
<ModelVersion>1.1</ModelVersion>
- <HANAVersions>
<Version />
</HANAVersions>
- <B1Versions>
<Version />
</B1Versions>
- <B1AVersions>
<Version />
</B1AVersions>
<Description />
- <Metadata>
<CreatedAt>03/06/2014 01:47:11 p.m.</CreatedAt>
<ChangedAt>03/06/2014 01:47:11 p.m.</ChangedAt>
<ChangedBy />
</Metadata>
- <ModelList>
<Model name="SYS_AT_PCLIENTES" type="AttributeView" />
<Model name="SYS_AT_PDEVOLUCIONES" type="AttributeView" />
<Model name="SYS_AT_PSUCURSALES" type="AttributeView" />
<Model name="SYS_AT_PTRANSACCIONES" type="AttributeView" />
<Model name="SYS_CA_PCIRCULOBIZARRO" type="CalculationView" menu="SYS_CA_PCIRCULOBIZARRO" />
</ModelList>
</HANAModelPackageForB1>
Thanks

SAP HANA Modeling Sample end to end Project

Dear All,
I got trained on SAP HANA Modeling and BODS recently, and in process of learning SAP BO. My core is SAP EP and don't have indepth knowledge on SAP BI and Functional aspects.
I am working on few sample applications but I would like to do a Sample end to end project on real time scenarios/POC's.
Do you have any sample requirement documents that helps to do a end to end project(real time scenarios) . Does SAP store any piolet project requirement specs for public use which help to gain real time experience.
Kindly help me on this.
Thanks & Regards,
Rajeev Bikkani

hi look into this
Role of a Functional Consultant in an End To End Implementation
1. Functional consultant is expected to generate knowledge about the current business process, design current business flows, study current business processes and its complication, in all we can say getting through with current business setup. Flow diagrams and DFD are prepared, most of the time in Vision format, all this forms the part of AS IS document.
2. Everything configured has to be documented as per their categories in the form of predefined templates, these have to be then approved by the team leads or who ever the consultant is reporting to.
3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per my experience in implementation, it is a simultaneous process.
4. Before starting configuring future business processes in SAP, the DFD/ERD are prepared, this documentation is called TO BE, which can be also siad as the result of mapping and gap analysis.
5. Sometimes Functional consultants are also expected to prepare test scripts for testing the configured scenarios.
6. End user manual and user training is also expected from F.Consultants.
The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodology, dates and schedules, working hours which have been predicided are formally defined.

Are SAP HANA implementations on HANA as a Database or HANA as a Modeling tool

Hi all,
I've a general question today about the HANA as a product.
I want to know if most of the SAP HANA implementations that have been carried out in the last 3 or 4 years, were they mostly on HANA as a InMemory Database product or was it implemented as a Modelling tool. What I understand is most of the implementations on HANA have been done with HANA as a database replacing the customer's existing databases mostly Oracle or SQL Server. There are lots of case studies available on this situation. But I am not able to find any information on the clients who have chosen HANA as a Modelling tool along with HANA as a database.
In other words I am interested in knowing a rough estimate/number of customers who have implemented SAP HANA Modelling as a tool. Are there any success factors or case studies available giving facts and figures as to how customers have benefited by modelling on HANA. Assuming that the customer/s who have implemented HANA Modelling were on SAP BW 7.0 earlier I want to know how did they benefit by going for HANA Modelling using HANA Studio and why did they move from BW Modelling to HANA Modelling and what were the benefits they have reaped in.
How is it different from modelling data in BW DSOs and Cubes and MultiProviders,and modelling the same in Attribute Views, Analytic Views, Calculation views and native HANA SQL.
Please explain.
Thank you.
Regards,
Pavan.

A) hana is a database, which combines memory and technology.
A common hana server has at leaste 128gb ram. why? because the tables (or columns of that tables) are loaded in memory and are consumed from there. Hana uses compresion (1:11 ratio) and use columnar tables, because it speeds up the data reading from the database.
Hana have 3 parts of storage:
1) memory (explained above)
2) data: the disk where data is recorded
3) log: the disk where the last transactions are logged and it provides with recovery fails
B) you can have diferents scenearios (I will explain some of them):
BW on hana: it speeds up the data access due to hana technology
suite on hana: ERP and BW on hana
Hana has your DW database: you can use hana like a common database and benefits your organization with the speed of hana.
hope it helps.
this image can show you the diferents scenarios
http://esj.com/articles/2014/07/25/~/media/ECG/VirtualizationReview/Images/2014/07/0714vrm_hana.png

Designer - Dimensional modeling

Can Designer do Dimensional modeling ???
Welcome replies directly to my personal email.
Thanks!

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Dimensional modeling scenario

Hi Experts,
I am having a requirement to do dimensional datamodel for a datawarehouse for the below scenario. Please provide me your suggestions. How many dimensions and facts which i should consider for this? Given below is my requirements.
Percentage and Numbers of care plans due for review, indate or expired
Analysis by home, keyworker, client
Drill down to home by client
Drill down to keyworker by client
Drill down to client
Source OLTP Tables
Patient : (PatientInfo)
=========
clientName
clientAdress
Age
Staff: (StaffInfo/Keyworker)
============
StaffName
StaffDept
DOB
Careplan:(This table will holds Patient Careplans)(1:M)
=========
Expected Outcome (Expected Result of this actionplan)
Current Situation (Current condition of patient)
Action (what is the action taken for the result)
Start Date (patient start)
review Date (for every care plan there will be review date and on that date this record will expire and create a new record with the current situation)
EndDate (End date of patient)
Keyworker(Staff which is in primary charge for this patient- A staff can be keyworker for multiple patients)
thanks
MUS

Hi Rajiv,
I'm no expert either and am just beginning to learn HANA, but here are my thoughts (community, please correct me if I am mistaken.):
1. HANA leverages existing data modeling theories, such as the entity relationship model. This model is simply a way of organizing tables in a way that makes sense for reporting. For example, the star schema, optimized for analytical reporting. The HANA view is similar to a universe, it allows the end user to connect to it from their BI tool. In the background, the modeler still needs to pull in tables, create joins, leverage primary and foreign keys, etc. So in short, traditional modeling practices and theories still come into play.
2. If extracting and transforming data using SAP's Data Services, the transformation of data will happen in HANA, using the Data Quality Management GUI.
Just as a side note, HANA has 3 methods of extracting
data:
Data Services
SAP Replication
Server
SAP Landscape
Transformation
3. Yes, dimensional modeling is still required. At the end of the day, HANA is still a database. We
haven’t changed the theory of data modeling, it still needs to happen, our approach is just different.
Hope that helps.
Kyle

Dimensional Modeling on SAP Hana

Similar Messages

Maybe you are looking for