Angad Singh's Blog

Simplicity is the ultimate sophistication. — Leonardo Da Vinci Many people would think simple solution mean lack of functionality. In contrast, it really means there is consideration of various requirements of users and solution provides a fast learning curve. It's sophisticated solution minus complexity. Have you ever asked yourself that why do you prefer simplicity over complexity? When we were so little, we wanted everything to be simple and straight-forward. Most of us, when thinking of an issue or requirement or need, we try to map that thinking to a part or step in the solution. There is direct link. This is what every customer or consumer look in the products these days. They are looking for bond between their thinking and solution they are looking at. If a product or solution cannot create that kind of bond quickly then it faces a "lack of interest" or sometimes "rejection". A solution should be able to represent a story that user narrated but we w

You are working on a project and performing your daily tasks. A recent requirement make you ask this question "can we do this in HANA?". Sometimes, we discover things that we did not know at all. The discovered feature was always there but we just ignored it. In some cases, the feature got distributed in new release and we never tried it. Usually, these situations let us find something that can be helpful for deliverables. This way we learn and enhance our skills and hence, optimizes our development process. Personally, I am big fan of things that is simple and just made with purpose. While working with SAP HANA Data modelling perspective I have learnt things that can enhance the data models, provide fast development life cycle and make content management easier. Project requirement: Information need should be fulfilled with legacy data model or enhanced legacy data model. Following are the features that can be used to fulfill above requirements (based on real world expe

Being a Business Intelligence developer I work with data every day. I always strive for use case where we can do more with data and provide valuable insights to Business.  However, most of the time I am preparing operational reports which involves data modelling and designing report using specific tools and specific need (derived by Business). Though, it is good exercise to gain data analysis skills. Some of these reports are fun to build and challenging some time but still very specific. Few months ago I decided to explore the world of data science. The motive was to play with variety of data and explore use cases. I have principals when it comes to learning. One of my principal is "start from basics". There is no shortcut if you want to master something. You definitely need to know end to end if you really want to succeed and of course you have to be passionate about it. Therefore, I wanted to learn language build for data science but widely used. I started to read blogs a

In recent experience, I found that when we are using BW data sources then it display an error if OLAP connection language is set different from BW system. For example - I tried to change connection for this SAP Design Studio application and received following error: When I checked the backend connection in Preferences of SAP Design Studio then I found it is using language IE I checked Design Studio administrator guide and there were some hints to language dependency I found that the user language settings in BW was different from what I configured in OLAP connection BW OLAP Connection So I changed the language in OLAP connection in Information Design Tool to match BW system. Later, the error was gone and I was able to change data source. Once it is changed the it should appear as follows:

In this blog or document, I have shared my experience gained while creating forecast procedure using following features of SAP HANA: APL (Automated Predictive Library) Forecast Function Application Function Modeler (AFM) I haven't seen any convincing blog which promotes this feature of SAP HANA. Personally, I believe it is really good feature for people with beginner or no SQL scripting skills as AFM is graphical tool. However, the end result is a procedure which can be used later for different purpose. I created this forecast procedure based on the use case provided by  Forefront Analytics . The use case instructed to use APL forecast function. The input dataset was provided by Forefront Analytics . I started my research on APL and my main focus was time series function i.e. " Forecast ". I learnt about APL installation and different APL functions as I progressed. I discovered about AFM when I was watching SAP Technology videos as part of my APL research.  I have