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.

Similar Messages

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 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

SAP HANA Model validation error - Index out of range

Hi,
Creating a simple Attribute View using the SYSTEM user.
1. Log on with SYSTEM
2. CREATE SCHEMA EFASHION
3. CREATE THE TABLES UNDER EFASHION
4. LOAD DATA INTO TABLES
5. GRANT SELECT ON SCHEMA EFASHION TO _SYS_REPO WITH GRANT OPTION
Whilst activating/validating the Attribute View, face the following error:
Repository: Activation failed for atleast one object; atleast one runtime reported an error during activation. Please see CheckResults for details
Repository: Encountered an error in repository run time extension : Index $IDX$out of range [$BEG$, $END$]
Please help me to resolve this issue.
Thanks & Regards,
Ramana.

Hi,
I too have the exact same issue and error.
The tables are created under the efashion schema using the SYSTEM user. The tables are created as "column" tables.
Regards,
Asif.

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

Best practices for PAL and HANA Modeling

Hi all
I wanted to get your opinion on working with Predictive Analysis Library and SAP HANA modeling- analytical views, calculated views, etc.
If I have transactional data modelled into analytical view and now wish to run a predictive function on some of it's columns, what are you guys' suggestions on how to best go about building a PAL model within HANA?
Do I run the PAL procedure every time the table is updated? How do I decide on the frequency of the pal procedure? Any tips?
And do I use triggers for automated procedure runs?
What are some of the best practices?
If this has been brought up before, please point me to the right discussion.
Thanks!

Hi all
I wanted to get your opinion on working with Predictive Analysis Library and SAP HANA modeling- analytical views, calculated views, etc.
If I have transactional data modelled into analytical view and now wish to run a predictive function on some of it's columns, what are you guys' suggestions on how to best go about building a PAL model within HANA?
Do I run the PAL procedure every time the table is updated? How do I decide on the frequency of the pal procedure? Any tips?
And do I use triggers for automated procedure runs?
What are some of the best practices?
If this has been brought up before, please point me to the right discussion.
Thanks!

SAP HANA Modules

Hi Experts,
I am into SAP ABAP from past 4 Years and want to learn SAP HANA.
I have just checked there are 4 modules in SAP HANA.
1.) SAP HANA data Modelling AND Implementation
2.) Programming
3.) BW on HANA
4.) Administration
I want to switch from programming , so which module will be easier to learn for me?
I had small training on modelling 1 year back.
And also my question is there any coding involved in SAP HANA modelling and Implementation?
Please guide me with your valuable comments.

Hi Sridhar,
I don't this is the right place to discuss these doubts. Please find below link to get detail info to get your query. I would request please close the thread afterwards:-) as it is showning in highlighted list. You please inroll below courses then defintily will find out your answer. have a good day.
https://open.sap.com/courses/s4h1http:// SAP HANA
https://open.sap.com/courses/hana3 SAP HANA development
Thanks,
Prem

Regarding career in SAP HANA

Hi,
I am in confused state from past 6 months.
I have been working in SAP ABAP from past 5 years and from last 6 months I have been learning SAP HANA modelling and implementation side by side. I have learned below topics in the same.
a.) SLT/LT replication.
b.) Information models.
c.) Procedures and SQL.
But now when I am going for any interview they are expecting below things also from me which I have no idea.
a.) SAP BW prior experience.
b.) Any reporting tool experience. like BO or lumira
c.) Any DB experince like ORACLE or SQL.
Can someone please guide which area should I go for?
I just havn't opted for ABAP on HANA because I cannot see much openings for the same.
Secondly if I start learning ABAP on HANA will my above knowledge I gained in last 6 months will go waste?
Please guide me with your valuable comments.
Thanks and Regards
Sumeet

The demise of ABAP has been predicted as imminent for at least fifteen years. Yet here we still are.
Not all SAP installations will exploit HANA modelling and development. If you want to go that way, learn to use ABAP, the HANA tools and python really well, and gain experience.
If you want to stay as an ABAPper I can't really see anything that will prevent that in the next ten years.

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 )

Deploying / Transporting SAP HANA-ECC and BW Solution?

Is there one centralized deployment guid for SAP HANA solutions in the SAP ECC and SAP BW environment?
Please can one of you provide some directions to a centralized guide to move / deploy SAP HANA solutions build in one system to Quality and/or production environment?

Rama,
there's a pretty straight forward export/import functionality for moveing models from dev to qa and prod. Please see the SAP HANA Modeling Guide, chapter "Processing Information Objects".
You can also use CTS+ in conjunction with this functionality.
Regards,
Marc
SAP Customer Solution Adoption (CSA)

How to open closed quick launch area in hana modeler?

how to open closed quick launch area in hana modeler?

Hello Abhinay,
Open SAP HANA studio, go to window -> open Perspective-> SAP HANA modeler. Quick launch view will be opened.
OR
Go to window -> show view -> others . Type quick launch in serach. or under SAP HANA folder you will get the quick launch view option.
Regards
Subhash

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)

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD?

