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

Similar Messages

Help needed- SAP HANA implementations and costing

AS a project Manager, I am interested in knowing the details on SAP HANA implementation.
If any company wants to use HANA then whats should be the cost of appliances, related software's and integration with netweaver?
How the costing will be decied if any company wants to migrate to HANA?
Pleae help

Thanks Krishna and Raj for the info.
I also found blow link very informative in terms of costing related to Hardware, infra, software etc, do read if u get time.
http://public.dhe.ibm.com/common/ssi/ecm/en/xsw03127usen/XSW03127USEN.PDF
If anyone has mre views then pls share

HANA implementation in BW

Hi
Currently we are at BW 7.4 with SP6.0.
Migrated all frontend objects like queries and web templates from version 3x to 7x.
Most of the backend objects like info cubes, ODS and data flow (Transfer rules & Update rules) are still running in 3.x version.
We are about to start HANA implementation in our BW environment.
Since backend objects are still running in 3x version, is this going to impact HANA implementation?
Before HANA implementation is it necessary to migrate all 3x backend objects 7x?
Please advise.
Sat

Hi Satish Tummala
It would be good practice if you can migrate 3.x flow to 7.x where you can actually get advantages of new features of technology/latest version.
Please do remember that, if you continue with 3.x flow and converted only targets(DSO & Cubes) to HANA optimized, your update rules can never enhanced in future,unless you migrate it to 7.x.
Hope this info helps you. thank you.
Regards,
Mallikarjuna

What are the main reasons for SAP-HR Implementation Failures?

Dear Consultants,
Can some one shed the light on the following items:
1. At least 3 main reasons for failure of SAP-HR Implementations?

Hi,
Check this link
http://searchsap.techtarget.com/news/article/0,289142,sid21_gci892265,00.html

SAP HR implementation ( MOST MOST URGENT )

Hi Friends ,
Just i wanted to know the following answers ?please kindly send me full - detail script .
1. Project planning
2. Documentation of Functional Specifications and communication to ABAP Programmers
2. Blueprints (requirement analysis and process design)
3. Realization (configuration, QA testing and production support hand-over)
4. Go-live (data conversion, production system build and final QA testing)
5. Production Support.
Thanks and i appreciate your time .
Regards- Zubair ( Australia )

