techbytes

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

Most of customer's Use-case for HANA appliance is BW on HANA Database(HDB). This is the entry point of HANA into most of the customers Landscape. Here I will quickly try to cover what's new with BW 7.3 and 7.4 on HANA. Migrating BW onto HANA can be primarily seen from two perspectives. 1. Copying data from legacy DB to HANA 2. SAP BW application server migration onto HDB Here I am referring to migration with minimum system downtime. We will initally copy data into HANA and when everything is ready, will take down BI system down. Then migrate application servers too onto HANA. This ensures minimum service disruption time. Database Migration : Mass copying of data from Legacy into HDB, in general will be handled by in house BASIS team or your HANA hardware vendor can help in DB migration. In the Software Update Manager( SUM ),  we have Database Migration Option( DMO ). This makes our job easier to copy data foot print. However also note that, due to HANA Column stora...

This week started off with high by clearing HANA Certification exam(C_HANAIMP131). Although the exam is fairly easy, being certified by SAP feels good. I found below article very engaging, exploring BW' starting from initial jinx (which I never heard off) till BW on HANA. BW is Dead – Long Live BW Currently I'm working to create some models using SAP PAL.Hopefully by next week I can publish some. Also,  SAP is giving away free trail for 30 days to explore PAL. 

SAP BIBO 4.0 portfolio boasts of multiple reporting solutions. At times it might be confusing which tool to pick. Although one tool for all scenario doesn't exist, a refined set of reporting requirements should make it clear which tool to use for which scenario. Each tool has its own stronghold and weak areas. Crystal Reports : If we want pixel perfect reports, we will go for Crystal Reports. Mostly if requirement is to design report according to legal requirements or companies follow rigid format of reporting. Also Crystal reports is ideal, if we want to place lot of data in the report like year end results for stock holders. Also we can make the content dynamic by using variables. They can be broadcast/shared with business users.                              However the report format has to be pre-built and regular business users might find it difficult to deal with tool. We require power users to built t...

We will have a look at how BIBO suite reporting tools can interact with Data Modeled in HANA. Although most of the semantic layer options(Column aliases,filters etc) are also available in HANA modeler semantics node, building Universe on HANA gives existing users ease of use. As we have large existing user base who are good at designing Universe and also some options make sense to create in universe rather than in HANA modeler. *Universe still uses JDBC/ODBC  Connection to  interact with SAP HANA. It does add any      overhead/performance issue while interacting with HANA. It merely used as a passage. *Although explorer can be connected via Universe, it is recommended to connect HANA directly. As   Explorer is optimized for HANA(no need to build/refresh indexes and HANA provides real-time  data). *As Excel uses MDX query language, we can use it to display Hierarchies(parent-child/level) from HANA.

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

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