SAP BI on HANA Testing

owing to its complex landscape, we have just too many components that are integrating.


As shown above, we will below components typically in a landscape.

1. SAP HANA Box
2. SAP SLT
3. SAP BODS
4. SAP BI
5. SAP ECC/CRM/SRM
6. Legacy System
7. SAP BOBJ Suite

SAP HANA Box, it self has many components (to be continued...)

Comments

Post a Comment

Popular posts from this blog

SAP V1 V2 V3 JOBS

Image
Before starting with V-series jobs, lets review some fundamentals. Data base LUW:  It consists of sequence of DB operations(INSERT,UPDATE,DELETE) that needs to be committed to either all or none to keep DB in consistent state. COMMIT will be executed when all DB operations were successfully executed, once COMMITTED these changes can't be ROLLED BACK. This is part of traditional ACID property of any RDBMS. If a failure happens while executing the LUW(will be mostly technical like memory crunch,integrity violation or data base crashed,power failure) and when DB is restarted, DB will be ROLLed BACK to previous state. Which is nothing but the state when last COMMIT was happened. In other words, when ROLL BACK happens DB will be safely brought to previous COMMIT state. DB maintains log of actions performed since last COMMIT and as part of recovery process, all these actions will be reversed. All RDBMS will have in-built locking/multi concurrency control such that dirty READ-WRITE ope...
Read more

Does SAP HANA Complements or Competes with HADOOP stack??

Image
While HANA is SAP's answer for Big Data,then it is interesting to see how does HANA fits into fits into Big data paradigm. In particular, we will talk about HADOOP stack of technologies in view of Big Data. Welcome to world of unstructured data and HADOOP is ideal for processing large data sets & batch processing where response time is not a concern. Here Schema is not a concern as we are dealing with unstructured data and its not  optimized for data updates/inserts. It works with principle of write once, read always. Also random reads are not supported and data can only be appended. Having said above things, HANA follows for rows/columns storage model and we have to define schema before storing data. HANA is In-memory appliance thus supports faster read times/ on-the-fly aggregates/joins. After highlighting merits of both worlds, we can see that both comes from different worlds; HANA from world of structured with fixed schema optimized for real time access , HADOOP from...
Read more

Consuming HANA Models in BW, New breed of info Providers

BW on HANA We have 4 ways to make use of HANA data in BW. 1.        Virtual providers Virtual providers which are actually meant for real-time reposting based on data from OLTP systems directly (the whole data loading into Datasource, DTP execution and loading into infosource happens just right when query is executed in real time) can be used for consuming analytic/calculation views in BW. When we create virtual providers we have new option “Based on HANA”, which will ask you to input schema name and model name. Once model is selected then we start with modelling process in workbench. We have to select characteristics, key figures for our virtual info provider. Then we can map these to fields from HANA model (F4 help is provided). Here by providing BW Infoobjects will can make use of BW master data while reporting.  That’s all and virtual provider is ready for consumption using reporting tools. 2.        Transi...
Read more