What is the average duration of 1 full SAP life cycle or 1 end-to-end implementation. How long does it take to prepare DEV, QAS and PRD in any company?

Anand,
let me start with saying that the question you ask may not help you to determine the duration of your project. As Ryan and others stated the duration of the project is highly dependent on the scope of the solution you are implementing, geographical scope, amount of modifications/enhancements, number of languages, number of users that need to be trained, amount of standard processes customer is able to re-use in the implementation and many other factors (like quality of implementation contractor you will chose and availability of customer and implementors resources). I can probably go on for another couple lines, but I guess you get the idea.
With that out of the way let's talk about some example implementations that will give you an idea - Ryan did great job outlining what I would call traditional approach above. I have couple examples where customers leveraged innovative deployment strategies that are available today. In particular the project teams leveraged pre-packaged services like RDS, World Template or Best Practices as their baseline solution and they built from there. Second acceleration technique customers now leverage is the deployment in the SAP HANA Enterprise Cloud to accelerate the time to initial setup of the system and thus move from traditional blueprinting to scope validation exercise that further shortens the time. There are other acceleration techniques we see applied in some cases like use of iterative implementation of the delta requirements on top of the baseline solution.
Let me offer few examples to illustrate what I explained above:
ERP implementation at Schaidt Innovations with 3 months long deployment of ERP solution using ERP RDS as a baseline (you can view their testimonial here - Schaidt Innovations: SAP ERP on HANA in the cloud - YouTube)
Customer in Asia with global template deployment that leveraged SAP ERP for Manufacturing with deployment to cloud and 9 countries rollout (Japan, Korea, China, Taiwan, Hong Kong, UK, Germany and US). The initial deployment took 4 months for first country and 2 months for rollout into the additional 8 countries - so total of 6 months. The original plan using traditional approach with full blueprint and heavy configuration was estimated to be more than double of the actual deployment time.
There are many other examples where customers follow the assemble-to-order delivery model for their project and gain significant benefits doing so. I suggest you to review some of the recordings we did in 2013 about this approach and if you are member of ASUG review the Agile ASAP sessions we did for ASUG PM SIG.
Link to webinars: SAP A2O Webinar Series Schedule
Let me know if you have any questions.
Jan

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

What is step by step in real time project i.e. end-to-end life cycle?

what is step by step in real time project i.e. end-to-end life cycle?

Hi Vamsi,
The below explanation gives you an idea of what is going to come after what in a software development.
These below stages are know as Software Development Life Cycle/Waterfall Model.
1. System/Information Engineering and Modeling
As software is always of a large system (or business), work begins by establishing the requirements for all system elements and then allocating some subset of these requirements to software. This system view is essential when the software must interface with other elements such as hardware, people and other resources. System is the basic and very critical requirement for the existence of software in any entity. So if the system is not in place, the system should be engineered and put in place. In some cases, to extract the maximum output, the system should be re-engineered and spruced up. Once the ideal system is engineered or tuned, the development team studies the software requirement for the system.
2. Software Requirement Analysis
This process is also known as feasibility study. In this phase, the development team visits the customer and studies their system. They investigate the need for possible software automation in the given system. By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system. It also includes the personnel assignments, costs, project schedule, target dates etc.... The requirement gathering process is intensified and focussed specially on software. To understand the nature of the program(s) to be built, the system engineer or "Analyst" must understand the information domain for the software, as well as required function, behavior, performance and interfacing. The essential purpose of this phase is to find the need and to define the problem that needs to be solved .
3. System Analysis and Design
In this phase, the software development process, the software's overall structure and its nuances are defined. In terms of the client/server technology, the number of tiers needed for the package architecture, the database design, the data structure design etc... are all defined in this phase. A software development model is thus created. Analysis and Design are very crucial in the whole development cycle. Any glitch in the design phase could be very expensive to solve in the later stage of the software development. Much care is taken during this phase. The logical system of the product is developed in this phase.
4. Code Generation
The design must be translated into a machine-readable form. The code generation step performs this task. If the design is performed in a detailed manner, code generation can be accomplished without much complication. Programming tools like compilers, interpreters, debuggers etc... are used to generate the code. Different high level programming languages like C, C++, Pascal, Java are used for coding. With respect to the type of application, the right programming language is chosen.
5. Testing
Once the code is generated, the software program testing begins. Different testing methodologies are available to unravel the bugs that were committed during the previous phases. Different testing tools and methodologies are already available. Some companies build their own testing tools that are tailor made for their own development operations.
6. Maintenance
The software will definitely undergo change once it is delivered to the customer. There can be many reasons for this change to occur. Change could happen because of some unexpected input values into the system. In addition, the changes in the system could directly affect the software operations. The software should be developed to accommodate changes that could happen during the post implementation period.
Reward if helpful.
Thankyou,
Regards.

SAP HANA Modeling Sample end to end Project

Similar Messages

Maybe you are looking for