Business Blueprint
Once a company decides to buy SAP, a consulting company is being hired for the implementation. The consulting company analyze the business process of the company and prepare a blueprint.
Sometimes the business process is reengineered (BPR) to accommodate SAP's functionalities.
The second step is installation of SAP and setting up three clients namely development client, test client and production clients.
In the development client the SAP functional and development group start configuring the SAP based on the blueprint. Once it is completely configured, it is being transported to test client for testing using real time data. Once testing is successful, the configuration is being transported to production client to be used by real-time users.
So this process makes SAP more reliable and robust in production.
Preparation Before Implementing SAP
SAP R/3 implementation is generally a key project for any organization. It is necessary to do preparation before implementation.
Many organizations speak of "transferring technology." But what does that mean? Transfer technology involves transfer of the system which includes the
hardware
software
people
processes
information
organization
structure
synchronization
function and
behavior.
It becomes obvious that the transfer of any part of the system, without the rest of it, does not transfer technology. In our context, the software SAP/3 is being changed. In most of the cases the hardware needs to be changed. The people need training to operate SAP system. But unfortunately, many organizations fail to understand that they need to change their processes. SAP is a package & it contains many best practices suitable to almost each industry. The designer (configuring the system) must design the system keeping the objective of the business objective in mind. The user should be prepared to change its processes and ensure that the objective of the processes is met. This should be done without or minimum distortion of the processes designed by SAP. This is a big challenge to the designer as well as user. It should noted that the user representative involved in the system design should be empowered for low level BPR decisions.
Also the information stored in the system will be in different form than the legacy system. The user must be prepared & trained for the changed.
The major challenge is behavioral change. Implementation of SAP R/3 system changes relationship of different persons, it gives/denies access to information which was not available/available to the person, it changes processes and control functions. This all gives behavioral issues. To get best out of SAP, these issues must be addressed before implementation.
SAP R/3 re-engineers many processes and the fear of downsizing and loosing job hinders free acceptance of SAP in many organizations. This fear hinders free communication between the end-users and SAP system designer. The communication is a vital element in successful implementation of SAP R/3. This issue of 'Fear Of Downsizing' must be addressed before starting implementation project.
ASAP Implementation Methodology
Any enterprise application software has to cover a broad spectrum of functionality, yet to be configured enough to meet specific requirements. SAP achieves this by ASAP methodology & R/3 Business Engineer.
AcceleratedSAP (ASAP) is SAPs standard implementation methodology. It contains the Roadmap, a step-by step guide that incorporates experience from many years of implementing SAP. Quality checks are incorporated at end of each phase to ensure quality of deliverables and monitor critical success factors.
ASAP is delivered as a PC based package, so that an implementation project can begin prior to having an SAP R/3 system installed
ASAP Tools
ASAP Roadmap
ASAP and Business Engineer have compatibility with many third party modeling tools and packages like MS Excel etc
Creating the Business Blueprint for Implementation Projects
Purpose
To create a Business Blueprint during the implementation of mySAP.com solution to document the business processes in an enterprise, and to decide which processes should realize in SAP system.
The use of Business Blueprint in the Solution Manager during the realization phase (configuration and testing) should continue. It needs to reuse the project structure created in the Business Blueprint phase, to configure and generate test plans. One can also display, change and enhance project documentation created during the Business Blueprint phase, during configuration.
Prerequisites
You want to implement a mySAP.com solution. You have completed the Project Preparation: you have defined an implementation project and a system landscape in the project administration of the SAP Solution Manager.
Process Flow
...Create a Blueprint structure, using predefined substructures.
Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
Create the project documentation and save it in the Business Blueprint.
Assign transactions to process steps. This specifies which transactions in the system correspond to the process steps in your enterprise.
Print the Business Blueprint document.
When the Business Blueprint is complete, you can start to set up the development system landscape.
Result
You have created your Business Blueprint and set up your development system landscape. You can reuse the Business Blueprint and the project structure to configure and test your business processes
Business Blueprint
Use
This function documents the business processes in your company that you want to implement in the system. In a Business Blueprint for Projects, you create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. You can also create project documentation and assign it to individual scenarios, processes or process steps. You then assign transactions to each process step, to specify how your business processes should run in your SAP Systems.
The Business Blueprint is a detailed description of your business processes and system requirements. You can print it out.
Integration
You can continue to use the project documentation and the project structure that you create during the Business Blueprint, in the configuration and test organization phases.
When you configure your business processes, the system displays the Business Blueprint project structure. You can use the Business Blueprint project structure as a point of reference during configuration.
You can also display and edit the project documentation from the Business Blueprint phase, during configuration.
You base all test plans that you create during test organization, on the Business Blueprint project structure. The transactions that you assign to process steps in the Business Blueprint are put in test plans during test plan generation, and run as function tests to test the transactions.
Prerequisites
You have created a project of type implementation, template, or upgrade, in the project administration.
Features
Scope of the transaction Business Bueprint
Function Tab
Create a project structure Structure
Display the following documentation:
Documentation delivered by SAP, e.g. scenario descriptions
Documentats from templates, e.g. from template projects
To be able to edit general documentation, copy it to the Project Documentation tab. General Documentation
Assign documents to structure elements
Create, Change, Upload user documents Project Documentation
Input administration data, e.g. project status, team members assigned, planned and actual resources Administration
Assign transactions and programs to structure elements Transactions
Create, Display and Edit messages Messages
Display and Create a process graphic
Create a process graphic Graphic
Where-used list:
Use in user project
Use in other projects
Go to use by double-click General Documentation
Project Documentation
Transactions
General Functions
Function Navigation
Change the sequence, hide or show tabs Settings ® User-Specific
Translate project structure
For further information about translating document names for URLs, in your project, see Translating a Template
Goto  Translation
Create/print a Business Blueprint document Business Blueprint  Create Blueprint Document
Assign Document Authorizations
Assign authorizations in the Role (PFCG) and User Maintenance.
Activities
1. Create a Blueprint structure in the Structure tab, using predefined substructures.
2. Check the Business Blueprint structure, and the business scenarios, business processes and process steps it contains.
3. Decide which business scenarios, business processes and process steps you want to include in the Business Blueprint. You can enhance the processes and process steps, or adjust the names of individual processes to suit your company requirements.
4. Create project documentation to save in the Business Blueprint, in the Project Documentation tab.
5. Assign transactions to process steps in the Transactions tab. This specifies which transactions in the system correspond to the process steps in your enterprise.
6. Print the Business Blueprint document.
7. When the Business Blueprint is complete, you can start to set up the development system landscape.
Result
You have specified a Business Blueprint. You can reuse the Business Blueprint and the project structure to configure and test your business processes.
Business Blueprint
Definition
A Business Blueprint documents the business process requirements of a company. In collaborative business processes, several companies are involved.
Use
The Business Blueprint gives you a general idea of how your business processes could be mapped in one or more SAP Systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of a mySAP.com solution implementation.
Structure
A Business Blueprint compises the following structure elements in a hierarchy:
Organizational units
Master data
Business scenarios
Business processes
Process steps
You assign content, for example, project documentation, Business Configuration Sets, or transactions to individual structure elements, in the SAP Solution Manager.
You can also create structure elements for organizational units and master data, below a business scenario. You only use these structure elements if the organizational units and master data are only relevant to the business process above them in the structure.
09885707073

