It has been a quite while since the last post. But with a go live and a reorganization of my current project I hadn't time to look into some topic. But here is a new kind of interessting bug. We had an open task from a user of the controlling department, that a query display the message:
"Size Limit of result set exceeded."
Since 24.05.2019 the latest service pack of Analysis Office is available. At the moment I am working on a test tool to automate testing in BW so I can easy check if any change of mappings and so on has an impact on my ADSO or query result. But I found time to install it. A "bug" what I found was when I want to insert a data source from the recent list, nothing happend. The solution was to reinstall Analysis Office and now it works. Here is the list of bug fixes:
Here just a short notice if somebody doesn't know it yet. If you have a false information in a data record you can fix this manually either in a PSA or (A)DSO. Just select the desired entry and click Display (F7).
It has been very quite at the moment.Because nothing spectecular is happening in the Analysis Office world. SAP released Analysis Office 2.7 SP5. I still hope they get Analysis Office 2.8 back on track and without so much problems as they have today. But back to topic.
Since last week SAP published the latest version of Analysis Office 2.7 SP5. I don't know if any other version ever had a service pack so high like the actual version. At this time SAP doesn't offer the newst help file under help.sap.com/boaa. So stay tuned if there is something happening. Here is an overview about what they fixed:
In my current project we have the hide a position in a hierarchy, because it is a departmental requirement. The hierarchy is used by many departments so we cannot change it and we also don't want to have the same hierarchy two times (except for the one position). So we first excluded the position in the query.
Since last week the latest SP of Analysis Office is available. You can download it here, but you need a S-User. I know I am a little bit late but here here is the overview of what is now fixed:
It is done, the newest edtion of Analysis Office - The Comprehensive Guide is available. It took me this time a little bit longer to update it. There are several reasons like my project workload or the the private stuff which make it sometimes difficult to write on a book and tests functions in peace without noise. You can now find it in the store and here is the table of content. It covers Analysis Office 2.7 SP3 and contains 299 Pages. It is only available as PDF but it is as always DRM free. Also is the 3rd edition now available on amazon.
Since the 21.12.2018 the latest service pack of Analysis Office 2.7 is available. I looked in the morning into the Support Portal but it wasn't released and in the afternoon Patrick wrote on Twitter, that Analysis Office 2.7 SP3 is released. I thought it wouldn't released anymore in 2018 but here are the fixed problems:
In my current project I have to filter data with a lot of logic. So I build some ABAP routines in a DTP filter to receive the necessary data. First you have to open the DataTransferProcess (DTP) in change mode and select the Filter button on the Extraction tab.
I received an email from Jean-Pierre, who tried the new function Data Source for Defining Formulas of Analysis Office 2.7 - but it didn't work as he mentioned in his email. The option Select Data Soure for Defining Formulas was gray out for BEx Queries. It worked when he insert the Multiprovider or the Composite Provider. So I was very confused and tried to find a solution.
It is a little late for Analysis Office 2.7 SP2 but SAP just delivered Patch 1 so I can write a short note about it. Finaly SAP give you the option to Create a Web Application in Lumira Designer. But if you installed SAP Design Studio an SAP Lumira Designer, it always opens Design Studio. Analysis Office doesn't care if you first install Lumira or Design Studio. Design Studio always wins. At the moment there is no setting like the DefaultBWQueryDesigner for the old BEx Query Designer or the new Eclipse Query Designer.
Patch 1 also fixes some little bugs.
I think it is nothing spectacular but it is maintenance.
It's been a while since the last blog post and I am also late for the news that Analysis Office 2.7 SP2 is available. As Patrick told me on 05.10.2018 Analysis Office 2.7 SP2 is GA. But I was on vaction so I didn't find the time to write about it. So here we are:
This is fixed in Service Pack 2
When I have more time, I will look deeper into Analysis Office 2.7 SP2 and write a short overview.
Since last week Analysis Office 2.7 SP1 is available. Here is a short overview what SAP fixed in this verison.
Since Analysis Office 2.6 you are able to launch workbooks from BIP with variables. The biggest problem is to have a BI Platform 4.2 SP5 and time to test this feature. In case of writing an updated version of Analysis Office - The Comprehensive Guide, I now have a BI Platform which fulfilled the conditions. According to SAP slides, the command looks like this:
In my current project we have a go live. So I needed a function to reset the transport status of some transports. So if you release your transport falsely the transport is locked by release and can no longer be removed from the transport status. Maybe you also want to delete the entire transport request. This option is also denied as soon as the tasks have been released. The standard procedures are very laborious and not only cost a lot of time, but also have a certain risk potential. SAP offers a report which solves your problem. The report is RDDIT076. As you see in the next picture, the transport is released.
A new function in Analysis Office 2.7 is "Select Data Source for Defining Formulas". But what does this mean? First the prerequisites:
So I just logged into my BW 7.50 test system and what I have to see, we only have a BW 7.5 SP11. So I have applied the notes and each note need further notes to implemented. I just want to test something and now I have to implement more than 30 notes.
In my project I have now the opportunity to build SAP HANA Calculation Views. We use Calculation Views to combine two different Advanced DataStore Objects. First you have to set the parameter External HANA View in the setting of your ADSO. When you activate this setting a SAP HANA Table is created which you can use in a Calculation View.
Today Analysis Office 2.7 was released. Thanks to Zisi1990, who pointed me seconds after it was released that it is available. You can download it with a S-User. Here is a short overview what's new in Analysis Office 2.7:
After a short vacation over Pentecost I have now time to write "What's new in Analysis Office 2.6 SP3". A short overview yo find in this post. The user guide shows some new things:
The admin guide has 20 new pages to the Analysis Office 2.6 guide. The settings chapter is new organized and in my opinion a little bit better organized than before. Also new is the topic how to use the BI Platform with hyperlinks and variables like the old BI Portal. This is described in section 5.9.4 in the admin guide.
Since yesterday Analysis Office 2.6 SP3 is available. You need as always a S-User to download the latest version. Here is a short overview what it might fix.
In my current project we run into an issue that we have to match navigation attributes from one ADSO to an infoobject of another ADSO. The old feature of a MultiProvider was to Identify (assign).
I hope you can help me, to find out if there is any interesting about a book that covers BW Backend topics. I think about a book which covers SAP HANA, AMDP/ABAP, BW Administration and so on. Thanks for your time.
If you want to create a Composite Provider in the BW Modeling Tools, you have to choose New >> Composite Provider in the context menu of your InfoArea or File >> New >> Composite Provider.
Since last week the new version of my book SAP Analysis Office - The Comprehensive Guide is now available. You can find it only here in my shop. The book is based on Analysis Office 2.6 and covers now all about:
The table of content can be found here. If you have any questions feel free to write them into the comments.
One question from me:
Is it ok, that there is only Paypal as payment method or do you need more? Just write it in the comments and I will see what I can do.
Analysis Office 2.6 SP2 is available since two weeks. There are only some slight changes to Analysis Office 2.6 SP1. You are now able to set the selection type for the formula SAPSetFilterComponent to MEMBERSELECTORBYRANGE. So you can use it to define the filter dialog with range option as standard.
Also a new selection type for the VBA API SAPCallMemberSelector is now available. It is called MULTIPLEBYRANGE, which allows you to select a range of members for filtering. So if you found new functions, feel free to write them down in the comments.
Since two days the new version of Analysis Office 2.6 is available. You need as always a S-User to download the latest version. Here is a short overview what it might fix:
A overview what's new will be available next week. If you find something interesting, please feel free to post a comment.
Analysis Office 2.6 SP1 is available since last week. When you look at the What's new guide from SAP, you see nothing spectacular new. You have now a new file system setting called AlwaysDoApplicationSteps. You can use this setting to write entries into the table RSDDSTAT_OLAP afer each action without the need to close Analysis Office.
In my current project I have a file to import, which only delivers me a string with a length of 1000. I also get a description what is in this file. Like the following points:
The file looks like: 0000123456London............................ So I have a file and a description how to decode this file. Now I need to find a way to separate this information into InfoObjects. I build a Z-Table which contains the decode information.
Since today Analysis Office 2.6 SP1 is available. You need as always a S-User to download the latest version. Here is a short overview what it might fix.
A overview what's new will be available next week. If you find something interesting, please feel free to post a comment.
Lately, all my posts started with "In my current project", so now something else, even if it was developed in the current project. The problem we are facing with is that we get a data extraction which deliver us only the new data records, not the reverse data record.
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.
After I started my BW/4HANA instance on cal.sap.com and everything was working, I logged on and typed RSA1. But there was no modeling tab anymore. Then I rememberd, I need the BW Modeling Tools. So I installed the latest Version of Eclipse and the BW Modeling Tools. After that I need a Project. The project is the binder for all activities in our BW system. Make a right-click in the Eclipse Project Explorer and choose BW Project.
A new feature of Analysis Office 2.4 is workbook or sheet protection. It is similar to the Microsoft Excel Protect Sheet / Workbook function, but it is also different. When you need to protect your workbook or sheet and you use the Excel functionality, you can not refresh or drill down your Crosstab. But when you want to refresh your data or give the users the opportunity to drill down or filter, you have to use the workbook / sheet protection from Analysis Office.
And also these parameters:
Only then AppBuilderCompanyProfileDirectory is a PerMachine parameter, the others are UserRoaming. How the other parameters exactly work has to be tested. The Ao_app.config also provides new parameters:
So it can be possible that the user can choose between the old BEx Query Designer and the new BW Modeling Tools. The default parameter is "0", so at the moment I cannot say what exactly has to be the value for other query designers. The parameter DoSelectorHierarchyExplicitSelection should select only the child nodes of a node and the parent node is not automatically checked. But I haven't got a chance to test this. So I can't confirm this. I don't know at the moment how the parameter AutoCompleteFetchMemberLimit works, I only know the default value is 30. But as soon as possible I add these information to this post.
So after I read a lot about BW/4HANA, I decided to create a own SAP BW/4HANA 1.0 [Developer Edition] instance on my Amazon AWS account. First I had to extend my normal AWS account with a IAM user. For this you choose under Security, Identity & Compliance >> IAM. Under Users you click on Add user.
A new feature of Analysis Office 2.4 is that you have a function called Customize User Interface. On the first view it looks similar to the Excel customize ribbon function. But it has more flexiblity to switch between different interfaces. First you have to open the Customize User Interface dialog via File >> Analysis. The following dialog appears.
This week I want to test the integration of a BI Platform to my .Net program. So I want to install a test version of the BIP, but my virtual machine hadn't enough space. The first step was to extend the space of the disk. It is very easy in VirtualBox to extend the disk.
After my VirtualBox was ready I could install the BIP. But the next issue was found very soon. I need a license key.
So it is done, Part 2 finally is written and an example is uploaded to github. It took me about 8 months to release Part 2 of these series. Part 1 was released in March 2016 and now I had time to write an example for Part 2 and upload it to github. Part 1 discover the basics about a RFC Server with the SAP NCo Connector, part 2 now explain how to build a RFC Server more flexible.
If a SAP Design Studio Application has been developed in local mode or on a develop machine, these can be exported and then imported into a new system. Here is a short guide.
This week the new open SAP course BW/4HANA in a Nutshell started. It is a free course. One big thing is that BW/4HANA no longer supports the good old BEx Suite. You now have to use the BW Modeling Tools based on Eclipse. In this and further posts I will go deeper into the BW Modeling Tools and what is possible and what is not possible at the moment.
If you have any questions feel free to ask or correct me ;) So let's get started.
Here is a short guide how to update an extension in SAP Design Studio.
1. Select Help >> About
In this article I describe in a short manual how to set up Eclipse for Design Studio.
1. Open Eclispe and choose Window >> Preferences.
This week I don't have much time to write an article about Analysis Office, but I found an interesting article from Xavier about Migrating Analysis for Office workbooks from BW to BI Platform last week.
The topic came up yesterday as a collegue asked me if I know why he can't save a workbook to the BI platform. The workbook was opened from a NetWeaver system and than the option save to BI Platform isn't available.
So read this article if you have the same problem.
You can define the RuleID, if you do not define an ID, the system generates one automatically. As Data Source Alias, you have to enter the data source alias, e.g. DS_1. As Position you can choose between Before, After, BelowHeader or BesideHeader. For PositionBy you can enter one of the following elements:
Here is the post Analysis Office: How to work with Excel formulas as a short video.
Since Analysis Office 2.3 was released, you are able to cancel long-running queries. In the Ao_app.config you can define the parameter CancelPopupDelay. The default value is 5 seconds. You can change this setting to specify after how many seconds the cancel dialog should be displayed. The dialog could appear when you inserting a data source or navigating through the data and it took more than 5 seconds.
If the dialog is displayed, you could press "cancel" to cancel the server request. In the following message dialog, you can select restart to go back to the workbook and the data source is active. Or you select close to go back to the workbook and the data source is offline. If you don't cancel the request, the dialog will disappear automatically when the server request is completed.
It is done. My Analysis Office book is finished. You can now download the table of content and the release of the book is next week. Have fun and if you have feedback send it to me.
Have a nice weekend.
The information what you need to use Design Studio including the SDK can be found on many places. My problem was there is no guide where you find everything and here is a list:
The Preferred Startup Mode of Design Studio decides where an application is developed and saved.
In Analysis Office 2.2 SP3 some new interesting parameter for Ao_app.config were delivered. The following parameter are interesting and in some case maybe very useful.
Use this setting to define the maximum number of parallel threads that can be used to open the SAP HANA DataSources of a workbook. This only works with SAP HANA.
Use this setting to specify the mode of the prompting dialog when you open a workbook from the NetWeaver that contains exactly one DataSource.
The function SAPGetVariable returns the value for a specific BW variable. For example:
and reinstall Design Studio again. Maybe sometimes it is enough to rename only the folders. More Design Studio troubleshooting can be find in the Design Studio Wiki.
Analysis Office has different two kinds of variants. One is a workbook variant and the other is a DataSource variant. So what is exactly the difference?
If you have a workbook you can save your variants in the prompt dialog.
I just got access to a NetWeaver 7.5 SP2 and I want to test it with Analysis Office 2.3. So I open Excel and insert a query. And here we go first error: "unable to open data source", so I thought maybe the query is broken and I developed a new query and insert it. Here we go, same error. Maybe queries don't work, so I insert a InfoCube directly. Same error...
Now I refresh the insert query and got an Analysis Office message: Error while executing function module: BICS_PROV_OPEN
In the explanation was one line with the hint "wrong parameter type in an rfc call", so I looked into st22 and saw a dump which the message: CALL_FUNCTION_ILLEGAL_P_TYPE
The other day I had a very strange phenomenon. I was at a client, where I had created several queries a month ago. The query information shows me as owner of these queries. In the meantime the Department has made some small changes, so that I was no longer the last user who changed the query.
A new feature of Analysis Office 2.3 is a macro called SAPOpenWorkbook. Some of you maybe know the old sapbex.xla!SAPBExReadWorkbook or the BExAnalyzer.xla!runWorkbook command.
The user guide explanation for this macro is:
You can use this API method to open an Analysis workbook. The workbook that should be opened can be stored on a SAP NetWeaver server or on a BI platform.
The workbook is opened in the same Microsoft Excel instance. After the command execution, the opened workbook is active.
As you know the sapbex.xla!SAPBExReadWorkbook respectively BExAnalyzer.xla!runWorkbook command needed either an established connection from the addin or you created your own connection with the following code:
For more articles please use the year archive above.
Life experiences of a SAP Business Warehouse Consultant