I just got an email from you via the contact formula. But When I answer to your email or to your shop order, I get an error "The email account that you tried to reach does not exist." I tried it several times, maybe your account is full? So can you please provide me another mail address or contact information? Maybe via Linkedin or so?
Thanks, I don't know any other way to contact you :)
Until the end of the month you can get my book with 30% off. Just use the discount code Summer2019. You can buy it here.
It's a kind of summer break at the moment and I haven't done a lot for this blog in the last time. But SAP now release the 7th service pack of Analysis Office.
You can now use the filtering data access mode with SAP Analytics Cloud data sources, analytic and planning models. There are also 3 new file system settings:
The setting ShowCutCopyPasteInGridContextMenu allows you to sepcify whether the cut, copy and paste entries should be available in the context menu for a crosstab cell. The setting EnableImprovedAddInCompatibility should improve the compatibility with other Microsoft Office add-ins. How this work we will see.
The setting UseSeparateDisplaySettingsForFilterDialog you can define if the display settings defined in the filter dialog should be saved with the workbook.
So as you can see nothing spectecularit fixes also a little bit:
I am still looking for Analysis Office 2.8, but now I am first enyoing my vacation.
In our current project we had to deal with the requirement that the enduser only want to show a certain node of a hierarchy to filter. So we used the F4 restriction from the transaction spro. You find the entry under Business Warehouse >> Enhancements >> BAdI: Restricting the Value Help in the Variables Screen. We implemented it in the method GET_RESTRICTION_NODE.
At this time I had only experience with the method GET_RESTRICTION_FLAT and searched for implementation examples. I found a wiki entry on scn. In our case we had bookable nodes so we implemented it like this to get these node and all children of it.
l_s_node-nodename = 'NODE1'.
l_s_node-niobnjm = 'ZZ_IO'.
Append l_s_node to c_t_node.
But it didn't work out. The debugging showed no error, but the restriction always showed the complete hierarchy. After a little digging we found our mistake, it have to look like the follwing:
l_s_node-nodename = 'LEAF1'.
Append l_s_node to c_t_node.
l_s_node-nodename = 'LEAF2'.
Append l_s_node to c_t_node.
And so on for all leafs. So we had to add all leafs and not the nodes. I didn't found any good explanation so here is the short article about it. Thanks to my collegue who had the problem.
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."
That's an odd thing, because the query has only six columns and 110 rows and when the user dragged the calendar month into the columns it should have 12 columns for the actual year and 110 rows. Which is defintily lower than the limit of Analysis Office, which is 500.000 cells.
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:
Did anyone have the same bug with the Insert DataSource function?
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.
Recently I had the opporunity to work with SAP HANA Table Functions. First I had a complex SAP HANA Calculation View with Joins, Aggregations and so on. But I read a blog post on the SCN by Konrad Załęski and thought maybe I can use Table Functions to do the same as I do with my Calculation Views.
I use Eclipse 2018-09 (4.9.0) and the BW Modeling Tools 1.19.35 so maybe the options are not at the same position in another version. As far as I know SAP, the buttons are definitly not at the same position anymore. 🙈
To reduce the complexity I used three calculation views to narrow down my problem step by step.
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 as always a bugfixing Service Pack and as I mentioned in the last article, there are no new functions. I am still looking forward to Analysis Office 2.8.
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:
It is as always a bugfixing Service Pack and I don't see any new functions. If you find one, just write it to the comments. Just little notice, my book Analysis Office - The Comprehensive
Guide 4th edtion with Analysis Office 2.7 is almost ready for proofreading and so stay tuned.
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.
The Problem only exists when he insert a Bex Query and he received the error message:
"The selected data source cannot be used formula-optimized. The data source is inserted without crosstab to be used for analysis (ID-113017)
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.
The User and Admin Guide is still on Analysis Office 2.7 and I hope it will be released the next days.
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:
&var[<data source alias>]<variable>=<value>
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.
Life experiences of a SAP Business Warehouse Consultant