How beneficial it is to have EP system database on HANA?

Dear HANA Experts,
I would like to know the benefits of implementing EP 7.4 on HANA.
As far as I know, there will be less Database accesses during Java Enterprise Portal system operations.
How beneficial it is to have EP 7.4 database on HANA?
Please provide pointers to know more information regarding this topic.
During POC, one benefit which we have observed is that Portal system came up in less than 2 minutes on HANA DB where as it is taking around 7 minutes in MSSQL DB !!
Thanks,
John Prabhakar

I currently have 11 1G system files which I'd like to combine into say 3 4GB system data files, or 2 6GB system data files.WHY is any change needed?
What is gained by doing so?
Do you suffer from CTD?
Never confuse movement with progress.
Going around in circles is movement, but most folks do not consider it to be progress,

Forms in SAP MM implementation

Hello Gurus,
Can someone throw some light on the various forms which need to be printed or faxed for internal use or for vendor use, in a typical SAP MM Implementation.
Thanks,
Sachin

HI,
These are the forms which are needed in MM implementations.
Again it entirely depents on the clients requirement.
1. RFQ
2. PO (All kinds of PO's like services, subcontracting, assets Consumables etc)
3. GR
4. GI
5. Service Entry Sheets
6. Shedulling Agreements
7. Shedule Lines mainted for Sheduling Agreements
8. Contracts
Thanks & Regards,
Kiran

What are SAP products?

Dear all
i am new in SAP and research about SAP products in university .
so i want to know what are sap products exactly.
i heard many names as products of SAP AG but i don't know
the diffrences.for instance i read ABAP ,SAP GUI,NETWEAVER
SAP business one,my SAP business suite,what are the use of this products.what should someone do to establish a complete system of sap.deos it need to have database?
to explain more i know that ORACLE CORPORATION have 4 major products:
1. DATABASE Server
2. APPLICATION Server
3. Developer Suite
4. Application e-business suite 11i
so plz write for me what are SAP AG products and thier use

There are a lot of SAP products, I wouldn't name them all, but I will give the basics.
1) Web Application Server, ABAP and/or JAVA. This is the basis for SAP applications.
2) SAP R/3 or SAP ERP. These are the applications in which most companies have installed. These applications run the day to day business functions. They run on the ABAP side of the WAS. The frontend end that the user uses to interact with the system is the SAPgui.
3) There are many other systems which compliment your R/3 implementation such as CRM, SRM, APO, etc.
4) Enterprise Portal, is an application which runs on the Java side of the WAS, this is a web based frontend which integrates SAP applications and non-SAP applications into one central place where the user can access all kinds of data.
There are many other products in SAP, these are just the major ones.
SAP supports many databases, such as Oracle, SQL, DB2.
Regards,
Rich Heilman

Global SAP HR Implementation

Hello Forum,
I am in a situation of planning implementation strategy for Global SAP HR implementation across 30 counties.
Process to be implemented
1. Performanace management
2. Hiring and firing
3. Payroll
4. Manage Employee Info.
5. Recruting
6. ESS
7. MSS
etc.
I am wondering if some one can reply following queries with above inputs
1. The cutover approach and principles
2. The data conversion sequence
3. List the interim processes required
4. Expected resources to support implementation
Thanks in advance.
Sanjay

Hi,
I hv worked with World's largest SAP HCM implementaion.
Certain points from my side..
1.The cutover approach and principles
Best is to start with a country where less number of population.(For first go live)
Maintain separate testing team for SIT also.
Adhere to global implementation strategies and unique terminologies in all countries (Config part)
2. The data conversion sequence
Maintain a separate team for data conversion and data cleansing should be the job of client. You can use different methods for uploading data for different countries (Eg: only for US Specific we have DTT tool etc.)
3. List the interim processes required
4. Expected resources to support implementation
Respect on the implementation approach.
Up to how many countries and you are planning to go live on the same date (Parallel implementation)?
Or you are planning as a sequence of rollouts etc.
Regards
Thomas.
Edited by: Thomas Padiyara on Jul 29, 2008 4:50 AM
Edited by: Thomas Padiyara on Jul 30, 2008 8:48 AM

SAP HR Implementation complexity

Hi,
Could some tell me what are difficulties or complexities involved in SAP HR implementation and at what stage we may face the major issue.
And also on what basis we personal area , subreas, employee groups and subroups are formed in blue print.
I mean how we finalize the enterprise and personal structure in blue print.
And also once implemented what will be handover activities.
Many Thanks
Chinni

Hi,
As you know that we have ASAP Methodology...
Each and every phase we find difficulties. Below are few examples
Phase I : Mostly consultants are not going to participate here.
Phase II : 1/ In AS-IS --> you find many problems like, we need to understand the client Business and his ongoing process. It differ from each and every client
2/ Blue Print --> Here we need to map the client requirement to SAP (Its really a big task). Here we need to have workshops with end users.
Phase III : Configuration --> Some times we may think that is not a big issue.. but we will not be getting the results.. we need to break our heads.
Phase IV : We need to test and need to prepare the Test Scenarios and Test Cases.. again its an other big task
Phase V : Support and maintenance is an other part.
Once the AS-IS is completed, then we have to decide on what criterias and functionalities we have to define our Per Areas, PSA, EE Grouping and EE sub grouping. Before AS-IS we cant define those.
Hope you got your questions clarified.
Good Luck...!
KK

Non-SAP JPA implementation

Hello, experts!
I have an WD application that uses EJB model. All works fine, but I want to change SAP JPA implementation to Hibernate JPA implementation.
This is my persistence.xml
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
     <persistence-unit name="test" transaction-type="JTA">
     <provider>org.hibernate.ejb.HibernatePersistence</provider>
     <jta-data-source>msDS</jta-data-source>
     <properties>
          <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/>
     </properties>
     </persistence-unit>
</persistence>
I have got this exception after substituting JPA implementations : org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager
I have read on different forums that this exception means that container cant get a transaction. But I want to use "transaction-type="JTA", not "manual" transactions.
Thanks for any reply.

