blog.

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:

• You are now able to connect to SAP BusinessObjects Cloud
• Customize User Interface has new options
• New different troubleshooting modes
• New options with Table Design
• A new API method SAPCallMemberSelector
• Changes on the grouping Crosstab function
• New file system setting ShowUtcTimeStampsInDataCells

This is a first view on the What's new Guide. I am also published Analysis Office - The Comprehensive Guide (2nd edition) as a Kindle ebook on amazon. Feel free to choose where to buy it. So stay tuned.

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:

• Keep the application simple and don't use too many components
• Don't use crosstab components for smartphone applications
• Limit the total number of cells in your crosstab to 500 for tablet applications

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.

• 2460877 - Excel crashes when opening several workbooks with SAPListOfMessages
• 2461196 - Advanced calculation editor throws error when inserting a member
• 2468933 - Effective filter shows only # for compounded characteristic
• 2463167 - Non-SAP (built-in) formula cells of workbook are not refreshed
• 2467459 - Prompts dialog clears variable

I am still waiting for Analysis Office 2.5, which is still in ramp up. Here is a first look from Tammy.

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.

There are a good post on the SCN. First you have to download Oracle VirtualBox. After that you have to download openSUSE. If you are a Linux Newbie you can read the following post how to install openSUSE on VirtualBox. The BW 7.5 SP2 developer edition can be found here.

After you have downloaded everything and your openSUSE is running you should read this post to get the installation of the BW done. I needed a BW 7.5 for the new edition of my book, so it was a nice variety for me. 

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.

In my current project, we have to deal with 30.000.000 records for the initialization run and about 10.000.000 records each day. The big problem is we have no SAP HANA system for BW. So, we have to build a perfect data model to load the data and push it through the BW to deliver it to another DWH system. First I want to describe how our first steps worked and then which parameter we changed to make it more efficient. I will also describe where we had our problems and how we have solved them. So let's go.

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:

• DataSource
• Transformation
• DataStoreObject
• InfoCube
• SPO
• MultiProvider
• DTP
• InfoSource
• OpenHub
• Query

I used them in my last blogpost about Copy Queries to a new MultiProvider.

The elements have also shape-data which can be filled. For example DataSource has the following shape data:

• Name
• Source System
• Update Mode
• Loading Time

A DataTransferProcess has for example:

• Technical Name
• Extraction Mode
• Loading Time

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.

Now you can enter one InfoCube and choose Transfer. Now you can add more tests or click Execute to run the test.

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:

• 2424808 - AO 2.x: Planning - Error occurs when saving a new line that contains fields of the type "Date"
• 2431548 - Exception after inserting Query
• 2431738 - Analysis Office: Swap Axis button active for grouped crosstabs when cursor is outside the grouped crosstabs
• 2431821 - Analysis Office: SAPContainer visible after ungrouping all crosstabs
• 2422924 - Paste values: Members containing "-" are handled like a intervals
• 2426904 - VBA callbacks of wrong workbook are executed
• 2422141 - Analysis Office: If saving to NetWeaver platform into 'My Documents' the 'Save' button is not active
• 2429271 - Analysis Office: Formula =SAPGetWorkbookInfo("LogonUser") does return an empty string when logging in to BIP with SSO
• 2438868 - AO 2.x: Formula SAPGetVariable shows wrong value for Hierarchy Node variable

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 the transaction SE16 open table RSPCCHAIN and insert into VARIANTE the technical name of your process chain.

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.

Nobody will remember this after a huge project, so every request has to be transported twice and this is annoying. So we have to find a solution for this. I found a thread on the SCN which describes a solution that worked for me. Yes I found a link which is still working after the redesign of the SCN. I was surprised. Here is the solution: