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

Virtualization with SAP HANA

Image
Virtualization Most of Corporate Enterprise warehouse Eco system consists multiple disparate  Data warehouses. reason can be attributed to mergers and acquisitions,  departments using specialized software, databases choose to support specific data needs. All these scenarios result in building multiple data marts over multiple technologies. However, to serve the purpose of single source of truth, we end up building Enterprise Data Warehouse(EDW)  by sourcing data from various data marts across organization. One way of doing is, running a project for establishing standard ETL methods to extract data from regional Data Marts and staging data into EDW. However various departmental/ regional DW already contains highly formatted, information rich and aggregated data built readily available. This implies that we might not need to 1. Perform extensive transformations 2. Source data is meta data rich 3. Less data volumes will be retrieved from source systems Following trad...
Read more

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

Ramblings over Rank Node, ABAP vs HANA SQL Data types and Activation error for DSO with only Key Fields

Rank Node : We have new node type introduced in calculation views, Rank Node. This serves the same purpose of Exceptions from Bex. Instead of swamping  user with lot of data, we could restrict to display only TOP N values. The value of N could be fixed or based on a input parameter. In addition to Calculated, Restricted Attributes/ Measures , Rank node will further enhance OLAP toolkit of HANA Appliance. Temporal Join : ABAP vs HANA Native Data Types :   Every table in SAP will have two definitions. ABAP run time object and Database Object. From SE11, we can navigate to both and you can spot differences between them. reason being, ABAP Language  comes with some native data types. Examples being DATS, TIMS, CUKY, UNIT, CURR etc. These data types will mapped onto underlying Database native data types. Hence we have two representations of same object. Database interface helps us in converting Open SQL queries into underlying Database SQL. Lets shift our focus to Impo...
Read more