Are you sure that your DB (dialect) is SQL Server?
If yes, then try adding the following property to your persistence.xml
<property name="hibernate.transaction.manager_lookup_class"
value="test.persistence.SAPCETransactionManagerLookup"/>
where SAPCETransactionManagerLookup is
package test.persistence;
import org.hibernate.transaction.JNDITransactionManagerLookup;
public class SAPCETransactionManagerLookup extends
                JNDITransactionManagerLookup {
        @Override
        protected String getName() {
                return "TransactionManager";
        public String getUserTransactionName() {
                return "UserTransaction";
You may also try adding another property along with the above one, if the aforementioned property doesn't work.
<property name="hibernate.transaction.factory_class"
value="org.hibernate.transaction.JTATransactionFactory"/>

Roles and responsebilities of sap sd implementation consultant?

what are the roles and responsebilities of sap sd implementation consultant?

Hi,
Refer to this website for roles and responsebilities of sap sd implementation consultant.
http://www.sap-img.com/general/role-of-a-sap-functional-consultant.htm
Simple - he is responsbile for implementation of SAP SD Module.
Regarding Implemenation
http://en.wikipedia.org/wiki/SAP_Implementation
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

SAP CRM Implementation Project - Phases/Stages

Hi all
I am very new to this Area !
I would like to know different Phases/Stages in the SAP CRM Implementation Project !
Regards
RJ

Remo,
I believe every SAP CRM Implementation project would follow the ASAP methodology which is as follows:
Phase1: Project Preparation
The system landscape is set up, consultants are assigned. Project charter is created etc.
Phase2: Business Blueprint
The implementation consultants do a study of the clients business and learn how the processes/ cycles involved thru discussions, workshops etc
This is documented as an AS-IS document.
The clients business processes are then mapped on to SAP by the consultants.
This is documented as the TO-BE document
Gap Analysis is performed to identify any gaps between the AS-IS and TO-BE documents. i.e. something that the client wants but cannot be met thru SAP CRM. Then enhancements etc come into picture.
Phase3: Realization
The system is configured as per the TO-BE document. And the client is given for testing.
Phase4: Preparation for Go-LIve
Once the client confirms all the unit and integration tests, the master data needs to be uploaded. Other system checks by basis and SAP itself are performed.
Phase5: Go live and support
The project goes live and the consultants give a month's of hypercare or support.
Hope this is wat you were expecting.
Regards,
Julius
P.S: Reward if it helps.

How effectively do you use SolMan in SAP ERP Implementation, Upgrade?

Effectively utilizing Solution Manager (SolMan) during SAP ERP Implementation or upgrade are very far and few!
I have shared my thoughts and experience of using (or not using) SolMan in this piece.
I will be glad to know your experience and insight on SolMan's utilization, either in comments here or on the article's website.
Until next time,
Jawad Akhtar

Anyone..? <crickets>

How to carry forward any open documents in a new SAP B1 Implementation

Hi,
I want to know what are the best practices to record any open documents during a fresh SAP B1 implementation.
The client has an existing running business and may be implementing SAP B1 at the start of the financial year or during the middle of the financial year.
How do I enter the open documents as on the go-live date; documents like open Purchase Orders, open Sales Orders, open GRPO, open Deliveries, etc.
What are the multiple approaches / alternatives to evaluate and what are the best practices?
Note: I am not talking merely about the GL or Inventory Opening Balances, but the entire set of open documents!
Thanks.

1. When it comes to documents that post to the G/L you want those posted the day you go live as this is part of your opening balance. This would be for you A/R and A/P Invoices. Just make sure the Due Dates are correct and the G/L account is your Opening Balance account. Why? So you can run a trial balance for that day. So in your case I would either do 1-SEP-2014 or 31-Aug-2014. Again I prefer to enter them in as the day before go live so that I can easily run a Trial Balance on my opening transactions. I have yet to have the opening balance balance out on these imports.
2. I would go with the open items on the PO. Why? Less work and still accomplishes the need for open items. In all cases add the original document # from the legacy system in the remarks so you can always find the original.
3. Once again, I would go with only the open balance. Why? It is less work and you can always record any audit remarks in the remarks section of the document. Remember the goal is to import your opening balance. You do not want to step into historical data, it is not easy and takes a long time. So unless the customer is paying for it, this can become a money loser. If analysis is need on historical data, then they have their legacy system to look at.
4. The whole reason for the Service Type invoices is purely for the opening balance of the Accounts Receivable and Accounts Payable opening balances. The document total should be the total for the amount that is owed as this is your opening balance for the A/R and A/P accounts along with the customers and vendors sub ledger.
5. Yes. It can be done through the DTW. I haven't tried the new features on the Inventory Counting, but I believe they have added an import feature. Either way should work as long as you get the inventory in the correct places and the inventory accounts to the correct value.
Remember, opening balances are meant to be the values of the legacy system as a snapshot in time. This means that inventory is correct and in the correct place and most importantly the accounts are correct. The reason for the Opening Balance account is as an offset account to the journal entries you create for importing these opening documents. In the end, the Opening Balance account should be 0 if the legacy system is balance.

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

Similar Messages

Maybe you are looking for