In my current project we have a lots of source systems which delivers our data in a key figure model. In a normal case is this not a problem. But we need the values of the key figures in a hierarchy. So there are two ways to realize it. First way would be we build a structure with restricted key figures and get our hierarchy. Here is the problem, the customer will need different queries to realize his needs. If there is a change, we need to adjust different queries (each has a light different hierarchy) and the maintainace is immense.
As you might know, Analysis Office 2.6 is available now. To download it, you need a S-User with download credentials. First SAP BusinessObjects Analysis for Microsoft Office is now called, SAP Analysis for Microsoft Office. Damn I have to rewrite my book, just kidding. Here is a short overview of What's new in Analysis Office 2.6:
So I just downloaded Analysis Office 2.6 and maybe I can write a little bit more in the next days.
In the last month I was very busy with my thesis and my project at work, so I had no time to write a lot of blog posts. So here is a short overview what Analysis Office 2.5 SP2 fix. But keep in mind, Analysis Office 2.6 is up coming.
In my current project I created with a collegue a really cool function to analyze a string with 1333 characters. We are using a BW 7.4 SP 17 on HANA. First we have to build an Advanced DataStoreObject with a Field which has a length of 1333. For further understanding, we call the field Field_1333. As data type I used SSTRING.
A really cool feature of Analysis Office 2.5 can you see in the "backend" under File >> Analysis. The function Customize Analysis offers now new options. Besides the Customize User Interface from Analysis Office 2.4 which allows you to change the ribbon menu of Analysis Office, you now can directly modify the technical settings of Analysis Office.
This week is very short in case of the day of German unity and we have sprint change next week, I haven't time to write a lot so here is just one goodie. When you insert a DataSource in Analysis Office 2.5 you see the recent inserted DataSource. Now in Analysis Office 2.5 you also see the technical name of the query and the system. I think this is nice if you are testing a query on different systems.
In my current project I work a lot in the backend of a BW 7.4 on HANA but I finally found time to look into Analysis Office 2.5. Here is a short explanation about the feature that the scaling factor works now with conditional formatting. If you configure your conditional formatting like the following screenshot and apply after that your favourite scaling factor. It automatically adjusts.
Analysis Office 2.5 is finally available since the end of August for everyone. After I submit my diploma thesis last week, I have now time to see whats new in Analysis Office 2.5. Here is the first short overview of the new feature:
At the moment it is very quiet about new blog post. This is maybe the summer break everybody talks about. ;)
I am at the final phase of my diploma thesis and have no time to do cool stuff and also SAP doesn't release Analysis Office 2.5. It is still in ramp up and nothing new at the moment.
So I could only say, my current project is a BW on HANA and I am testing how HANA SQL Script (AMDP) works and how fast we could build some stuff. First tests show a transformation with routines for 800.000 records about 1:55 minutes. The same transformation with AMDP (ABAP Managed Database Procedures) only need between 15 - 23 seconds. This is really impressive.
So stay tuned, if SAP will release Analysis Office 2.5 and some examples with AMDP.
Mobile Application is the big thing in management. If you want to create a mobile application in SAP Design Studio, SAP have some recommendations:
I hope everybody stick to this recommendations or we will see people looking like that:
I know that I don't publish a lot of new posts the last few weeks. The reason is I am writing on my diploma thesis. The title is "S/4HANA versus BW/4HANA - Zukunft der Datenanalyse". My deadline is in the middle of September so I have to write a lot these days. At the moment, I have access to a BW/4HANA instance in the cloud and I want to share how you could export your development before you terminate the instance. First you have to log on with the SAP* user in the client 000. Go to the transaction stms and select the System Overview.
Last week the Analysis Office 2.4 SP3 was released. Here is a short overview of notes, which may solves some problems.
If you use a BW/4HANA instance, you have to use the BW Modeling Tools (BWMT) to build your data model. You could only build Advanced DataStore-Objects (ADSO). If you create a new ADSO, you have to select a BW-Project and an InfoArea. After that you have to define a technical name and a description. You could also use a template to build your ADSO.
I described in a earlier post how to use BW/4HANA on Amazon AWS. But if you just need a developing system for some time and don't want to use BW/4HANA, you can use the BW 7.5 SP2 developer edition on a virtual machine.
After I had time in my parental leave to read proof the second edition of my book, I can say it is now finished. The second edition is now available in the store. You can download the table of content here. This version is only available here and at the moment not on Amazon.
If you have any questions feel free to ask and send me either an email or a comment. I hope to publish regularly in the next weeks so stay tuned.
In this blogpost I want to know if there is an interesting about an Analysis Office Video Course. Thanks for your time and your answers. Open the survey.
I want to document a BW data model and searched for a Microsoft Visio shape, but I found nothing. So I build my own Visio shapes. At the moment there are the following types available:
I used them in my last blogpost about Copy Queries to a new MultiProvider.
In my current project, we want to separate the current MultiProvider with VirtualProvider underneath into one MultiProvider with VirtualProvider and one MultiProvider without VirtualProvider. This step is necessary, because we receive a lot of data and don't want to push all these data through the VirtualProvider. The VirtualProvider only add one field which we haven't got in our InfoCubes and it isn't necessary in all queries just a few.
At the moment I had to deal with a special problem. I have data in a SPO from two different sources and the goal was to find the corresponding two data lines and make one out of it. This line should marked with a special character. So I decided to build an Analysis Process (APD).
Sometimes it is necessary to check your data model if it still fit your needs. For this you can use the transaction rsrv. Select there under All Elementary Tests >> Database >> Database information about InfoProvider tables.
On 10.03.2017 a new service pack for Analysis Office was released. The main reason why you should update from SP0 or SP1 is that they fixed a lot of bugs in it (and maybe they build some new). Here is a short overview of the fixed problems:
In my current project I had to clean up the existing process chains. A lot of process chains were created via SPOs and not really used in the system. First I had to check, if one is used in a another process chain or in which one they are used.
In my current project we have to transport from a maintenance system to our development system. The problem is when you now transport the objects into quality system, you have to check the option "Overwrite Originals" so that your transport is working. But you have to put this flag on every transport you make in the future from your development system to quality.
There are also some changes in the User Interface Customization.
In my current project, we have a copy of the productive system as a maintenance system, because we made huge changes in
the development system in case of the project. So if there is an error in the production, we can easily repair it.
Some changes have also be transported into the development system, so we have the same state and our future request can be transported into production. For this we use the functionality Transport of Copies. All objects of the originally request are still locked. If you want to create a transport of copies, open the transaction SE01. Check the option “Transport of Copies” and click on Display.
After we created in Part 1 the transparent tables and in Part 2 all BAdI implementation, we can now maintain and create our SPO. First we have to fill our table ZSPOPATTERN with a PATTERNID and a corresponding INFOOBJECT. Go to the se16 and create a new table entry. As PATTERNID enter a unique id for example CALYEAR and as INFOOBJECT 0CALYEAR. For TXTLG and TXTSM enter a useful text. Depending on how many InfoObject are used for a partition, create the other pattern.
After we created in part 1 all tables and objects, we can now create a new BAdI to generate the partitions. Go to the transaction se19 and create a new implementation with the Name RSLPO_BADI_PARTITIONING.
At my current project I needed a way to create Semantic Partitioning Object (SPO) via BAdI to reduce the end-of-year work. After a little search via Google (you cannot find anything on the new SAP Community Page), I found these threads.
Life experiences of a SAP Business Warehouse Consultant